bind error

hi there,

i upgrade the bind with:
make PORT_REPLACES_BASE_BIND9=yes all install


but when i type

ndc start (or named)
it gave me:
ndc: error: name server has not started (yet?)

i whent to see the log file and look like this:

Apr 15 14:10:32 samaell named[10451]: starting BIND 9.2.2
Apr 15 14:10:32 samaell named[10451]: could not listen on UDP socket: address in use
Apr 15 14:10:32 samaell named[10451]: listening on IPv6 interfaces failed
Apr 15 14:10:32 samaell named[10451]: could not listen on UDP socket: address in use
Apr 15 14:10:32 samaell named[10451]: creating IPv4 interface xl0 failed; interface ignored
Apr 15 14:10:32 samaell named[10451]: could not listen on UDP socket: address in use
Apr 15 14:10:32 samaell named[10451]: creating IPv4 interface lo0 failed; interface ignored
Apr 15 14:10:32 samaell named[10451]: not listening on any interfaces
Apr 15 14:10:32 samaell named[10451]: /etc/namedb/rndc.key:6: unknown option 'options'
Apr 15 14:10:32 samaell named[10451]: couldn't add command channel 127.0.0.1#953: failure
Apr 15 14:10:32 samaell named[10451]: /etc/namedb/rndc.key:6: unknown option 'options'
Apr 15 14:10:32 samaell named[10451]: couldn't add command channel ::1#953: failure
Apr 15 14:10:32 samaell named[10451]: dns_master_load: localhost:18: ignoring out-of-zone data (localhost)
Apr 15 14:10:32 samaell named[10451]: dns_master_load: localhost:21: ignoring out-of-zone data (localhost)
Apr 15 14:10:32 samaell named[10451]: dns_master_load: localhost:23: ignoring out-of-zone data (1.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.0.ip6.int)
Apr 15 14:10:32 samaell named[10451]: localhost:23: file does not end with newline
Apr 15 14:10:32 samaell named[10451]: dns_master_load: localhost:18: ignoring out-of-zone data (localhost)
Apr 15 14:10:32 samaell named[10451]: dns_master_load: localhost:19: ignoring out-of-zone data (1.0.0.127.in-addr.arpa)
Apr 15 14:10:32 samaell named[10451]: dns_master_load: localhost:21: ignoring out-of-zone data (localhost)
Apr 15 14:10:32 samaell named[10451]: dns_master_load: localhost:23: ignoring out-of-zone data (1.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.0.ip6.int)
Apr 15 14:10:32 samaell named[10451]: localhost:23: file does not end with newline
Apr 15 14:10:32 samaell named[10451]: dns_master_load: localhost:19: ignoring out-of-zone data (1.0.0.127.in-addr.arpa)
Apr 15 14:10:32 samaell named[10451]: dns_master_load: localhost:23: ignoring out-of-zone data (1.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.0.ip6.int)
Apr 15 14:10:32 samaell named[10451]: localhost:23: file does not end with newline


What is append....

Please help me

Please don't double post....

http://www.linuxquestions.org/questi...threadid=55131

Jamie...

It sounds to me like you already have named running. After you did the upgrade to you check the contents of /etc/named.conf to check that it hasn't been over written?

What version of Bind did you upgrade from? The config files may not be exactly the same.

cheers

Jamie...

1º sorry about the double post

2º

I've upgrade from 8.3.3 to 9.2.2
I check the /etc/namd.conf but it looks like the same before the upgrade

What can i do now??

Did you check about named already running? The following bit of you error message

Apr 15 14:10:32 samaell named[10451]: could not listen on UDP socket: address in use
Apr 15 14:10:32 samaell named[10451]: listening on IPv6 interfaces failed
Apr 15 14:10:32 samaell named[10451]: could not listen on UDP socket: address in use
Apr 15 14:10:32 samaell named[10451]: creating IPv4 interface xl0 failed; interface ignored
Apr 15 14:10:32 samaell named[10451]: could not listen on UDP socket: address in use
Apr 15 14:10:32 samaell named[10451]: creating IPv4 interface lo0 failed; interface ignored
Apr 15 14:10:32 samaell named[10451]: not listening on any interfaces

suggests that you already have named running on your system and are attempting to start it again.

cheers

Jamie...

thanks for the your time.....

i try to restart the system without the
named_enable="yes"

and i dont have the dns,
but when i type de ndc start (only 1 time) it append again...

but the dns is now up...

It seems that he make named double??!!!

The problem is that i dont have any mesanger say that the dns is up


Help.............me
Thanks

So its started working now?? Are you sure your new version of Bind came with NCD and that you're not starting the old version?

cheers

Jamie...

Bind came with NCD ???
sorry i dont know what is it!!

i think iam starting the new version because this new have suport to ipv6 anwsers, and the old didnt have...

Sorry hcd should have read 'ndc' doh...

Jamie...

Soooo
Can i do anything??
is there a way to "kill" the old bind (if it still there)???

Originally posted by tandre Can i do anything??

It sounds like the new named isn't binding to the IPV4 interfaces for some reason, and that the IPV6 stuff is causing lots of errors

Originally posted by tandre is there a way to "kill" the old bind (if it still there)???

killall named, rm -rf /somePath/oldNamedBinary would do it, but it sounds like the new one is running. Post a copy of your named.conf and your zone files so we can have a look.

cheers

Jamie...

the named.conf looks like this:

options {
directory "/etc/namedb";
forwarders {
193.137.232.2;
// 2001:690:1fff:200:0000:0000:0000:2;

};
allow-query{any;};
listen-on-v6{any;};
/*
* 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;

/*
* If running in a sandbox, you may have to specify a different
* location for the dumpfile.
*/
// dump-file "s/named_dump.db";
};

zone "localhost" {
type master;
file "localhost";
#check-names fail;
allow-update{none;};
allow-transfer{any;};
allow-query{any;};
};

zone "." {
type hint;
file "named.root";
};

zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost";
allow-query{any;};
};

zone "1.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.INT" {
type master;
file "localhost";
#check-names fail;
allow-update{none;};
allow-transfer{any;};
allow-query{any;};
};

zone "d.3.2.0.9.6.0.1.0.0.2.IP6.INT" {
type master;
file "localhost-v6.ipg";
#check-names fail;
allow-update{none;};
allow-transfer{any;};
allow-query{any;};
also-notify{};
};
zone "ipv6.ipg.pt" {
type master;
file "ipv6.ipg.pt";
#check-names fail;
allow-update{none;};
allow-transfer{any;};
allow-query{any;};
also-notify{};
};

do u need the zone files

Unless you are on a research network somewhere, you are not using IPv6.

Disable it. I can't guarentee that this will fix anything, but it will cut down on the background noise enough to see what is actually broken.