patrick.ainge.com

4 comments so far

1. 1 Avi Flax
   10:00 pm - 5-21-2006

   I think so, check out the DNS lookup.

   I got:

   DNS Lookup: feedlounge.com A record
   Generated by http://www.DNSstuff.com at 01:59:45 GMT on 22 May 2006.

   How I am searching:
   Searching for feedlounge.com A record at h.root-servers.net [128.63.2.53]: Got referral to d.gtld-servers.net. [took 10 ms]
   Searching for feedlounge.com A record at d.gtld-servers.net. [192.31.80.30]: Got referral to ns1.austindev.com. [took 145 ms]
   Searching for feedlounge.com A record at ns1.austindev.com. [65.90.216.129]: Got referral to B.ROOT-SERVERS.NET. [took 1044 ms]
   Searching for feedlounge.com A record at B.ROOT-SERVERS.NET. [192.228.79.201]: Got referral to K.GTLD-SERVERS.NET. [took 97 ms]
   Searching for feedlounge.com A record at K.GTLD-SERVERS.NET. [192.52.178.30]: Got referral to ns2.austindev.com. [took 91 ms]
   Searching for feedlounge.com A record at ns2.austindev.com. [64.237.106.132]: Timed out. Trying again.
   Searching for feedlounge.com A record at ns1.austindev.com. [65.90.216.129]: Got referral to L.ROOT-SERVERS.NET. [took 43 ms]
   Searching for feedlounge.com A record at L.ROOT-SERVERS.NET. [198.32.64.12]: Got referral to F.GTLD-SERVERS.NET. [took 77 ms]
   Searching for feedlounge.com A record at F.GTLD-SERVERS.NET. [192.35.51.30]: Timed out. Trying again.
   Searching for feedlounge.com A record at B.GTLD-SERVERS.NET. [192.33.14.30]: Got referral to austin.kingdesign.net. [took 248 ms]
   Searching for feedlounge.com A record at austin.kingdesign.net. [66.179.191.58]: Timed out. Trying again.
   Searching for feedlounge.com A record at austin.kingdesign.net. [66.179.191.58]: Timed out. Trying again.
   Searching for feedlounge.com A record at ns2.austindev.com. [64.237.106.132]: Timed out. Trying again.
   Searching for feedlounge.com A record at austin.kingdesign.net. [66.179.191.58]: Timed out. Trying again.

2. 2 Patrick Ainge
   10:22 pm - 5-21-2006

   I am also unable to find a cached address to test if it is only a DNS problem. The TTL on the records has been exceeded, but this only makes sense really.

3. 3 Alex
   1:50 am - 5-22-2006

   The DNS server fried itself - as the new DNS propagates, you should be able to get back to FeedLounge (which has, frustratingly, been up this whole time).

4. 4 Patrick Ainge
   12:03 pm - 5-22-2006

   Thanks for the update. Ahh DNS… Need I say more.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>