LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   Bind server is unable to resolve specific domain (https://www.linuxquestions.org/questions/linux-server-73/bind-server-is-unable-to-resolve-specific-domain-722923/)

bizzaro 05-01-2009 08:50 AM

Bind server is unable to resolve specific domain
 
I have a bind server that is unable to resolve a specific domain. I am able to resolve the domain from other places. Here is a trace.

; <<>> DiG 9.2.4 <<>> brinker.com +trace
;; global options: printcmd
. 110610 IN NS C.ROOT-SERVERS.NET.
. 110610 IN NS D.ROOT-SERVERS.NET.
. 110610 IN NS E.ROOT-SERVERS.NET.
. 110610 IN NS F.ROOT-SERVERS.NET.
. 110610 IN NS G.ROOT-SERVERS.NET.
. 110610 IN NS H.ROOT-SERVERS.NET.
. 110610 IN NS I.ROOT-SERVERS.NET.
. 110610 IN NS J.ROOT-SERVERS.NET.
. 110610 IN NS K.ROOT-SERVERS.NET.
. 110610 IN NS L.ROOT-SERVERS.NET.
. 110610 IN NS M.ROOT-SERVERS.NET.
. 110610 IN NS A.ROOT-SERVERS.NET.
. 110610 IN NS B.ROOT-SERVERS.NET.
;; Received 500 bytes from 168.98.65.5#53(168.98.65.5) in 7 ms

com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
;; Received 501 bytes from 192.33.4.12#53(C.ROOT-SERVERS.NET) in 15 ms

brinker.com. 172800 IN NS ns1.brinker.com.
brinker.com. 172800 IN NS ns2.brinker.com.
;; Received 97 bytes from 192.43.172.30#53(I.GTLD-SERVERS.NET) in 70 ms

brinker.com. 86400 IN A 63.163.55.10
brinker.com. 86400 IN NS ns1.brinker.com.
brinker.com. 86400 IN NS ns2.brinker.com.
;; Received 113 bytes from 63.163.55.51#53(ns1.brinker.com) in 39 ms


Dig run without trace:
; <<>> DiG 9.2.4 <<>> brinker.com
;; global options: printcmd
;; connection timed out; no servers could be reached

Any ideas??

archangel_617b 05-01-2009 11:18 AM

Uh, what? I see different NS records when I try to dig that domain:

dig ns binker.com +short
ns1.hostingnet.com.
ns2.hostingnet.com.


Is this some random domain on the Internet or what?

- Arch

10speed705 05-01-2009 12:32 PM

I am getting the same results.

Arch
You have a typo he is trying to find brinker.com not binker.com

archangel_617b 05-01-2009 02:52 PM

Quote:

Originally Posted by 10speed705 (Post 3526940)
I am getting the same results.

Arch
You have a typo he is trying to find brinker.com not binker.com

Oh, duh. So I did. My query looks okay for that domain:

Code:

brinker.com.            86400  IN      A      63.163.55.10
brinker.com.            86400  IN      NS      ns1.brinker.com.
brinker.com.            86400  IN      NS      ns2.brinker.com.
;; Received 113 bytes from 63.163.55.51#53(ns1.brinker.com) in 78 ms


bizzaro 05-04-2009 08:47 AM

It is brinker.com. I don't see why it won't resolve for me. Is there anything obvious in my previous trace? It keeps saying ;; connection timed out; no servers could be reached.


All times are GMT -5. The time now is 06:24 PM.