still debugging dns issues that are no doubt to do with wider issues:
someone here might know who to tell?
#whois amazon.com
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for
On Thu, Dec 9, 2010 at 3:40 PM, Paul Macdonald p...@ifdnrg.com wrote:
still debugging dns issues that are no doubt to do with wider issues:
someone here might know who to tell?
#whois amazon.com
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
On 09/12/2010 21:10, Gary Gatten wrote:
Probably Wikileaks supporters fighting back against the DDoS. Interesting
issue, anyone else seeing similar problems?
i came across the amazon whois hack as a result of debugging failed
whois lookups (on freebsd obv)
given the freebsd method of
2010
Subject: more dns weirdness
still debugging dns issues that are no doubt to do with wider issues:
someone here might know who to tell?
#whois amazon.com
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go
On Thu, Dec 09, 2010 at 09:24:56PM +, Paul Macdonald wrote:
On 09/12/2010 21:10, Gary Gatten wrote:
Probably Wikileaks supporters fighting back against the DDoS. Interesting
issue, anyone else seeing similar problems?
i came across the amazon whois hack as a result of debugging failed
On 09/12/2010 22:01, Andy Tornquist wrote:
Have you tried a different server to query?
the wider issue is that freebsd whois will use tld.whois-servers.net
cnames to resolve appropriate whois servers and that whois-servers.net
has nameservers from one sole provider (ultradns), which is
Have you tried a different server to query?
On 12/9/10, Paul Macdonald p...@ifdnrg.com wrote:
still debugging dns issues that are no doubt to do with wider issues:
someone here might know who to tell?
#whois amazon.com
Whois Server Version 2.0
Domain names in the .com and .net domains
On Thu, Dec 9, 2010 at 5:15 PM, Paul Macdonald p...@ifdnrg.com wrote:
the wider issue is that freebsd whois will use tld.whois-servers.netcnames to
resolve appropriate whois servers and that
whois-servers.net has nameservers from one sole provider (ultradns),
which is still having problems.
On Thu, Dec 9, 2010 at 2:15 PM, Paul Macdonald p...@ifdnrg.com wrote:
On 09/12/2010 22:01, Andy Tornquist wrote:
Have you tried a different server to query?
the wider issue is that freebsd whois will use tld.whois-servers.net cnames
to resolve appropriate whois servers and that
