I found a solution, however, I do not know why it was a reason: I cleared the file: -rw-r--r-- 1 root root 2147483647 Dec 25 23:37 secondary.xxx.com.tw Is the file size of 2 G the maximum? I thought 4 G bye Ronald Wiplinger LDB wrote:
Ronald Wiplinger wrote:
LDB wrote:
Ronald Wiplinger wrote:
On one machine I got some DNS troubles. I start dns, but it is not running without any reasons! Can you please give me a hand?
# /etc/rc.d/named stop;/etc/rc.d/named start;/etc/rc.d/named status Shutting down name server bind9 - Warning: named not running ! done Starting name server bind9 done Checking for nameserver bind9 running
# ps ax |grep name returns empty
# tail /var/log/messages
Dec 26 18:03:50 dns /usr/sbin/named[2111]: starting BIND 9.1.3 Dec 26 18:03:50 dns /usr/sbin/named[2111]: using 1 CPU Dec 26 18:03:50 dns /usr/sbin/named[2113]: loading configuration from '/etc/named.conf' Dec 26 18:03:50 dns /usr/sbin/named[2113]: zone '0.168.192.in-addr.arpa' allows updates by IP address, which is insecure Dec 26 18:03:50 dns /usr/sbin/named[2113]: zone 'xxx.com.tw' allows updates by IP address, which is insecure Dec 26 18:03:50 dns /usr/sbin/named[2113]: zone 'xxxx.com' allows updates by IP address, which is insecure Dec 26 18:03:50 dns /usr/sbin/named[2113]: set maximum open files to -1: permission denied Dec 26 18:03:50 dns /usr/sbin/named[2113]: listening on IPv4 interface lo, 127.0.0.1#53 Dec 26 18:03:50 dns /usr/sbin/named[2113]: listening on IPv4 interface eth0, xx.218.36.50#53 Dec 26 18:03:50 dns /usr/sbin/named[2113]: listening on IPv4 interface eth1, 192.168.0.254#53 Dec 26 18:03:50 dns /usr/sbin/named[2113]: running
One more time in single steps:
dns:~ # /etc/rc.d/named stop Shutting down name server bind9 - Warning: named not running ! done dns:~ # /etc/rc.d/named start Starting name server bind9 done dns:~ # /etc/rc.d/named status Checking for nameserver bind9 dead dns:~ #
Why? How to track it down?
bye
Ronald Wiplinger
Try starting it in the foreground on the commandline to ensure you are seeing everything.
bash> /usr/sbin/named -d 10 -t /var/lib/named -u named
That did not change anything, but I found I got a core.xxxx files everytime. I had never to deal with that, what do I do next?
bye
Ronald Wiplinger
do you mind sharing your /etc/named.conf file with me?
Thanks,
LDB
-- Ronald Wiplinger (CEO of ELMIT) http://www.elmit.com http://voip.elmit.com http://e-paper.elmit.com Tel. (M) +886.939.775.516 (O) +886.2.2835.7765 (ENUM) or FWD 511208 - I'm a SpamCon Foundation Member, #694, Verify it at http://www.spamcon.org PS: Spam prevention! Our system is protected with a spam prevention program. If you send us an e-mail, our system will send you a confirmation message back. Just reply to this confirmation message please. After receiving this confirmation message, our system will send the hold message (one) and all future messages (after the received confirmation message) to me without asking you again.