bind redirecting NS

[Charles Bodley]

Dug as suggested
dig habibi.tf-pdc.internal.tflogic.com @10.1.2.1

; <<>> DiG 9.1.0 <<>> habibi.tf-pdc.internal.tflogic.com @10.1.2.1
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45133
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;habibi.tf-pdc.internal.tflogic.com. IN A

;; ANSWER SECTION:
habibi.tf-pdc.internal.tflogic.com. 1200 IN A   10.1.8.251

;; Query time: 4 msec
;; SERVER: 10.1.2.1#53(10.1.2.1)
;; WHEN: Thu Dec 27 17:45:12 2001
;; MSG SIZE  rcvd: 68

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Barry Margolin
Sent: Thursday, December 27, 2001 3:42 PM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: Re: bind redirecting NS


In article <a0g0g6$hf1 at pub3.rc.vix.com>,
Charles Bodley <bodley at tflogic.com> wrote:
>
>New zone file.
>
>$TTL 3600
>$ORIGIN tflogic.com.
>internal        IN      SOA     internal.tflogic.com.
>hostmaster.tflogic.com. (
>                        2001121701 ; serial
>                        43200 ; refresh
>                        7200 ; retry
>                        1209600 ; expire
>                        3600 ; default_ttl
>                        )
>internal        IN      NS      blizzard.cyberset.com.
>internal        IN      A       10.1.2.17
>$ORIGIN internal.tflogic.com.
>localhost       IN      A       127.0.0.1
>users           IN      A       10.0.0.1
>tf-pdc          IN      A       10.1.2.1
>tf-pdc                  NS      tf-pdc
>tf-bb           IN      A       10.1.2.52
>
>Restarted named after making recommended change. Dig still cannot resolve
>it.

According to that response, your server went to the tf-pdc server, and this
is the answer it returned.  The delegation is correct -- tf-pdc claims that
the name isn't currently defined.  What happens if you query tf-pdc
directly with "dig habibi.tf-pdc.internal.tflogic.com @10.1.2.1"?

Make sure you don't have a 'zone "tf-pdc.internal.tflogic.com"' statement
in your server's named.conf.

>dig habibi.tf-pdc.internal.tflogic.com
>
>; <<>> DiG 9.1.0 <<>> habibi.tf-pdc.internal.tflogic.com
>;; global options:  printcmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3457
>;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
>;; QUESTION SECTION:
>;habibi.tf-pdc.internal.tflogic.com. IN A
>
>;; AUTHORITY SECTION:
>tf-pdc.internal.tflogic.com. 3600 IN    SOA
tf-pdc.internal.tflogic.com.
>hostmaster.tflogic.com. 2001082499 43200 7200 1209600 3600
>
>;; Query time: 6 msec
>;; SERVER: 10.1.2.17#53(10.1.2.17)
>;; WHEN: Thu Dec 27 15:26:51 2001
>;; MSG SIZE  rcvd: 99



--
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the
group.