what the hell..?

[Kevin Darcy]

Yeah, that's what you get if you include "dig" twice in your command-line...

                                                                         
                           -Kevin

wharfratjoe wrote:

>; <<>> DiG 9.2.3 <<>> dig @ns.xs4all.nl saturncorp.com
>;; global options:  printcmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
>;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13
>
>;; QUESTION SECTION:
>;dig.                           IN      A
>
>;; AUTHORITY SECTION:
>.                       59238   IN      NS      a.root-servers.net.
>.                       59238   IN      NS      h.root-servers.net.
>.                       59238   IN      NS      c.root-servers.net.
>.                       59238   IN      NS      g.root-servers.net.
>.                       59238   IN      NS      f.root-servers.net.
>.                       59238   IN      NS      b.root-servers.net.
>.                       59238   IN      NS      j.root-servers.net.
>.                       59238   IN      NS      k.root-servers.net.
>.                       59238   IN      NS      l.root-servers.net.
>.                       59238   IN      NS      m.root-servers.net.
>.                       59238   IN      NS      i.root-servers.net.
>.                       59238   IN      NS      e.root-servers.net.
>.                       59238   IN      NS      d.root-servers.net.
>
>;; ADDITIONAL SECTION:
>a.root-servers.net.     145638  IN      A       198.41.0.4
>h.root-servers.net.     145638  IN      A       128.63.2.53
>c.root-servers.net.     145638  IN      A       192.33.4.12
>g.root-servers.net.     145638  IN      A       192.112.36.4
>f.root-servers.net.     145638  IN      A       192.5.5.241
>b.root-servers.net.     145638  IN      A       192.228.79.201
>j.root-servers.net.     145638  IN      A       192.58.128.30
>k.root-servers.net.     145638  IN      A       193.0.14.129
>l.root-servers.net.     145638  IN      A       198.32.64.12
>m.root-servers.net.     145638  IN      A       202.12.27.33
>i.root-servers.net.     145638  IN      A       192.36.148.17
>e.root-servers.net.     145638  IN      A       192.203.230.10
>d.root-servers.net.     145638  IN      A       128.8.10.90
>
>;; Query time: 187 msec
>;; SERVER: 194.109.6.67#53(ns.xs4all.nl)
>;; WHEN: Thu Dec 16 09:44:07 2004
>;; MSG SIZE  rcvd: 440
>
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18467
>;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
>
>;; QUESTION SECTION:
>;saturncorp.com.                        IN      A
>
>;; ANSWER SECTION:
>saturncorp.com.         43200   IN      A       12.23.213.10
>
>;; AUTHORITY SECTION:
>saturncorp.com.         43200   IN      NS      ns.saturncorp.com.
>
>;; Query time: 234 msec
>;; SERVER: 127.0.0.1#53(127.0.0.1)
>;; WHEN: Thu Dec 16 09:44:07 2004
>;; MSG SIZE  rcvd: 65
>
>Kevin Darcy wrote:
>
>  
>
>>D McDonald wrote:
>>
>> 
>>
>>    
>>
>>>Could sometype this into their shell for me..
>>>
>>>dig @ns.xs4all.nl saturncorp.com
>>>
>>>Ok, theres no answer, but how on earth did root-servers.com get in auth list? I understand that att 
>>>still think they are our soa...
>>>
>>>   
>>>
>>>      
>>>
>>ns.xs4all.nl doesn't support recursion (not to my client, and presumably 
>>not to yours either), and presumably doesn't have any relevant 
>>information cached. So it's giving you a referral to the root zone. 
>>There's nothing incorrect about that. If you want recursive service, you 
>>should be asking a nameserver that provides it to you.
>>
>>- Kevin
>> 
>>
>>    
>>
>
>
>  
>
>>
>>
>> 
>>
>>    
>>
>
>
>
>
>
>  
>