Reverse DNS for 32 IPs (was: PTR delegation 16 IPs)

[Barry Margolin]

In article <4.2.0.58.20000119112713.00a36890 at mail.fireclick.com>,
Robert Gahl  <bgahl at bawcsa.org> wrote:
>At 06:44 PM 1/19/00 +0000, Barry Margolin wrote:
>
>>Usually when dig works and nslookup doesn't, it's a problem with nslookup, 
>>not your configuration.
>
>Based on the other discussions I've seen on the list about nslookup, I was 
>beginning to lean that way.
>
>>Do you have recursion disabled on your nameserver?  If so, it won't be able
>>to look up its own address, because it needs to query the parent domain
>>server to find the CNAME record for its address, which would then refer it
>>to the RFC 2317-style subdomain.  Since nslookup refuses to use a default
>>server that can't reverse-resolve its own address, it will fail, even
>>though there's really nothing wrong.
>
>Sorry, Barry, but some of this is greek to me :( I don't have recursion 
>disabled that I know of. For the sake of completeness, here is what I have 
>so far:

What you posted looks fine to me.  You can try using "nslookup -d2" to see
detailed debugging information showing what nslookup is doing when it
fails.

If you post your actual IP addresses I might be able to figure it out.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, 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.