Reverse DNS errors?

Barry Margolin barmar at bbnplanet.com
Tue Nov 30 15:28:23 UTC 1999


In article <3843D129.F5C7D357 at techdreams.com>,
Vince  <ice at techdreams.com> wrote:
>ok now in 67.92.204.in-addr.arpa I have the following....
>
>$TTL 43200
>@ IN SOA ns.techdreams.com. support.techdreams.com. (
>   1999112309 ; serial
>   3600 ; refresh
>   900 ; retry
>   1209600 ; expire
>   43200 ; default_ttl
>   )
>@  IN PTR ns.netonduty.com.
>@  IN NS ns.techdreams.com.
>;
>; techdreams Reverse mappings
>;
>50.67.92.204    IN      PTR     ns.techdreams.com.
>50.67.92.204    IN      PTR     www.techdreams.com.
>50.67.92.204    IN      PTR     ftp.techdreams.com.
>50.67.92.204    IN      PTR     mail.techdreams.com.

Since the origin for this zone file is 67.92.204.in-addr.arpa, this is
creating PTR records named 50.67.92.204.67.92.204.in-addr.arpa.  Is this
what you intended?  I don't think so.

You can fix this by changing those lines to:

50 IN PTR ...

or

50.67.92.204.in-addr.arpa.  IN PTR ...

(don't forget the trailing "." in "arpa.") or by putting:

$ORIGIN in-addr.arpa.

before the PTR lines.

-- 
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.


More information about the bind-users mailing list