Package: nsd3
Version: 3.2.12-1
Severity: important
I ran across the same problem seemingly that this person
mentions here:
---
http://serverfault.com/questions/444354/nginx-and-nsd3-dont-start-on-boot-because-they-cannot-use-the-assigned-ip
The error I see in my nsd.log is:
---
[1354446740] nsd[2556]: error: can't bind udp socket: Cannot assign requested
address
[1354446740] nsd[2556]: error: server initialization failed, nsd could not be
started
as the most recent example.
This is happening for me on physical hardware (brand new Sandy
Bridge system), so it's definitely not isolated to VM's as is the case
in the aforementioned URL with the same problem.
It might not be a coincidence though that both that problem
report and my own system both seem to be using IPv6 in some form. I
can't tell from the error in nsd.log which interface nsd is failing to
bind to (I'm specifying one IPv4 and one IPv6 address in my nsd.conf
file, both configured on the same interface on my own system).
Anyway, simply starting nsd3 after boot has finished resolves
the issue. But it's obviously not working as intended the way it
behaves currently.
Let me know if I can help out in any other way.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages nsd3 depends on:
ii adduser 3.113+nmu3
ii libc6 2.13-35
ii libssl1.0.0 1.0.1c-4
ii lsb-base 4.1+Debian8
nsd3 recommends no packages.
nsd3 suggests no packages.
-- Configuration Files:
/etc/nsd3/nsd.conf.sample [Errno 13] Permission denied:
u'/etc/nsd3/nsd.conf.sample'
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
