Way back when I was setting up the firewall here at the office,
I set up the DNS stuff like this:
o Internal servers for bluetree.ie and 3.168.192.in-addr.arpa
on server1 and server2.
o External server for bluetree.ie on firewall.
o Clients on firewall use internal servers (by specifying server1
and server2 in /etc/resolv.conf).
o Internal servers use firewall server as a forwarder.
I also determined that I needed to make the firewall DNS server
authoritative for 3.168.192.in-addr.arpa, so I made it a slave
for this domain and used access control measures to ensure
that external hosts can't query it.
But... I can't remember why I needed to make the firewall
server authoritative for the internal reverse lookups. It must
have been a fairly obvious reason, because I didn't make a
note of it anywhere :-(
Current theory is that that part of my memory has been
over-written by stuff on COM threading models... Bummer!
Any ideas, anyone?
Later,
Kenn
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!
