If I remember right, DIG does not know the root servers and asks the local host to retrieve that information and a server at 172.27.254.11(which is RFC 1918 address space) gave you that answer.

Is your machine/shop setup with private root servers?

Lyle

On 2/3/2015 12:50 PM, Linux Addict wrote:
I do dig . +trace and the results seem show .new servers. This is causing SERVFAIL for root query. Any ideas?

 dig . +trace

; <<>> DiG 9.7.0-P1 <<>> . +trace
;; global options: +cmd
.                       348510  IN      NS      b.root-servers.new.
.                       348510  IN      NS      h.root-servers.new.
.                       348510  IN      NS      l.root-servers.new.
.                       348510  IN      NS      f.root-servers.new.
.                       348510  IN      NS      m.root-servers.new.
.                       348510  IN      NS      k.root-servers.new.
.                       348510  IN      NS      i.root-servers.new.
.                       348510  IN      NS      e.root-servers.new.
.                       348510  IN      NS      g.root-servers.new.
.                       348510  IN      NS      j.root-servers.new.
.                       348510  IN      NS      c.root-servers.new.
.                       348510  IN      NS      d.root-servers.new.
;; Received 405 bytes from 172.27.254.11#53(172.27.254.11) in 1 ms

;; connection timed out; no servers could be reached



_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to