Selective forwarding for reverse zones?

[Treptow, Craig]

Here is the reverse behavior on nameserver1:

# nslookup 192.168.40.26
Server:  nameserver1.principal.com
Address:  192.168.34.5

*** nameserver1.principal.com can't find 192.168.40.26: Non-existent
host/domain
# hostname
fozzy
#
# nslookup fozzy
Server:  nameserver1.principal.com
Address:  192.168.34.5

Name:    fozzy.principal.com
Address:  192.168.34.5


And the debug and d2 output from a reverse query on nameserver1 using
nslookup:

# nslookup
Default Server:  nameserver1.principal.com
Address:  192.168.34.5

> set debug
> 192.168.40.26
Server:  nameserver1.principal.com
Address:  192.168.34.5

;; res_nmkquery(QUERY, 26.40.168.192.in-addr.arpa, IN, PTR)
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 29905, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion
avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        26.40.168.192.in-addr.arpa, type = PTR, class = IN
    AUTHORITY RECORDS:
    ->  168.192.in-addr.arpa
        ttl = 21600 (6H)
        origin = nameserver1.principal.com
        mail addr = kratochvil.keith.principal.com
        serial = 9909985
        refresh = 10800 (3H)
        retry   = 3600 (1H)
        expire  = 604800 (1W)
        minimum ttl = 21600 (6H)

------------
*** nameserver1.principal.com can't find 192.168.40.26: Non-existent
host/domain
> set d2
> 192.168.40.26
Server:  nameserver1.principal.com
Address:  192.168.34.5

;; res_nmkquery(QUERY, 26.40.168.192.in-addr.arpa, IN, PTR)
------------
SendRequest(), len 44
    HEADER:
        opcode = QUERY, id = 20099, rcode = NOERROR
        header flags:  query, want recursion
        questions = 1,  answers = 0,  authority records = 0,  additional = 0

    QUESTIONS:
        26.40.168.192.in-addr.arpa, type = PTR, class = IN

------------
------------
Got answer (142 bytes):
    HEADER:
        opcode = QUERY, id = 20099, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion
avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        26.40.168.192.in-addr.arpa, type = PTR, class = IN
    AUTHORITY RECORDS:
    ->  168.192.in-addr.arpa
        type = SOA, class = IN, dlen = 66
        ttl = 21600 (6H)
        origin = nameserver1.principal.com
        mail addr = kratochvil.keith.principal.com
        serial = 9909985
        refresh = 10800 (3H)
        retry   = 3600 (1H)
        expire  = 604800 (1W)
        minimum ttl = 21600 (6H)

------------
*** nameserver1.principal.com can't find 192.168.40.26: Non-existent
host/domain
> 

Is that the tracing you meant?  

I'm not yet dig literate so let me know if this is helpful:

# dig 192.168.40.26 +deb 

; <<>> DiG 8.2 <<>> 192.168.40.26 +deb 
;; res_nmkquery(QUERY, 192.168.40.26, IN, A)
;; res options: init debug recurs defnam dnsrch
;; res_send()
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35106
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;;      192.168.40.26, type = A, class = IN

;; Querying server (# 1) address = 192.168.34.5
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35106
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;;      192.168.40.26, type = A, class = IN

;; Total query time: 2116 msec
;; FROM: fozzy to SERVER: default -- 192.168.34.5
;; WHEN: Sun Mar 25 19:54:53 2001
;; MSG SIZE  sent: 31  rcvd: 31

# dig 192.168.40.26 +d2

; <<>> DiG 8.2 <<>> 192.168.40.26 +d2 
;; res_nmkquery(QUERY, 192.168.40.26, IN, A)
;; res options: init debug recurs defnam dnsrch ?0x80000000?
;; res_send()
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28490
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;;      192.168.40.26, type = A, class = IN

;; Querying server (# 1) address = 192.168.34.5
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28490
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;;      192.168.40.26, type = A, class = IN

;; Total query time: 2457 msec
;; FROM: fozzy to SERVER: default -- 192.168.34.5
;; WHEN: Sun Mar 25 19:54:23 2001
;; MSG SIZE  sent: 31  rcvd: 31
#

I've had little exposure to the tracing/debug output, so if the answer is
staring me in the face, please let me know.

Thanks.

Craig
-----Original Message-----
From: Barry Margolin [mailto:barmar at genuity.net]
Sent: Tuesday, April 11, 2000 12:30 PM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: Re: Selective forwarding for reverse zones?


In article
<93D3D41C8EB4D2119C4200805F9F496107C33034 at pfgdsmmsg010.principal.com>,
Treptow, Craig <Treptow.Craig at principal.com> wrote:
>The other details are the same before, as is the behavior displayed on the
>"nameserver1" machine

You never showed the behavior when trying to do a reverse lookup on the
nameserver1 machine.

Did you try turning on tracing on nameserver1 to see what it's doing when
you try the failing lookups?

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, 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.