View Single Post
  #10  
Old 9th February 2009, 00:39
bobwdn bobwdn is offline
Member
 
Join Date: Dec 2006
Location: Nashville, Tennessee, USA
Posts: 50
Thanks: 7
Thanked 0 Times in 0 Posts
Default waht I found

After running /etc/init.d/bind9 restart as root I get:
Code:
Feb  8 16:23:48 web02 named[5287]: starting BIND 9.4.2-P2 -u bind -t /var/lib/named
Feb  8 16:23:48 web02 named[5287]: found 1 CPU, using 1 worker thread
Feb  8 16:23:48 web02 named[5287]: loading configuration from '/etc/bind/named.conf'
Feb  8 16:23:48 web02 named[5287]: /etc/bind/named.conf:43: zone 'firstdomain.com': already exists previous definition: /etc/bind/named.conf:37
Feb  8 16:23:48 web02 named[5287]: loading configuration: failure
Feb  8 16:23:48 web02 named[5287]: exiting (due to fatal error)
Then. to answer you, I did
Code:
locate named.conf
/root/ispconfig/isp/conf/named.conf.master
/usr/share/man/man5/named.conf.5.gz
/var/lib/named/etc/bind/named.conf
/var/lib/named/etc/bind/named.conf.local
/var/lib/named/etc/bind/named.conf.options
/var/lib/named/etc/bind/named.conf~
Then:

Code:
cat /var/lib/named/etc/bind/named.conf
options {
        pid-file "/var/run/bind/run/named.pid";
        directory "/etc/bind";
        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 "db.root";
};

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


zone "firstdomain.com" {
        type master;
        file "pri.firstdomain.com";
};
zone "webmail1.firstdomain.com" {
        type master;
        file "pri.webmail1.firstdomain.com";
};
zone "seconddomain.com" {
        type master;
        file "pri.seconddomain.com";
};


zone "seconddomain.com" {
        type slave;
        file "sec.seconddomain.com";
        masters { 192.168.5.102; };
};


//// MAKE MANUAL ENTRIES BELOW THIS LINE! ////
And finally, as far as exactly what happened when bind stopped, I am not sure. I do know it is about the same time as my dns nameserver entry corrected on my domain provider (GoDaddy.) Because my original website (that worked before I moved to GoDaddy) returned to our www.firstdomain.com address.

I am sorry, I have been ill and it has been a couple of days since bind9 stopped. Is there some way to look back in the log file to see?
Reply With Quote