BIND configuration - superior wisdom required.

James Herbert lists at
Sun Dec 19 19:15:20 UTC 2004


First off, if this is a FAQ, I'm most apologetic. The docs I looked at 
didn't really answer me, and I don't grok BIND yet.

Ok. My current situation is this:

I have a small internal network, and a smaller external 
network 217.155.x.168/29. I have just installed my sixth system on the 
network and have thus moved over to the internal NAT'ed network so as 
not to run out of address space. My servers have bidirectional mapping 
through the NAT box (OpenBSD/pf) such that 217.155.x.169 <-> 
and so on. Now this works great, except for the obvious problem that 
internal clients are still getting the external IP addresses of my 
servers from my ISP's DNS servers.

What I'd like BIND to do for me is this:

Be a DNS server for my internal network. It needs to answer only to my 
internal network, and reply to queries for servers on the internal 
network with their internal IP addresses, and forward everything else to 
my ISP's DNS servers.

I've looked at views, split-horizon, forwarding, caching, but I'm a bit 
lost. If someone could point me in the right direction by firstly 
telling me if I've got the right idea, and secondly telling me what I 
should be configuring BIND to do, that would be wonderful. I'm using 
BIND 9.2.3.



No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.0 - Release Date: 17/12/2004

More information about the bind-users mailing list