On 05/03/11 12:56, Ronan Mullally wrote:
> Depending on the linux disto you've got you may well find zone files
> already there to do just that - making the server authoritative for
> these domains. Debian has a 'db.empty' file which I apply with:
>> zone "10.in-addr.arpa" { type master; file "/etc/bind/db.empty"; };
> ...
Thanks! When I was initially setting up bind on the SheevaPlug box
(running an ARM port of ubuntu 9.04), I'd added 20.168.192.in-addr.arpa
as a zone in /etc/bind/named.conf.local, and commented out
// Consider adding the 1918 zones here, if they are not used in your
// organization
// include "/etc/bind/zones.rfc1918";
since I figured I'm using one of them. I've uncommented the include so
it loads the zones.rfc1918 file which contains the exact approach you
describe above. With that, and a reload of bind, I can see that what
used to go up to the UPC servers are now properly handled internally.
At the same time, our local subnet names/addresses still resolve
correctly, which shows my initial worry which led me to commenting the
line out was a red herring.
Thanks a bunch!
B
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!