Re: delegating in-addr.arpa.

[charles@lunarmedia.net]

i read through the classless doc, i think its rfc2317.
honestly, they take the same approach that you offered up as a solution,
meaning that it is done for each individual ip address. so, i have to
think that your method is the right way to do it.
the only thing that i have noticed, is that lookups insert a syslog entry
stating:

Feb 14 09:18:46 ns1 named[28352]: bad referral (200.168.192.in-addr.arpa
!< 45.200.168.192.in-addr.arpa) from [10.6.21.233].53

the only difference i see with the classless is that you end up setting up
cname records that end up pointing to the actual ptr rather than ns
records:

Default Server:  dns-1.enteract.com
Address:  207.229.143.1

> 216.1.105.226
Server:  dns-1.enteract.com
Address:  207.229.143.1

Name:    ns1.lunarmedia.net
Address:  216.1.105.226
Aliases:  226.105.1.216.in-addr.arpa





On Wed, 14 Feb 2001, Steven Pritchard wrote:

> charles@lunarmedia.net said:
> > I just expected an easier method of delegation rather than per ip address.
>
> Like I said, you can delegate a level higher, but that'll break things
> for recursive clients.
>
> If I remember correctly, there's an RFC on classless in-addr.arpa
> delegation...  Maybe they have better ideas.
>
> Steve
>

-
To unsubscribe, send email to majordomo@luci.org with
"unsubscribe luci-discuss" in the body.