|
|
 |  |
Re: Reverse DNS puzzleFrom: Craig Bowers Date: Wednesday, November 10, 1999
Time: 2:36:00 amOh good grief. A very large light goes on over my head. Previous ISP's had
delagated our range to us automatically, and I was failing to see the
obvious.
Thanks for the illumination.
Regards,
Craig Bowers
>-----Original Message-----
>From: quickdns-talk@lists.menandmice.com
>[mailto:quickdns-talk@lists.menandmice.com]On Behalf Of Men & Mice
>Support
>Sent: Tuesday, November 09, 1999 6:04 PM
>To: QuickDNS Talk
>Subject: Re: Reverse DNS puzzle
>
>
>>...but of more
>>concern is that it reports there are no PTR records for our
>machines with A
>>records. I don't get this. I had quickDNS pro create a reverse
>domain for
>>our whole IP range. Yet when I use an online Reverse DNS lookup
>it fails to
>>complete the reverse lookup, but is able to complete the reverse lookup on
>>some of the ISP's machines in the same IP range.
>
>[...]
>
>>148.249.13.216.in-addr.arpa. PTR www.caravel.bc.ca.
>
>The problem is that your ISP has control of the reverse zone. The
>fact that you have created a reverse zone file doesn't mean that a
>resolver will query your server for your addresses.
>
>Reverse queries are resolved just like domain queries, starting at
>the root servers. The root servers delegate the class C subnet to
>your ISP:
> 249.13.216.in-addr.arpa. NS ns1.metronet.ca.
> 249.13.216.in-addr.arpa. NS ns2.metronet.ca.
>
>Your provider can't delegate this reverse zone to you, because it's
>delegated to them (and besides which, they have some addresses in
>this range as well).
>
>Right now, a query to ns1.metronet.ca for 216.13.249.148 gives no
>records found. You need to prod your ISP into resolving this. They
>have two possible solutions:
>
>1) They can add PTR records for all of your addresses to their
>reverse zone file. If you ever add, remove, or rename a computer in
>your network, you'll need to have them change the reverse record.
>
> -- OR --
>
>2) They can delegate your part of the reverse zone using classless
>delegation (as described in RFC 2317
><http://www.faqs.org/rfcs/rfc2317.html>). This would give you direct
>control over your own reverse records. This type of delegation can be
>handled in a variety of ways; the most straightforward involves
>making a minor change to your existing reverse zone file. They would
>also have to create a number of records, but these records are very
>simple (and repetitive).
>
>If you or your ISP need any help understanding RFC 2317, just ask.
>____________________________________________________________________
>Chris Buxton cbuxton@menandmice.com
>Men & Mice http://www.menandmice.com
>Makers of: QuickDNS Pro
|

Return to Digital Point Solutions' Home Page |