Mailinglist Archive: opensuse (4344 mails)
| < Previous | Next > |
RE: [SLE] weird named process
- From: "Ivan Mojzis" <ivan@xxxxxxxxxx>
- Date: Mon, 1 Aug 2005 21:39:27 +0200
- Message-id: <0fb201c596d0$bafc5470$0b01a8c0@xxxxxxxxxxxxxxxxx>
Config files in- and outside of jail are exactly the same. I found nothong
suspicious in logs.
boot.msg says:<notice>startproc: execve (/usr/sbin/named) [
/usr/sbin/named -t /var/lib/named -u named ], [ CONSOLE=/dev/console
TERM=linux SHELL=/bin/sh INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1
COLUMNS=99 PATH=/sbin:/usr/sbin:/bin:/usr/bin vga=0x314 RUNLEVEL=5 PWD=/
SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-800x600.cfg
PREVLEVEL=N LINES=33 checkAndCopyConfigFilesCalled=yes HOME=/ SHLVL=2
namedConfChecked=yes splash=silent SPLASH=yes initializeNamedCalled=yes
_=/sbin/startproc DAEMON=/usr/sbin/named ]
Starting name server BIND done
/var/log/messages
Jul 21 12:36:04 linux4seang named[4007]: starting BIND 9.2.4 -t
/var/lib/named -u named
Jul 21 12:36:04 linux4seang named[4007]: using 1 CPU
Jul 21 12:36:04 linux4seang named[4007]: loading configuration from
'/etc/named.conf'
Jul 21 12:36:04 linux4seang named[4007]: listening on IPv6 interfaces,
port 53
Jul 21 12:36:04 linux4seang named[4007]: listening on IPv4 interface lo,
127.0.0.1#53
Jul 21 12:36:04 linux4seang named[4007]: binding TCP socket: address in
use
Jul 21 12:36:04 linux4seang named[4007]: listening on IPv4 interface eth0,
192.168.0.2#53
Jul 21 12:36:04 linux4seang named[4007]: binding TCP socket: address in
use
Jul 21 12:36:04 linux4seang named[4007]: listening on IPv4 interface eth1,
192.168.1.1#53
Jul 21 12:36:04 linux4seang named[4007]: binding TCP socket: address in
use
Jul 21 12:36:04 linux4seang named[4007]: command channel listening on
127.0.0.1#953
Jul 21 12:36:04 linux4seang named[4007]: command channel listening on
::1#953
Jul 21 12:36:04 linux4seang named[4007]: zone 0.0.127.in-addr.arpa/IN:
loaded serial 42
Jul 21 12:36:04 linux4seang named[4007]: zone 1.168.192.in-addr.arpa/IN:
loaded serial 2005061007
Jul 21 12:36:04 linux4seang named[4007]: zone localhost/IN: loaded serial
42
Jul 21 12:36:04 linux4seang named[4007]: zone aaa.sk/IN: loaded serial
2005071401
Jul 21 12:36:04 linux4seang named[4007]: zone bbb.sk/IN: loaded serial
2005071401
Jul 21 12:36:04 linux4seang named[4007]: zone ccc.sk/IN: loaded serial
2005061001
Jul 21 12:36:04 linux4seang named[4007]: zone ddd.sk/IN: loaded serial
2005061009
Jul 21 12:36:04 linux4seang named[4007]: zone aaa.sk/IN: loaded serial
2005072101
Jul 21 12:36:04 linux4seang named[4007]: zone bbb.sk/IN: loaded serial
2005072101
Jul 21 12:36:04 linux4seang named[4007]: zone ccc.sk/IN: loaded serial
2005072101
Jul 21 12:36:04 linux4seang named[4007]: zone ddd.sk/IN: loaded serial
2005072101
Jul 21 12:36:04 linux4seang named[4007]: running
Jul 21 12:36:04 linux4seang named[4007]: zone aaa.sk/IN: sending notifies
(serial 2005072101)
Jul 21 12:36:04 linux4seang named[4007]: zone ccc.sk/IN: sending notifies
(serial 2005072101)
Jul 21 12:36:04 linux4seang named[4007]: zone ddd.sk/IN: sending notifies
(serial 2005072101)
Jul 21 12:36:04 linux4seang named[4007]: zone bbb.sk/IN: sending notifies
(serial 2005072101)
Jul 21 12:36:19 linux4seang named[4007]: received notify for zone 'aaa.sk'
Jul 21 12:36:20 linux4seang named[4007]: received notify for zone 'ccc.sk'
Jul 21 12:36:20 linux4seang named[4007]: received notify for zone 'ddd.sk'
Jul 21 12:36:20 linux4seang named[4007]: received notify for zone 'bbb.sk'
/var/lib/named/log/named.log:
contains only records like this:
Jul 21 12:36:45.969 client 127.0.0.1#1047: query:
8.62.185.212.dnsbl.sorbs.net IN A
Thanks,
Ivan
-----Original Message-----
From: Marlier, Ian [mailto:ian.marlier@xxxxxxxxxxxxxxxxxxx]
Sent: Monday, August 01, 2005 9:03 PM
To: suse-linux-e@xxxxxxxx
Subject: RE: [SLE] weird named process
> Hi all,
> has anyone experienced (and solved) two strange problems described
bellow
> with SuSE Linux 9.2 ?
> - first - named process doesnt't resolve queries from internal
network
> after clean reboot of machine - machne acts like internet
> gateway+mailserver, has 1 internal and 1 external interface. named
uses
> configuration with view statement in named.conf to answer in different
> manner queries from inside and outside. Just logging in as root and
> issuing rcnamed restart solves the problem but WHY ?
I've had problems with named a couple of times. Both times it turned
out that the problem was the chroot jail, and the conf files
(/etc/named.conf and /var/lib/named/etc/named.conf) not being identical.
It's something to think about, at least.
(The first time that it happened, I just copied /etc/named.conf to
/var/lib/named/etc/named.conf, and then rebooted the machine. Named
came up properly at boot time after that.)
Also, is named logging anything to any of these when it tries to start:
/var/log/boot.msg
/var/log/messages
/var/lib/named/log/named.log
?
- Ian
> Thanks.
>
> Ivan Mojzis
> Slovak Repiblic
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx
__________ Informacia od NOD32 1.1184 (20050801) __________
Tato sprava bola preverena antivirusovym systemom NOD32.
http://www.eset.sk
suspicious in logs.
boot.msg says:<notice>startproc: execve (/usr/sbin/named) [
/usr/sbin/named -t /var/lib/named -u named ], [ CONSOLE=/dev/console
TERM=linux SHELL=/bin/sh INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1
COLUMNS=99 PATH=/sbin:/usr/sbin:/bin:/usr/bin vga=0x314 RUNLEVEL=5 PWD=/
SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-800x600.cfg
PREVLEVEL=N LINES=33 checkAndCopyConfigFilesCalled=yes HOME=/ SHLVL=2
namedConfChecked=yes splash=silent SPLASH=yes initializeNamedCalled=yes
_=/sbin/startproc DAEMON=/usr/sbin/named ]
Starting name server BIND done
/var/log/messages
Jul 21 12:36:04 linux4seang named[4007]: starting BIND 9.2.4 -t
/var/lib/named -u named
Jul 21 12:36:04 linux4seang named[4007]: using 1 CPU
Jul 21 12:36:04 linux4seang named[4007]: loading configuration from
'/etc/named.conf'
Jul 21 12:36:04 linux4seang named[4007]: listening on IPv6 interfaces,
port 53
Jul 21 12:36:04 linux4seang named[4007]: listening on IPv4 interface lo,
127.0.0.1#53
Jul 21 12:36:04 linux4seang named[4007]: binding TCP socket: address in
use
Jul 21 12:36:04 linux4seang named[4007]: listening on IPv4 interface eth0,
192.168.0.2#53
Jul 21 12:36:04 linux4seang named[4007]: binding TCP socket: address in
use
Jul 21 12:36:04 linux4seang named[4007]: listening on IPv4 interface eth1,
192.168.1.1#53
Jul 21 12:36:04 linux4seang named[4007]: binding TCP socket: address in
use
Jul 21 12:36:04 linux4seang named[4007]: command channel listening on
127.0.0.1#953
Jul 21 12:36:04 linux4seang named[4007]: command channel listening on
::1#953
Jul 21 12:36:04 linux4seang named[4007]: zone 0.0.127.in-addr.arpa/IN:
loaded serial 42
Jul 21 12:36:04 linux4seang named[4007]: zone 1.168.192.in-addr.arpa/IN:
loaded serial 2005061007
Jul 21 12:36:04 linux4seang named[4007]: zone localhost/IN: loaded serial
42
Jul 21 12:36:04 linux4seang named[4007]: zone aaa.sk/IN: loaded serial
2005071401
Jul 21 12:36:04 linux4seang named[4007]: zone bbb.sk/IN: loaded serial
2005071401
Jul 21 12:36:04 linux4seang named[4007]: zone ccc.sk/IN: loaded serial
2005061001
Jul 21 12:36:04 linux4seang named[4007]: zone ddd.sk/IN: loaded serial
2005061009
Jul 21 12:36:04 linux4seang named[4007]: zone aaa.sk/IN: loaded serial
2005072101
Jul 21 12:36:04 linux4seang named[4007]: zone bbb.sk/IN: loaded serial
2005072101
Jul 21 12:36:04 linux4seang named[4007]: zone ccc.sk/IN: loaded serial
2005072101
Jul 21 12:36:04 linux4seang named[4007]: zone ddd.sk/IN: loaded serial
2005072101
Jul 21 12:36:04 linux4seang named[4007]: running
Jul 21 12:36:04 linux4seang named[4007]: zone aaa.sk/IN: sending notifies
(serial 2005072101)
Jul 21 12:36:04 linux4seang named[4007]: zone ccc.sk/IN: sending notifies
(serial 2005072101)
Jul 21 12:36:04 linux4seang named[4007]: zone ddd.sk/IN: sending notifies
(serial 2005072101)
Jul 21 12:36:04 linux4seang named[4007]: zone bbb.sk/IN: sending notifies
(serial 2005072101)
Jul 21 12:36:19 linux4seang named[4007]: received notify for zone 'aaa.sk'
Jul 21 12:36:20 linux4seang named[4007]: received notify for zone 'ccc.sk'
Jul 21 12:36:20 linux4seang named[4007]: received notify for zone 'ddd.sk'
Jul 21 12:36:20 linux4seang named[4007]: received notify for zone 'bbb.sk'
/var/lib/named/log/named.log:
contains only records like this:
Jul 21 12:36:45.969 client 127.0.0.1#1047: query:
8.62.185.212.dnsbl.sorbs.net IN A
Thanks,
Ivan
-----Original Message-----
From: Marlier, Ian [mailto:ian.marlier@xxxxxxxxxxxxxxxxxxx]
Sent: Monday, August 01, 2005 9:03 PM
To: suse-linux-e@xxxxxxxx
Subject: RE: [SLE] weird named process
> Hi all,
> has anyone experienced (and solved) two strange problems described
bellow
> with SuSE Linux 9.2 ?
> - first - named process doesnt't resolve queries from internal
network
> after clean reboot of machine - machne acts like internet
> gateway+mailserver, has 1 internal and 1 external interface. named
uses
> configuration with view statement in named.conf to answer in different
> manner queries from inside and outside. Just logging in as root and
> issuing rcnamed restart solves the problem but WHY ?
I've had problems with named a couple of times. Both times it turned
out that the problem was the chroot jail, and the conf files
(/etc/named.conf and /var/lib/named/etc/named.conf) not being identical.
It's something to think about, at least.
(The first time that it happened, I just copied /etc/named.conf to
/var/lib/named/etc/named.conf, and then rebooted the machine. Named
came up properly at boot time after that.)
Also, is named logging anything to any of these when it tries to start:
/var/log/boot.msg
/var/log/messages
/var/lib/named/log/named.log
?
- Ian
> Thanks.
>
> Ivan Mojzis
> Slovak Repiblic
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx
__________ Informacia od NOD32 1.1184 (20050801) __________
Tato sprava bola preverena antivirusovym systemom NOD32.
http://www.eset.sk
| < Previous | Next > |