Michael Nottebrock wrote:
> On Tuesday, 17. July 2007, Heiko Wundram (Beenic) wrote:
>> This is natural, unless you specifically enter the zones for 192.168.8.*
>> (forward and reverse) in your client DNS server (as slave or forward zones,
>> see the bind manual for the latter, which I'd recommend in your case).
Yes, this is the right answer. Thanks Heiko for providing it. BIND
always takes more specific zone definitions first before less specific
ones. So if using your example you set a zone for
8.168.192.in-addr.arpa named will first look up names in that zone,
and anything else in 168.192.in-addr.arpa that isn't in that zone will
get the local NXDOMAIN answer. Same rules apply for forward zones of
course (to named there is no difference, a zone is a zone).
I think this issue probably deserves a comment in the named.conf file.
I'll prepare a patch and send it to [EMAIL PROTECTED]
> Ah, I'm (re)-learning more about DNS here than I ever thought I would.
> Indeed,
> with forward and reverse slave zones, I don't need to comment out anything
> anymore from the default config. I guess that solves my problems and the list
> audience will be saved from yet more DNS talk. :)
Heh, well I'm glad it worked out for you, and I'm sorry I missed your
initial message, I could have saved a lot of drama if I'd left the
office 15 minutes later. :)
Doug
--
This .signature sanitized for your protection
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
