Fedora Core 5 - not updating DNS/web

[rajclark]

Hi there,

I'm experimenting with FC5 as a host for ISP config. I've gone to FC5 because the Fedora folks have done a decent job of integrating Xen and support the cluster tools (GFS). I ultimately want to build a cluster of Xen hosts to support fail over and have tried many other distros without much luck...

Anyhow; I hacked the dist.txt file and made a new entry for FC5 to skip the checks it was doing and it all now seems to have installed and the Web UI is running. I can do the things I'd done previously with it under SuSE except that it doesn't actually seem to have created the DNS zone files for the domains I create, modified the named.conf (chrooted Bind) or added anything to the virtual hosts.

It sounds like a permissions problem, but ISPConfig seems to be runnign as root. I've looked for logs around the place, but haven't found anything that might give me a clue about the problem. Can someone pleae point me at a log file or debug setting that might let me know what's not working?

I have SELINUX off, but it wasn't complaining about modifying files anyway...

Thanks!

Tony

[falko]

What's in your named.conf now?
What happens if you start or restart BIND manually? Anything in the log files (in /var/log)?

[rajclark]

Hi there,

named.conf (from the chroot directory):

[root@bleem etc]# cat named.conf
//
// named.conf for Red Hat caching-nameserver
//

options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};

//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};

zone "." IN {
type hint;
file "named.ca";
};

zone "localdomain" IN {
type master;
file "localdomain.zone";
allow-update { none; };
};

zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};

zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 .0.0.0.0.0.0.ip6.arpa" IN {
type master;
file "named.ip6.local";
allow-update { none; };
};

zone "255.in-addr.arpa" IN {
type master;
file "named.broadcast";
allow-update { none; };
};

zone "0.in-addr.arpa" IN {
type master;
file "named.zero";
allow-update { none; };
};

include "/etc/rndc.key";
;
From /var/log/messages on a restart:

Mar 26 20:29:58 bleem named[1671]: shutting down: flushing changes
Mar 26 20:29:58 bleem named[1671]: stopping command channel on 127.0.0.1#953
Mar 26 20:29:58 bleem named[1671]: no longer listening on 127.0.0.1#53
Mar 26 20:29:58 bleem named[1671]: no longer listening on 203.0.153.230#53
Mar 26 20:29:58 bleem named[1671]: exiting
Mar 26 20:30:01 bleem named[12982]: starting BIND 9.3.2 -u named -t /var/named/chroot
Mar 26 20:30:01 bleem named[12982]: found 1 CPU, using 1 worker thread
Mar 26 20:30:01 bleem named[12982]: loading configuration from '/etc/named.conf'
Mar 26 20:30:01 bleem named[12982]: listening on IPv4 interface lo, 127.0.0.1#53
Mar 26 20:30:01 bleem named[12982]: listening on IPv4 interface eth0, 203.0.153.230#53
Mar 26 20:30:01 bleem named[12982]: command channel listening on 127.0.0.1#953
Mar 26 20:30:01 bleem named[12982]: zone 0.in-addr.arpa/IN: loaded serial 42
Mar 26 20:30:01 bleem named[12982]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Mar 26 20:30:01 bleem named[12982]: zone 255.in-addr.arpa/IN: loaded serial 42
Mar 26 20:30:01 bleem named[12982]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
Mar 26 20:30:01 bleem named[12982]: zone localdomain/IN: loaded serial 42
Mar 26 20:30:01 bleem named[12982]: zone localhost/IN: loaded serial 42
Mar 26 20:30:01 bleem named[12982]: running

[till]

This named conf has not been written by ISPConfig.

Please check in ISPConfig under management > server > settings if the path to named.conf and the directory for the zone files are correct.

[rajclark]

Thanks for the quick responses; you need a weekend sometime though! You're correct that the paths are wrong in those settings, but setting them right has a couple of issues:

1) It still doesn't update the named config. I am, however seeing the following in the http log under /root/ispconfig/httpd/logs:

df: `/var/named/chroot/proc': Permission denied

which I trust has something to do with this as it happens when I try to commit a change to the DNS.

2) The Zonefiles Dir setting doesn't want to be changed in Server->Settings->DNS and stays at /etc/bind. As mine is chrooted, It doesn't like this and is, I expect, part of the problem...

Again; my thanks for your promptness with this!

Many thanks,

Tony

[till]

Did you get any errors during installation or did you insert / modify anything in the ISPConfig SQL database manually such as inserting a line in the isp_server table?

[rajclark]

No errors; I got through the errors which were related to things not being installed, but the last install was clean. I didn't insert anything into the database manually, but did have to run the install process a few times while I figured out which requirements wheren't installed.

I appreciate your time on this; I know I'm on an unsupported platform and shouldn't expect anything !

Thanks,

Tony

[rajclark]

More on this; I looked at the other thread with dns issues and peeked into the log file. I saw:
27.03.2006 - 17:34:56 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_system.lib.php, Line 696: /etc/rc.d/init.d/named restart &> /dev/null
27.03.2006 - 17:34:56 => WARN - /root/ispconfig/scripts/lib/classes/ispconfig_system.lib.php, Line 696: WARNING: could not /etc/rc.d/init.d/ restart &> /dev/null


So it's having issues restarting, but isn't modifying the files anyway.

Tony

[falko]

Originally Posted by rajclark

2) The Zonefiles Dir setting doesn't want to be changed in Server->Settings->DNS and stays at /etc/bind. As mine is chrooted, It doesn't like this and is, I expect, part of the problem...

Have a look at post #7 in this thread: http://www.howtoforge.com/forums/showthread.php?t=3359