 |  |
>Hello All,
Re: Setting up reverse domain for subnet only.
From: Men & Mice Support
Date: Thursday, August 12, 1999
Time: 12:22:00 pm
>
>Ok, I'm new at this, and since I don't have a whole block of
>addresses to myself, I've been given the ability to manage the
>reverse DNS for my subnet only. Which is kind of cool.
Hi Rob.
Your ISP has done something wrong. Tell him to reread RFC 2317, which is
available from <http://www.faqs.org/rfcs/rfc2317.html>, or just use my
example below (which follows the rules set forth in RFC 2317).
Here's what he's done:
128.41.201.209.in-addr.arpa. NS alice.netshak.com.
129.41.201.209.in-addr.arpa. NS alice.netshak.com.
130.41.201.209.in-addr.arpa. NS alice.netshak.com.
.
.
.
191.41.201.209.in-addr.arpa. NS alice.netshak.com.
His instructions to you (aside from the numeric error you noted) should
result in a zone file for 41.201.209.in-addr.arpa. that looks like this
(replacing namex with real hostnames):
41.201.209.in-addr.arpa. NS alice.netshak.com.
128.41.201.209.in-addr.arpa. PTR name1.netshak.com.
129.41.201.209.in-addr.arpa. PTR name2.netshak.com.
130.41.201.209.in-addr.arpa. PTR name3.netshak.com.
.
.
.
191.41.201.209.in-addr.arpa. PTR name64.netshak.com.
However, this method causes problems. Furthermore, there shouldn't be
entries for 128 and 191 - they're special, used by the subnet. Here's an
example of a legal way to do this:
His file:
128.41.201.209.in-addr.arpa. NS alice.netshak.com.
128.41.201.209.in-addr.arpa. NS ns.iconnet.net.
128.41.201.209.in-addr.arpa. NS ns2.teb1.iconnet.net.
129.41.201.209.in-addr.arpa. CNAME
129.128.41.201.209.in-addr.arpa.
130.41.201.209.in-addr.arpa. CNAME
130.128.41.201.209.in-addr.arpa.
131.41.201.209.in-addr.arpa. CNAME
131.128.41.201.209.in-addr.arpa.
.
.
.
190.41.201.209.in-addr.arpa. CNAME
190.128.41.201.209.in-addr.arpa.
Your file (zone name is 128.41.201.209.in-addr.arpa.):
128.41.201.209.in-addr.arpa. NS alice.netshak.com.
128.41.201.209.in-addr.arpa. NS ns.iconnet.net.
128.41.201.209.in-addr.arpa. NS ns2.teb1.iconnet.net.
129.128.41.201.209.in-addr.arpa. PTR name1.netshak.com.
130.128.41.201.209.in-addr.arpa. PTR name2.netshak.com.
131.128.41.201.209.in-addr.arpa. PTR name3.netshak.com.
.
.
.
190.128.41.201.209.in-addr.arpa. PTR name62.netshak.com.
Note the extra octet in the reversed addresses - this is because you're
using a subnet of the 209.201.41 network, not the whole class C. All of
this is explained in RFC 2317 (an internet standards document), but it's
one of those documents where, if you don't speak fluent technobabble, you
have no chance of deciphering it.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com http://www.menandmice.com
Messages In This Thread:
Return to Digital Point Solutions' Home Page