Hello,
Note that DA only calls a "reload" not a full "restart" for new domains.
However, looking over the
named boot script for freebsd the reload done by DA will end up doing a full restart of named (which is fine).
So test with this to see if it's being restarted:
Code:
ps ax | grep named
/usr/local/etc/rc.d/named reload
ps ax | grep named
the PID number for named (on the far left) should be changing. Example, on our test system:
Code:
[root@freebsd7 /usr/local/etc/rc.d]# ps ax |grep named
77400 ?? Is 0:00.04 /usr/sbin/named -u bind
[root@freebsd7 /usr/local/etc/rc.d]# ./named reload
Stopping Named: [ OK ]
Starting Named: [ OK ]
[root@freebsd7 /usr/local/etc/rc.d]# ps ax |grep named
77424 ?? Ss 0:00.04 /usr/sbin/named -u bind
[root@freebsd7 /usr/local/etc/rc.d]#
Check the contents of your named boot script. Make sure it looks like this file:
http://www.directadmin.com/named.freebsd
Also check your system to see where your named.pid file is.
With our named boot script, it can be one of either:
/var/run/named.pid
/var/run/named/pid
Try deleting both of them (if they exist). Kill named manually, eg:
start it up, and see which one is created.
If it's located somewhere else, then the boot script won't see it, and named won't get restarted since the process id number won't be found by the script.
John
