Restricting allow-query for private network, permit for public?
Barry Margolin
barry.margolin at level3.com
Tue Aug 5 18:17:57 UTC 2003
In article <bgorev$1qk$1 at sf1.isc.org>,
Christian Fowler <google at N0SPAMgravesweeper.com> wrote:
>currently the nameserver happily serves out public IP's for foo.com and all
>it's hosts. I would like to add some 192.168.1.XXX hosts, however, I would
>like to restrict the ability to look up 192 hosts to the 192.168.1.0/24
>network. So the world can lookup www.foo.com and get a public IP, while only
>my internal network can lookup private.foo.com and get 192.168.1.4 - if a
>public request comes in for private.foo.com it won't work.
>
>I have submerged myself in the "BIND 9 Administrator Reference Manual" for
>hours and give up. Is such a thing even possible to do on the same nameserver
>or do I run two different named daemons w/ diff't named.conf's ?
Look in the section on "views".
--
Barry Margolin, barry.margolin at level3.com
Level(3), Woburn, 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.
More information about the bind-users
mailing list