Some hosts not resolving from No-IP by our DNS servers

Josh Kuo josh.kuo at gmail.com
Wed Mar 9 18:37:37 UTC 2011


If I am not mistaken, when you do +trace, the trace actually comes
from your machine running 'dig', and not the DNS resolver itself.
(Others on list please correct me)

Can you perform the same 'dig' query from the DNS server, without
specifying which resolver to use? This smells like the DNS server
itself is having trouble communicating to the outside.

I would start from there to make sure the DNS server itself can
resolve these names. Also make sure recursion is enabled.


On Wednesday, March 9, 2011, Frank Pikelner
<Frank.Pikelner at netcraftcommunications.com> wrote:
>
>
>
>
>
>
>
>
>
>
> Hello,
>
> I'm having a problem resolving several hosts from NO-IP. When I attempt to resolve them from our DNS servers I get no reply (we can resolve other hosts). I'm not certain why the resolution stops. If I force a resolution using external DNS servers using dig (i.e. Google 8.8.8.8) the hosts resolve without problem. Here is the trace from our DNS server:
>
>
> dig oa.in-ip.info +trace
>
> ; <<>> DiG 9.6-ESV-R1 <<>> oa.in-ip.info +trace
> ;; global options: +cmd
> .                       25973   IN      NS      j.root-servers.net.
> .                       25973   IN      NS      e.root-servers.net.
> .                       25973   IN      NS      m.root-servers.net.
> .                       25973   IN      NS      k.root-servers.net.
> .                       25973   IN      NS      b.root-servers.net.
> .                       25973   IN      NS      d.root-servers.net.
> .                       25973   IN      NS      f.root-servers.net.
> .                       25973   IN      NS      g.root-servers.net.
> .                       25973   IN      NS      h.root-servers.net.
> .                       25973   IN      NS      c.root-servers.net.
> .                       25973   IN      NS      i.root-servers.net.
> .                       25973   IN      NS      a.root-servers.net.
> .                       25973   IN      NS      l.root-servers.net.
> ;; Received 436 bytes from 127.0.0.1#53(127.0.0.1) in 1 ms
>
> info.                   172800  IN      NS      d0.info.afilias-nst.org.
> info.                   172800  IN      NS      b2.info.afilias-nst.org.
> info.                   172800  IN      NS      b0.info.afilias-nst.org.
> info.                   172800  IN      NS      a0.info.afilias-nst.info.
> info.                   172800  IN      NS      a2.info.afilias-nst.info.
> info.                   172800  IN      NS      c0.info.afilias-nst.info.
> ;; Received 434 bytes from 192.58.128.30#53(j.root-servers.net) in 230 ms
>
> info.                   900     IN      SOA     a0.info.afilias-nst.info. noc.afilias-nst.info. 2009263081 3600 1800 604800 3600
> ;; Received 91 bytes from 199.249.113.1#53(a2.info.afilias-nst.info) in 3 ms
>
> Would appreciate any pointers.
>
> Thank you,
>
> Frank
>
>
>
>


More information about the bind-users mailing list