Bind 9.2.1 strangeness (dig)

[Kevin Darcy]

Robert Gahl wrote:

> I'm having some strange problems wrt BIND 9.2.1 and am at a loss to
> understand what is happening.
>
> The network topology here is that we live behind a DSL router (Flowpoint
> 2200) that is doing NAT for our office. When I attempt the following query
> from the DNS master, I get:
>
> [flame:/etc/rc.d/init.d]# dig taylormadegolf.com
>
> ; <<>> DiG 8.2 <<>> taylormadegolf.com
> ;; res options: init recurs defnam dnsrch
> ;; res_nsend to server default -- 192.168.254.1: Connection timed out
>
> However, when I do another dig, using a different domain, I get a valid
> response:
>
> [flame:/etc/rc.d/init.d]# dig wingchun.com
>
> ; <<>> DiG 8.2 <<>> wingchun.com
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
> ;; QUERY SECTION:
> ;;      wingchun.com, type = A, class = IN
>
> ;; ANSWER SECTION:
> wingchun.com.           6H IN A         64.82.99.81
>
> ;; AUTHORITY SECTION:
> wingchun.com.           6H IN NS        speakeasy.earthlink.net.
> wingchun.com.           6H IN NS        rumor.earthlink.net.
> wingchun.com.           6H IN NS        hearsay.earthlink.net.
>
> ;; ADDITIONAL SECTION:
> rumor.earthlink.net.    1d23h59m58s IN A  207.69.188.202
> hearsay.earthlink.net.  1d23h59m58s IN A  207.69.188.201
> speakeasy.earthlink.net.  1d23h59m58s IN A  207.69.188.200
>
> ;; Total query time: 2868 msec
> ;; FROM: flame.fireclick.com to SERVER: default -- 192.168.254.1
> ;; WHEN: Thu Feb  6 13:20:44 2003
> ;; MSG SIZE  sent: 30  rcvd: 173
>
> If I use one of our DNS servers that is located in one of our co-location
> facilities, I get a proper answer for taylormadegolf.com:
>
> web <bgahl>: dig taylormadegolf.com
>
> ; <<>> DiG 8.2 <<>> taylormadegolf.com
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
> ;; QUERY SECTION:
> ;;      taylormadegolf.com, type = A, class = IN
>
> ;; ANSWER SECTION:
> taylormadegolf.com.     3h50m43s IN A   209.204.119.40
>
> ;; AUTHORITY SECTION:
> taylormadegolf.com.     4h36m3s IN NS   ns2.snip.net.
> taylormadegolf.com.     4h36m3s IN NS   ns1.snip.net.
>
> ;; ADDITIONAL SECTION:
> ns1.snip.net.           1d21h50m43s IN A  209.204.64.2
> ns2.snip.net.           1d21h50m43s IN A  209.204.64.3
>
> ;; Total query time: 3 msec
> ;; FROM: web to SERVER: default -- 63.146.119.75
> ;; WHEN: Thu Feb  6 13:22:22 2003
> ;; MSG SIZE  sent: 36  rcvd: 128
>
> Does anyone have any pointers as to why I can't resolve this one domain but
> am able to resolve others? I have flushed the cache, restarted named, etc..
> trying to see if a clue comes forth, to no avail.
>
> Thanks for any assistance you can provide...

Beats me. I don't see anything obviously wrong with the domain. Can you
resolve *anything* from ns1.snip.net or ns2.snip.net? Try resolving their own
names: they are answering authoritatively for those from here.


- Kevin