[Discuss] DNS problems

[R. McFarlane]

At 07:48 PM 8/20/2006, Steven Kurylo, had this to say :

>I don't understand, maybe the terminology is wrong.  Other DNS servers
>should respond that there is no record, as their not the server for
>your record.
>
>However if you query a DNS cache, it should come back with the correct
>answer.  Before you get into that, ensure the DNS chain is actually
>working.
>
>For example, www.google.com
>*I've removed most of the output for brevity
>1)Ask a root server
>#dig @198.41.0.4 www.google.com
>A.GTLD-SERVERS.NET.     172800  IN      A       192.5.6.30
>2)Ask the next server (in this case, the com server)
>#dig @192.5.6.30 www.google.com
>ns1.google.com.         172800  IN      A       216.239.32.10
>3)Ok, now ask the google server
>#dig @216.239.32.10 www.google.com
>www.google.com.         604800  IN      CNAME   www.l.google.com.
>a.l.google.com.         86400   IN      A       216.239.53.9
>4)So now we have to ask about www.l.google.com.
>#dig @216.239.53.9 www.l.google.com.
>www.l.google.com.       300     IN      A       66.102.7.99
>
>Which is our final answer.  So you have to be able to do that first.
>Then you can worry about other DNS caches (not servers) getting the
>answer right.  Unless there is a firewall, they should just work.


         In using your example, it looks like my registrar is where 
the problem lies. I was able to follow the "chain" exactly like you 
did (except using the domain name I was trying to diagnose) and I got 
all the expected answers, but the problem remains that when you dig 
the domain name in question nothing shows. I can only surmise that my 
registrar has not updated their records properly or some such.
         Thank you for a fresh look at the problem!


http://www.mcfarlanecomputing.net/