The weirdest DNS problem I have come upon

Discussion in 'Server Operation' started by IPMolester, Jul 4, 2006.

  1. IPMolester

    IPMolester New Member

    I'm totally lost with this:

    I have set up a Linux (Mandriva 2006) server on my home ADSL line and everything works just splendid.

    Well, everything except for a tiny little problem. Bind sometimes has a problem with resolving A records, always for the same domains and hosts. But what I don't understand is that when I turn on more debugging in "dig" it shows me that it received the information, but a error claims it didn't

    Example:
    As you can see, dig did indeed receive the IP for ns1.theplanet.com, and then claimed it didn't.

    The problem doesn't seem to be a network problem, since I can ping the server.

    My question is this: Why is 'dig' claiming that it can't get the address for ns1.theplanet.com when it's obvious from the trace that it already did ?
     
    Last edited: Jul 4, 2006
  2. falko

    falko Super Moderator

    It's working for me:

    Code:
    dig www.break.com +trace +additional
    
    ; <<>> DiG 9.2.1 <<>> www.break.com +trace +additional
    ;; global options:  printcmd
    .                       279227  IN      NS      l.root-servers.net.
    .                       279227  IN      NS      m.root-servers.net.
    .                       279227  IN      NS      a.root-servers.net.
    .                       279227  IN      NS      b.root-servers.net.
    .                       279227  IN      NS      c.root-servers.net.
    .                       279227  IN      NS      d.root-servers.net.
    .                       279227  IN      NS      e.root-servers.net.
    .                       279227  IN      NS      f.root-servers.net.
    .                       279227  IN      NS      g.root-servers.net.
    .                       279227  IN      NS      h.root-servers.net.
    .                       279227  IN      NS      i.root-servers.net.
    .                       279227  IN      NS      j.root-servers.net.
    .                       279227  IN      NS      k.root-servers.net.
    ;; Received 228 bytes from 81.169.163.104#53(81.169.163.104) in 2 ms
    
    com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
    com.                    172800  IN      NS      M.GTLD-SERVERS.NET.
    A.GTLD-SERVERS.NET.     172800  IN      AAAA    2001:503:a83e::2:30
    A.GTLD-SERVERS.NET.     172800  IN      A       192.5.6.30
    G.GTLD-SERVERS.NET.     172800  IN      A       192.42.93.30
    H.GTLD-SERVERS.NET.     172800  IN      A       192.54.112.30
    C.GTLD-SERVERS.NET.     172800  IN      A       192.26.92.30
    I.GTLD-SERVERS.NET.     172800  IN      A       192.43.172.30
    B.GTLD-SERVERS.NET.     172800  IN      AAAA    2001:503:231d::2:30
    B.GTLD-SERVERS.NET.     172800  IN      A       192.33.14.30
    D.GTLD-SERVERS.NET.     172800  IN      A       192.31.80.30
    L.GTLD-SERVERS.NET.     172800  IN      A       192.41.162.30
    F.GTLD-SERVERS.NET.     172800  IN      A       192.35.51.30
    J.GTLD-SERVERS.NET.     172800  IN      A       192.48.79.30
    K.GTLD-SERVERS.NET.     172800  IN      A       192.52.178.30
    E.GTLD-SERVERS.NET.     172800  IN      A       192.12.94.30
    ;; Received 503 bytes from 198.32.64.12#53(l.root-servers.net) in 189 ms
    
    break.com.              172800  IN      NS      ns1.theplanet.com.
    break.com.              172800  IN      NS      ns2.theplanet.com.
    ns1.theplanet.com.      172800  IN      A       70.86.61.133
    ns1.theplanet.com.      172800  IN      A       70.86.61.134
    ns1.theplanet.com.      172800  IN      A       70.87.7.70
    ns1.theplanet.com.      172800  IN      A       70.87.7.71
    ns2.theplanet.com.      172800  IN      A       70.86.61.135
    ns2.theplanet.com.      172800  IN      A       70.86.61.136
    ns2.theplanet.com.      172800  IN      A       70.87.7.72
    ns2.theplanet.com.      172800  IN      A       70.87.7.73
    ;; Received 205 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 109 ms
    
    www.break.com.          10      IN      A       72.32.5.117
    break.com.              10      IN      NS      ns2.theplanet.com.
    break.com.              10      IN      NS      ns1.theplanet.com.
    ns1.theplanet.com.      7200    IN      A       70.86.61.134
    ns1.theplanet.com.      7200    IN      A       70.87.7.70
    ns1.theplanet.com.      7200    IN      A       70.87.7.71
    ns1.theplanet.com.      7200    IN      A       70.86.61.133
    ns2.theplanet.com.      7200    IN      A       70.86.61.135
    ns2.theplanet.com.      7200    IN      A       70.86.61.136
    ns2.theplanet.com.      7200    IN      A       70.87.7.72
    ns2.theplanet.com.      7200    IN      A       70.87.7.73
    ;; Received 221 bytes from 70.87.7.70#53(ns1.theplanet.com) in 137 ms
    What's in /etc/resolv.conf?
     

Share This Page