HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Installation/Configuration (http://www.howtoforge.com/forums/forumdisplay.php?f=16)
-   -   BIND-server problems (http://www.howtoforge.com/forums/showthread.php?t=15223)

NejcZ 31st August 2007 23:01

BIND-server problems
 
Hey, me again. I'm running Fedora core 5, perfect setup with IspConfig, for like 2 years now. My server was down last year, but now i got it online again. There's a problem, when i create any new domain. Bind just won't start.

Failed to start BIND : Starting named: Error in named configuration: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 zone 242.255.84.in-addr.arpa/IN: loaded serial 2007083104 zone nejcz.net/IN: loaded serial 2007082901 zone test.domain.com/IN: loading master file pri.test.domain.com: file not found _default/test.domain.com/IN: file not found [FAILED]

Last year everything worked well. Has anyone any ideas what could be wrong? Thanx in advance, Nejc!

till 1st September 2007 16:03

Do you have a domain test.domain.com in the dns-manager?

NejcZ 1st September 2007 16:10

Yes, i created it with ISPConfig DNS manager. nejcz.net was also created with dns manager and it works just fine. But when i create any other, bind just won't start.

falko 1st September 2007 22:23

What's in your named.conf? Are there any errors in your logs when BIND doesn't restart?

NejcZ 1st September 2007 22:54

Yep, like that

Quote:

Aug 31 22:00:01 localhost named[950]: exiting
Aug 31 22:00:03 localhost named: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Aug 31 22:00:03 localhost named: zone 242.255.84.in-addr.arpa/IN: loaded serial 2007083104
Aug 31 22:00:03 localhost named: zone nejcz.net/IN: loaded serial 2007082901
Aug 31 22:00:03 localhost named: zone test.domain.com/IN: loading master file pri.test.domain.com: file not found
Aug 31 22:00:03 localhost named: _default/test.domain.com/IN: file not found
Aug 31 22:00:11 localhost named: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Aug 31 22:00:11 localhost named: zone 242.255.84.in-addr.arpa/IN: loaded serial 2007083104
Aug 31 22:00:11 localhost named: zone nejcz.net/IN: loaded serial 2007082901
Aug 31 22:00:11 localhost named: zone test.domain.com/IN: loading master file pri.test.domain.com: file not found
Aug 31 22:00:11 localhost named: _default/test.domain.com/IN: file not found
Aug 31 22:00:26 localhost named[1568]: starting BIND 9.3.4 -u named -t /var/named/chroot
Aug 31 22:00:26 localhost named[1568]: found 1 CPU, using 1 worker thread
Aug 31 22:00:26 localhost named[1568]: loading configuration from '/etc/named.conf'
Aug 31 22:00:26 localhost named[1568]: listening on IPv4 interface lo, 127.0.0.1#53
Aug 31 22:00:26 localhost named[1568]: listening on IPv4 interface eth0, 192.168.2.101#53
Aug 31 22:00:26 localhost named[1568]: command channel listening on 127.0.0.1#953
Aug 31 22:00:26 localhost named[1568]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Aug 31 22:00:26 localhost named[1568]: zone 242.255.84.in-addr.arpa/IN: loaded serial 2007083105
Aug 31 22:00:26 localhost named[1568]: zone nejcz.net/IN: loaded serial 2007082901
Aug 31 22:00:26 localhost named[1568]: running
Aug 31 22:00:26 localhost named[1568]: zone 242.255.84.in-addr.arpa/IN: sending notifies (serial 2007083105)
Aug 31 22:00:26 localhost named[1568]: zone nejcz.net/IN: sending notifies (serial 2007082901)
Sep 1 21:50:16 localhost named[1568]: shutting down: flushing changes
Sep 1 21:50:16 localhost named[1568]: stopping command channel on 127.0.0.1#953
Sep 1 21:50:16 localhost named[1568]: no longer listening on 127.0.0.1#53
Sep 1 21:50:16 localhost named[1568]: no longer listening on 192.168.2.101#53
Sep 1 21:50:16 localhost named[1568]: exiting
Sep 1 21:50:19 localhost named: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Sep 1 21:50:19 localhost named: zone 242.255.84.in-addr.arpa/IN: loaded serial 2007083105
Sep 1 21:50:19 localhost named: zone 2.168.192.in-addr.arpa/IN: loading master file pri.2.168.192.in-addr.arpa: file not found
Sep 1 21:50:19 localhost named: _default/2.168.192.in-addr.arpa/IN: file not found
Sep 1 21:50:19 localhost named: zone nejcz.net/IN: loaded serial 2007082901
Sep 1 21:50:19 localhost named: zone test.domain.com/IN: loading master file pri.test.domain.com: file not found
Sep 1 21:50:19 localhost named: _default/test.domain.com/IN: file not found
Sep 1 21:50:40 localhost named: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Sep 1 21:50:40 localhost named: zone 242.255.84.in-addr.arpa/IN: loaded serial 2007083105
Sep 1 21:50:40 localhost named: zone 2.168.192.in-addr.arpa/IN: loading master file pri.2.168.192.in-addr.arpa: file not found
Sep 1 21:50:40 localhost named: _default/2.168.192.in-addr.arpa/IN: file not found
Sep 1 21:50:40 localhost named: zone nejcz.net/IN: loaded serial 2007082901
Sep 1 21:50:40 localhost named: zone test.domain.com/IN: loading master file pri.test.domain.com: file not found
Sep 1 21:50:40 localhost named: _default/test.domain.com/IN: file not found
named.conf

Quote:

options {
pid-file "/var/named/chroot/var/run/named/named.pid";
directory "/var/named";
auth-nxdomain no;
/*
* 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
//
zone "." {
type hint;
file "named.ca";
};

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

zone "242.255.84.in-addr.arpa" {
type master;
file "pri.242.255.84.in-addr.arpa";
};
zone "2.168.192.in-addr.arpa" {
type master;
file "pri.2.168.192.in-addr.arpa";
};


zone "nejcz.net" {
type master;
file "pri.nejcz.net";
};
zone "test.domain.com" {
type master;
file "pri.test.domain.com";
};



//// MAKE MANUAL ENTRIES BELOW THIS LINE! ////
key rndc-key {
algorithm hmac-md5;
secret "4zoFB7ZhhBE8+X7Ysp8lyQ==";
};
controls {
inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { rndc-key; };
};
zone "214.242.255.84.in-addr.arpa" {
type delegation-only;
};


till 2nd September 2007 12:07

Please try to delete the zone test.domain.com, wait a minute, empty the recycle bin and then recreate the zone to let ISPConfig create new config files for this zone.

NejcZ 2nd September 2007 12:17

I have tried that, but it didn't work. :confused:

till 2nd September 2007 12:31

Which bind config directory is set in ISPConfig under management > server > settings on the dns tab?

NejcZ 2nd September 2007 12:35

named.conf dir: /etc/named.conf
zonefiles dir: /var/named

till 2nd September 2007 13:52

Ok, thats fine.

Do you have any errors in the logfile:

/home/admispconfig/ispconfif/ispconfig.log


All times are GMT +2. The time now is 05:26.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.