Delegating an in-addr.arpa domain to myself (cheating, I know!)

[Barry Margolin]

In article <386a8a4a.30406275 at news.earthlink.net>,
Mark Landin <m555 at earthlink.net> wrote:
>Reading the O'Reilly DNS and BIND book leads me to believe that my
>problem is that the 1.1.192.in-addr.arpa domain isn't delegated right.
>They say to send a delegation request to the InterNIC. Obviously,
>that's not appropriate in my case, since someone else has already been
>delegated that domain. (nslookup is probably trying to contact a name
>server at the "real" 192.1.1.11, and there isn't one there ... even if
>there is that's not the one I want to talk to!)
>
>So how can I delegate that domain to myself internally? I tried
>putting this in my db. file:
>
>1.1.192.in-addr.arpa.		IN NS	locutus.eng.tdwilliamson.com.
>
>But it complained that 1.1.192.in-addr.arpa wasn't in my zone
>(tdwilliamson.com) which of course is isn't.
>
>What can I do to fix this? Is it possible? 

You don't need to delegate it, just make your server primary for the
domain.  Create a zone file containing the 1.1.192.in-addr.arpa domain, and
list it in your named.boot file:

primary 1.1.192.in-addr.arpa db.192.1.1 

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, 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.