Sorry that this is turning into a hassle! I recognized that bind didn't have recursion turned off by default so I went to do this, setting one option in named.conf.options.
However, on reloading the zones I got some errors. After killing the named process completely and trying to start fresh, I got the following error. [EMAIL PROTECTED]:/etc/bind$ sudo -u bind /etc/init.d/bind9 start Starting domain name service: namedchmod: changing permissions of `/var/run/bind/run': Operation not permitted . Right now I can't resolve names from outside of the network or locally... bind seems to time out. I think it's probably just permissions since the daemon starts but I can't connect, however I'm not sure if it's a firewall rule or just the fact that bind can't write or chmod certain files that it wants to. Sorry again about the hassle. If anyone wants to try changing the permissions on /var/run/bind/run so that named can do what it needs to do with this file, I think that would be the first troubleshooting step. Next perhaps someone could try restarting the daemon process as I was, using sudo -u bind /etc/init.d/bind9 start, and then perhaps with a restart command to make sure that I will be able to do this in the future. "rndc reload" is the other command that I'll probably have to use frequently in order to make new changes take effect. _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
