From: TJ@noneofyour.business   
      
   On 07/23/2012 08:59 AM, TJ wrote:   
   > On 07/22/2012 10:39 PM, Moe Trin wrote:   
   >>   
   >> Hard to say for sure, but that _should_ be new enough - the RFC4074   
   >> dates from 2005, and it did make enough waves that a number of   
   >> manufacturers were embarassed into fixing things.  A stock WRT54G   
   >> should be at 192.168.1.254, and have something resembing a caching   
   >> nameserver - so   
   >>   
   >>    dig @192.168.1.254 a.root-servers.net     or   
   >>    host a.root-servers.net 192.168.1.254   
   >>   
   >> should return a list of root-name-server IPs, and 9 of the 13 root   
   >> servers have both IPv4 and IPv6 addresses, like   
   >>   
   >>    a.root-servers.net      3600000 IN      A       198.41.0.4   
   >>    a.root-servers.net      3600000 IN      AAAA    2001:503:ba3e::2:30   
   >>   
   >>          Old guy   
   >>   
   > Hmm. That's disturbing. The second command timed out before finding   
   > anything. The first returned this:   
   >   
   > ; <<>> DiG 9.9.1-P1 <<>> @192.168.1.254 a.root-servers.net   
   > ; (1 server found)   
   > ;; global options: +cmd   
   > ;; connection timed out; no servers could be reached   
   >   
   > Something is awry. Yet it's working, anyway. The "Gateway" is reported   
   > by Mageia 2 at 192.168.1.1. Should I be using that instead of the IP you   
   > suggested?   
   >   
   > TJ   
      
   Again, no time right now for intensive study of the situation. Winter   
   would be better.   
      
   TJ   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)