Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
Did you check about named already running? The following bit of you error message
Code:
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.
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
Quote:
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.
};
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{};
};
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.