|
|
 |  |
Re: Reverse DNSFrom: Men & Mice Support Date: Wednesday, December 5, 2001
Time: 1:01:47 amAt 10:31 PM -0800 12/4/01, Robert Ameeti wrote:
>>I have the following IP's delegated by my ISP to my DNS servers.
>>
>>Client 1
>>
>>209.91.118.144 - 209.91.118.151
>>207.148.164.200 - 207.148.164.207
>>
>>My ISP states:
>>
>>"Make sure that this Reverse DNS Zone is set up on your server:
>>200-29.164.148.207.in-addr.arpa"
>
>Where does the 200-29 come from in the above Reverse DNS? (I'm
>needing to do similar stuff)
>
>I see that 207.148.164.200 gets reversed to 164.148.207.in-addr.arpa
>but I don't understand the prefixed part.
This comes from the classless subnet delegation.
A classless subnet reverse zone has an arbitrary name. It doesn't
actually have to end in "in-addr.arpa.", though they usually do. The
name is assigned by the ISP or NSP, who presumably controls the
larger classed reverse zone where the "delegation" (which doesn't
actually have to be a real delegation) takes place.
Let me give some examples. Below are three different ways the given
subnet could have been delegated, showing what the ISP would have in
their 164.148.207.in-addr.arpa reverse zone.
1) The method used in this particular case:
200-29.164.148.207.in-addr.arpa. NS ns1.wavefront.ab.ca.
200-29.164.148.207.in-addr.arpa. NS ns2.wavefront.ab.ca.
201.164.148.207.in-addr.arpa. CNAME 201.200-29.164.148.207.in-addr.arpa.
202.164.148.207.in-addr.arpa. CNAME 202.200-29.164.148.207.in-addr.arpa.
203.164.148.207.in-addr.arpa. CNAME 203.200-29.164.148.207.in-addr.arpa.
204.164.148.207.in-addr.arpa. CNAME 204.200-29.164.148.207.in-addr.arpa.
205.164.148.207.in-addr.arpa. CNAME 205.200-29.164.148.207.in-addr.arpa.
206.164.148.207.in-addr.arpa. CNAME 206.200-29.164.148.207.in-addr.arpa.
2) A method that's perhaps a little easier to read:
wavefront.164.148.207.in-addr.arpa. NS ns1.wavefront.ab.ca.
wavefront.164.148.207.in-addr.arpa. NS ns2.wavefront.ab.ca.
201.164.148.207.in-addr.arpa. CNAME 201.wavefront.164.148.207.in-addr.arpa.
202.164.148.207.in-addr.arpa. CNAME 202.wavefront.164.148.207.in-addr.arpa.
203.164.148.207.in-addr.arpa. CNAME 203.wavefront.164.148.207.in-addr.arpa.
204.164.148.207.in-addr.arpa. CNAME 204.wavefront.164.148.207.in-addr.arpa.
205.164.148.207.in-addr.arpa. CNAME 205.wavefront.164.148.207.in-addr.arpa.
206.164.148.207.in-addr.arpa. CNAME 206.wavefront.164.148.207.in-addr.arpa.
3) A method that doesn't involve an actual delegation:
201.164.148.207.in-addr.arpa. CNAME 201.rev.wavefront.ab.ca.
202.164.148.207.in-addr.arpa. CNAME 202.rev.wavefront.ab.ca.
203.164.148.207.in-addr.arpa. CNAME 203.rev.wavefront.ab.ca.
204.164.148.207.in-addr.arpa. CNAME 204.rev.wavefront.ab.ca.
205.164.148.207.in-addr.arpa. CNAME 205.rev.wavefront.ab.ca.
206.164.148.207.in-addr.arpa. CNAME 206.rev.wavefront.ab.ca.
In fact, method 3 doesn't even require a reverse zone separate from
the forward zone - the PTR records can actually be entered right
alongside the A records.
____________________________________________________________________
Chris Buxton Men & Mice
support@menandmice.com Making DNS Easy
|
Messages In This Thread:- Reverse DNS by Warren Michelsen on Oct 30, 1999 at 5:41:00 pm
- Reverse DNS by Caio James on Jun 29, 2000 at 8:23:23 pm
- Reverse DNS by Paul Didzerekis on May 2, 2001 at 1:53:19 pm
- Reverse DNS by Andrew Schmiechen on Jun 21, 2001 at 1:28:00 pm
- reverse DNS by Paul Didzerekis on Jun 21, 2001 at 3:43:12 pm
- Reverse DNS by Dan Tappin on Dec 4, 2001 at 8:01:31 am
- reverse dns by Steve Nowacki on Jul 29, 2003 at 10:02:19 am
- Reverse DNS by Larry Scott Hastings on Feb 11, 2005 at 1:52:38 pm
|

Return to Digital Point Solutions' Home Page |