Bruce Momjian wrote:
> Stefan Kaltenbrunner wrote:
>> Bruce Momjian wrote:
>>> Bruce Momjian wrote:
>>>> Stefan Kaltenbrunner wrote:
>>>>> Hi all!
>>>>>
>>>>> It seems like that EDB has some serious issues with (non) availability
>>>>> of its main domain (looks like somebody forgot to renew the domainname
>>>>> and is now waiting for getting the delegation added back to the TLD or
>>>>> such).
>>>>> This means that it is not impossible for our users to actually download
>>>>> the windows binary packages - in the interest of redundancy it would
>>>>> probably be a good idea if we at least mirrored those packages on our
>>>>> own existing mirror network as well.
>>>>> This would allow us to at least offer people an alternative - just in
>>>>> case something like this happens again...
>>>> I talked to Jim Mlodgenski of EnterpriseDB and he is working on the
>>>> problem with other EDB employees. :-O
>>> I can now access the Postgres binary downloads and enterprisedb.com, so
>>> at least from here, it is working. I believe it has not propogated to
>>> all other places.
>> afaiks it is still dead(as in no delegation to
>> ns1.contegix.com/ns2.contegix.com - maybe it works for you because your
>> resolver has it still cached?
>
> No, it was dead for me at the time I got your email. FYI, I am not
> using Comcast's DNS servers but rather my own DNS server. I see Comcast
> does sometimes have the updated DNS, and sometimes not, so it must be
> propagating within their DNS farm:
>
> dig @ns.snj.comcastcommercial.net. enterprisedb.com
well it is still dead as far as I can see because there is no delegation
to in the root tld servers - try using "dig +trace" to make it chase the
delegation down from the root servers and see if that works for you.
Not sure why it works with your local resolver but I guess the reason
for the comcast thingy is that some of their boxes still have the
records cached from before the event...
Stefan