Okay, I cannot take it any more.

[Barry Margolin]

In article <20000526102858.A21077 at hydra.entire-systems.com>,
Daniel Roesen  <droesen at entire-systems.com> wrote:
>On Thu, May 25, 2000 at 10:16:25PM -0500, Marcus Kennedy wrote:
>> The first thing is that I am not a full class C network.  I am a
>> branch of Cable One of Alabama.  This, I fear is part of my problem.
>
>No. This has nothing to do with forward resolving, just with reverse.
>
>> I cannot determine if they have correctly broken me off in their DNS
>> server.
>
>No, they did it utterly wrong.
>
>; <<>> DiG 8.2 <<>> @ns1.cableone.net. 222.15.116.24.in-addr.arpa. any +norec
>[...]
>;; AUTHORITY SECTION:
>222.15.116.24.in-addr.arpa.  23h59m23s
>   IN NS dns0.ancdf.org.15.116.24.in-addr.arpa.
>
>They obviously don't understand RFC2317 (Classless DNS Reverse Delegation).

It looks like they chose *not* to use RFC 2317, but instead delegated each
IP address as a separate zone.  This is a valid mechanism, and not
unreasonable for tiny address blocks, but they screwed up and forgot to put
a "." at the end of the dns0.ancdf.org hostname in the delegation record.

This scheme is described in DNS & BIND on p.216, under "Solution 2".

To be compatible with this, on dns0.ancdf.org, you have to create separate
zones for each IP address in your block:

zone "216.15.116.24.in-addr.arpa" {
  type master;
  file "zone/24.116.15.222";
};
zone "217.15.116.24.in-addr.arpa" {
  type master;
  file "zone/24.116.15.223";
};
and so on.

zone/24.116.15.219 would look like:

@ IN SOA dns0.ancdf.org. postmaster.ancdf.org. (
    ...)
  IN NS  dns0.ancdf.org.
  IN PTR dns0.ancdf.org.

and the other zone/24.116.15.xxx files would be similar, except they would
have different names in their PTR records.

-- 
Barry Margolin, barmar at genuity.net
Genuity, 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.