[lug] Reverse DNS problems

Nate Duehr nate at natetech.com
Wed Aug 8 09:02:26 MDT 2001


The delegations have to be correct all the way down from the root
servers, just like forwards.  Sometimes if it's a small ISP they'll have
IP space that's actually "owned" by their upstream and not IP space from
ARIN.  If so, their upstream has to delegate the reverse lookups down
to their servers, then they delegate down to you... etc etc etc.

Standard NS delegation happens for anything larger than a Class-C,
otherwise see RFC 2317 for info on smaller-than-class-c (CIDR block) DNS
reverse delegation.  Or DNS & Bind from O'Riley & Associates...

Since there's nothing "secure" or "secret" about DNS entries, if you'll
provide the IP range you're trying to get working, we can all look at it
from here and probably see what is wrong with it... (this is a common
thread that comes up on the bind-isc mailing list -- people hide their
true domain name from the list but of course the information is public
and available from every DNS server in the world... heh heh).


On Tue, Aug 07, 2001 at 09:48:18PM -0600, Justin wrote:
> I am having problems getting my reverse dns to work with a block of ip 
> address's that I use. They were delegated by an ISP and the forward 
> lookups are working just fine. The dns server is configured correctly 
> with a "xxx.xxx.xxx.in-addr.arpa" zone and reverse lookups work fine if 
> we query that server. But, if we make reverse queries using any other 
> dns server the ip does not resolve. Is there anything special that 
> needs to be done in order to get the reverse dns to work correctly? I 
> know when I had Qwest as an ISP I had to fill out a webform for reverse 
> dns to work properly, as well as have my own reverse zone. Thanks in 
> advance for any help.
> 
> Justin
> 
> -----
> glow at jackmoves.com
> www.jackmoves.com
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.



More information about the LUG mailing list