Odd issue with some domain queries
Larry Ludwig
larrylud at gmail.com
Mon Jun 1 14:53:56 UTC 2009
Hi all we are having this odd problem with only a few domain queries
and stumped on where is the issue...
Ok here is the details.
These three domains do not work through our name servers:
- lift.org
- khenkho.com
- rejuvenatetraining.com
If I query our name server I get an invalid domain name, yet if I
query say OpenDNS or use dig it works?? This issue isn't for the many
other DNS queries we perform and it appears to be only a select few.
Here is the output:
[root at ns1 etc]# nslookup lift.org
Server: 192.168.11.3
Address: 192.168.11.3#53
** server can't find lift.org: SERVFAIL
[root at ns1 etc]# dig +trace lift.org
; <<>> DiG 9.2.4 <<>> +trace lift.org
;; global options: printcmd
. 516709 IN NS e.root-servers.net.
. 516709 IN NS f.root-servers.net.
. 516709 IN NS g.root-servers.net.
. 516709 IN NS h.root-servers.net.
. 516709 IN NS i.root-servers.net.
. 516709 IN NS j.root-servers.net.
. 516709 IN NS k.root-servers.net.
. 516709 IN NS l.root-servers.net.
. 516709 IN NS m.root-servers.net.
. 516709 IN NS a.root-servers.net.
. 516709 IN NS b.root-servers.net.
. 516709 IN NS c.root-servers.net.
. 516709 IN NS d.root-servers.net.
;; Received 316 bytes from 192.168.11.3#53(192.168.11.3) in 2 ms
org. 172800 IN NS A2.ORG.AFILIAS-NST.INFO.
org. 172800 IN NS D0.ORG.AFILIAS-NST.org.
org. 172800 IN NS B2.ORG.AFILIAS-NST.org.
org. 172800 IN NS B0.ORG.AFILIAS-NST.org.
org. 172800 IN NS C0.ORG.AFILIAS-NST.INFO.
org. 172800 IN NS A0.ORG.AFILIAS-NST.INFO.
;; Received 428 bytes from 192.203.230.10#53(e.root-servers.net) in
100 ms
lift.org. 86400 IN NS ns1.phadhost.com.
lift.org. 86400 IN NS ns2.phadhost.com.
;; Received 74 bytes from 199.249.112.1#53(A2.ORG.AFILIAS-NST.INFO) in
99 ms
lift.org. 14400 IN A 174.132.255.78
lift.org. 86400 IN NS ns2.phadservers.com.
lift.org. 86400 IN NS ns1.phadservers.com.
;; Received 125 bytes from 174.132.255.76#53(ns1.phadhost.com) in 125 ms
[root at ns1 etc]# nslookup khenkho.com
Server: 192.168.11.3
Address: 192.168.11.3#53
** server can't find khenkho.com: SERVFAIL
[root at ns1 etc]# dig +trace khenkho.com
; <<>> DiG 9.2.4 <<>> +trace khenkho.com
;; global options: printcmd
. 516692 IN NS c.root-servers.net.
. 516692 IN NS d.root-servers.net.
. 516692 IN NS e.root-servers.net.
. 516692 IN NS f.root-servers.net.
. 516692 IN NS g.root-servers.net.
. 516692 IN NS h.root-servers.net.
. 516692 IN NS i.root-servers.net.
. 516692 IN NS j.root-servers.net.
. 516692 IN NS k.root-servers.net.
. 516692 IN NS l.root-servers.net.
. 516692 IN NS m.root-servers.net.
. 516692 IN NS a.root-servers.net.
. 516692 IN NS b.root-servers.net.
;; Received 332 bytes from 192.168.11.3#53(192.168.11.3) in 2 ms
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
;; Received 501 bytes from 192.33.4.12#53(c.root-servers.net) in 21 ms
khenkho.com. 172800 IN NS ns1.webanize.com.
khenkho.com. 172800 IN NS ns2.webanize.com.
;; Received 106 bytes from 192.54.112.30#53(H.GTLD-SERVERS.NET) in 101
ms
dig: couldn't get address for 'ns1.webanize.com': failure
[root at ns1 etc]# nslookup
> rejuvenatetraining.com
Server: 192.168.11.3
Address: 192.168.11.3#53
** server can't find rejuvenatetraining.com: SERVFAIL
> exit
[root at ns1 etc]# dig +trace rejuvenatetraining.com
; <<>> DiG 9.2.4 <<>> +trace rejuvenatetraining.com
;; global options: printcmd
. 516892 IN NS j.root-servers.net.
. 516892 IN NS k.root-servers.net.
. 516892 IN NS l.root-servers.net.
. 516892 IN NS m.root-servers.net.
. 516892 IN NS a.root-servers.net.
. 516892 IN NS b.root-servers.net.
. 516892 IN NS c.root-servers.net.
. 516892 IN NS d.root-servers.net.
. 516892 IN NS e.root-servers.net.
. 516892 IN NS f.root-servers.net.
. 516892 IN NS g.root-servers.net.
. 516892 IN NS h.root-servers.net.
. 516892 IN NS i.root-servers.net.
;; Received 316 bytes from 192.168.11.3#53(192.168.11.3) in 25 ms
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS A.GTLD-SERVERS.NET.
;; Received 512 bytes from 192.58.128.30#53(j.root-servers.net) in 103
ms
rejuvenatetraining.com. 172800 IN NS ns1.qualdns.net.
rejuvenatetraining.com. 172800 IN NS ns2.qualdns.net.
;; Received 119 bytes from 192.33.14.30#53(B.GTLD-SERVERS.NET) in 249 ms
rejuvenatetraining.com. 14400 IN A 174.132.225.20
rejuvenatetraining.com. 86400 IN NS ns1.qualdns.net.
rejuvenatetraining.com. 86400 IN NS ns2.qualdns.net.
;; Received 135 bytes from 174.132.225.18#53(ns1.qualdns.net) in 128 ms
Any ideas on what could be the issue?
Thanks in advance for your help.
-L
--
Larry Ludwig
More information about the bind-users
mailing list