I know all of the djbdns fans will attack me, but I set up a forwarding nameserver with the built-in BIND 9.3.1 version packaged with FreeBSD 5.4. I did give djbdns the old college try using the ports tree, but I had trouble getting daemontools and scvscan working in the time I allotted for the project. I was able to get BIND working strictly as a forwarding server using the following steps.
First I created a rndc.key file using rndc-confgen.
janney:/etc/namedb# rndc-confgen -a
wrote key file "/etc/namedb/rndc.key"
I created a /etc/named/rndc.conf file and copied the contents of /etc/namedb/rndc.key into rndc.conf, along with the entries shown below:
options {
default-server localhost;
default-key "rndc-key";
};
server localhost {
key "rndc-key";
};
key "rndc-key" {
algorithm hmac-md5;
secret "OBSCURED";
};
I then modified /etc/namedb/named.conf in the following ways.
listen-on { 127.0.0.1; 192.168.3.7;};
forward only;
forwarders {
192.168.2.1;
};
The first line tells BIND where to listen. The second tells BIND to only forward DNS requests. The third line tells BIND where to forward requests.
So what's the purpose of this setup? I am running BIND on a central system to which various remote sensors connect. All of them will be configured to ask DNS requests of this central system through an IPSec tunnel. None will make DNS requests on the client networks. This reduces the traffic caused by the sensor on the client network.
I had trouble setting up BIND using the configuration I outlined before. Specifically, BIND did not recognize the controls directive:
janney:/etc/namedb# named -g
28-Jun-2005 17:07:57.969 starting BIND 9.3.1 -g
28-Jun-2005 17:07:57.970 found 2 CPUs, using 2 worker threads
28-Jun-2005 17:07:57.986 loading configuration from '/etc/namedb/named.conf'
28-Jun-2005 17:07:57.987 /etc/namedb/named.conf:27: unknown option 'controls'
28-Jun-2005 17:07:57.991 loading configuration: failure
28-Jun-2005 17:07:57.991 exiting (due to fatal error)
I have no idea why this happened. Once I removed the controls section, everything worked. This is what I used for controls:
controls {
inet 127.0.0.1 allow { localhost; } keys { rndc-key; };
};
Comments on why this failed are appreciated.
0 komentar:
Posting Komentar