Search Again:

Re: Reverse DNS Questions

From: Men & Mice Support
Date: Friday, May 28, 1999
Time: 12:21:00 am

>I have added another remote POP recently through a new provider. We have
>1/2 class C for the POP and I have setup the following reverse DNS for
>this /25
>
>Inverse Zone File name: 29.100.209.in-addr.arpa.
>
>29.100.209.in-addr.arpa. NS jer.mia.net.
>29.100.209.in-addr.arpa. NS ns.dslnet.com.
>29.100.209.in-addr.arpa. NS ns2.nap.net.
>129.29.100.209.in-addr.arpa. PTR
> mia-burlington-gateway.mia.net.
>179.29.100.209.in-addr.arpa. PTR pm3-179-burl4.mia.net.
>
>130.29.100.209.in-addr.arpa. PTR pm3-130-burl2.mia.net.
>
>131.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.131.mia.net.
>132.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.132.mia.net.
>133.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.133.mia.net.
>134.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.134.mia.net.
>135.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.135.mia.net.
>136.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.136.mia.net.
>137.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.137.mia.net.
>138.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.138.mia.net.
>139.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.139.mia.net.
>140.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.140.mia.net.
>141.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.141.mia.net.
>142.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.142.mia.net.
>143.29.100.209.in-addr.arpa. PTR
> 130-pm3-209.100.29.143.mia.net.
>"blah blah"
>"blah blah"
>"blah blah"
>254.29.100.209.in-addr.arpa. PTR pc1-alero.mia.net.
>
>
>I sent over the inverse zone file to my new upscale provider and asked
>that we be made authoratative for this block. Here is a copy of email I
>received from them today:
>
><snip>
>I have received your request to set up reverse lookups for the
>209.100.29.128
>network. Because you are running your own name server (jer.mia.net
>206.190.23.194) I can give you authority over your reverse lookups for
>your
>subnet. The procedure that I follow is RFC 2317
>(http://www.dns.net/dnsrd/rfc/rfc2317.html).
>
>Otherwise, I can set up the reverses as requested and leave them on
>ns.dslnet.com. Let me know what you would like to do.
></snip>

He sounds like he mostly knows what he's talking about.

>Have I configured something wrong in the in-addr.arpa. file? I am
>working with new provider for these services and my other providers have
>always understood my needs, and have never had trouble configuring this
>with them.
>
>Am I correctly following RFC 2317?

No. You shouldn't have a file for <29.100.209.in-addr.arpa.> at all -
that's your provider's job.

Fortunately, once he tells you how he wants to handle classless delegation,
you can just change the name of the zone (in the Domain Info dialog) to
have all your records corrected automatically.

If he's really following the example procedure in the RFC, the zone name
will be changed from <29.100.209.in-addr.arpa.> to
<128/25.29.100.209.in-addr.arpa.>.

>One of my providers currently creates a "shim domain" for my inverse dns
>which requires that I name may inverse files as follows:
>mia-1.xxx.xx.xxx.in-addr.arpa. , mia-2.xxx.xx.xxx.in-addr.arpa. , etc...
>
>If this makes sense please help shed some light on this... Thanx,

It does indeed make sense. If you feel comfortably fluent in technobabble,
you can try reading the RFC in question:
<ftp://NIC.MERIT.EDU/internet/documents/rfc/rfc2317.txt>.

Tell your provider you'd like to go ahead with classless delegation. After
he finishes setting up his end, query his name server for a CNAME record
for <129.29.100.209.in-addr.arpa.>. This will show you what zone name to
give your file.

If you need further help with this, just ask. It's not an easy thing to
understand (or to explain), but it's fairly easy to set up once you get it.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com http://www.menandmice.com



Messages In This Thread:



Return to Digital Point Solutions' Home Page