BIND DNS not updating

[mhamann]

Hello,

When I set up new domains within ispCP, I would expect BIND to be updated with the DNS settings for those domains, but yet it is not. In order to make anything work, I have to add the DNS records manually through Webmin or something. I followed the instructions here (http://www.isp-control.net/documentation...gure_bind) during installation.

Also, I have no file called "/etc/named-ispcp.conf". I think this is the last step before I have everything working properly, but I can't figure out what's preventing the DNS from being updated.

Can anyone help??

Thanks!

[edeis]

I am experiencing similiar problems on CentOS 5.4 with Omega1.0.5. I am missing /etc/named-ispcp.conf

[root@drizzle log]# cat /var/named/chroot/etc/named.conf
include "/etc/named-ispcp.conf";

[root@drizzle log]# cat /etc/named-ispcp.conf
cat: /etc/named-ispcp.conf: No such file or directory


The only thing that comes close is:
/etc/ispcp/bind/named.conf
But the contents are rather dismal:
// bind Data BEGIN.

// dmn [{DMN_NAME}] cfg entry BEGIN.
// dmn [{DMN_NAME}] cfg entry END.

// bind Data END.

[qubed]

same problem anyone have an idea??

[edeis]

I think it is okay. I checked and my DNS seems to be working correctly.

I think that the reference to the following include ....
[root@drizzle log]# cat /var/named/chroot/etc/named.conf
include "/etc/named-ispcp.conf";

Actually refers to this file:
/var/named/chroot/etc/named-ispcp.conf

Something to do with being chrooted. So it's not to worry. Can someone confirm this?

Also, tot sure what is the active config file for NAMED. Edited the following:
/var/named/chroot/etc/named-ispcp.conf
/etc/ispcp/bind/working/named.conf
This looks like it is part of the template that comprises it:
/etc/ispcp/bind/named.conf

If you want to edit the DNS entries manually for domains, you can find them here:
/var/named/data/domainname.db

[Illidan]

The named.conf is in /etc/bind/
There are zone entries for any domain and subdomain.

Information about alias, php and so on are in /etc/apache2/sites-available/ and /etc/apache2/sites-enabled/

But I think It won't work if you edit named.conf file manually. There are too many other files dependent on the domain settings.