thr3ads.net - nsd users - [nsd-users] nsd4b5: reply from unexpected source [Sep 2013]

If this information is useful, please help other people find it:
Share via:

Andreas Schulze

2013-Sep-26 15:32 UTC

[nsd-users] nsd4b5: reply from unexpected source

Hi,

I normally run nsd with fixed ip-addresses in nsd.conf.

Today I tried to remove all these addresses and nsd listen on INADDR_ANY.
but then I get errors while using secondary addresses:

# ip -4 addr show dev lo
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
       inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
       inet 127.0.0.53/8 brd 127.255.255.255 scope host secondary lo:53

# netstat -lnp | grep nsd
tcp        0      0 0.0.0.0:53              0.0.0.0:*                
LISTEN      18170/nsd
tcp        0      0 :::53                   :::*                     
LISTEN      18170/nsd
udp        0      0 0.0.0.0:53              0.0.0.0:*                   
          18170/nsd
udp        0      0 :::53                   :::*                        
          18170/nsd

# dig @127.0.0.1 hostname.bind -c CH -t txt +short
"example"

BUT:
# dig @127.0.0.53 hostname.bind -c CH -t txt +short
;; reply from unexpected source: 127.0.0.1#53, expected 127.0.0.53#53

I think, there was a similar discussion on nsd-users or unbound-users  
but found nothing here...

Reason behind this question is a redundancy problem. I have 2 server  
providing name-service.
The service-address is maintained by a keepalived. So sometimes when  
nsd try to start, the service-address
is located on the other host. listen to a specific address fail, nsd  
don't start :-(

For that reason I also tried the "ip-transparent" option.
But I get still: error: can't bind udp socket: Cannot assign requested
address

Any hints?

Andreas

Arjen Zonneveld

2013-Sep-27 07:17 UTC

head link

[nsd-users] nsd4b5: reply from unexpected source

Hi Andreas,


On 2013-09-26 17:32, Andreas Schulze wrote:>
> For that reason I also tried the "ip-transparent" option.
> But I get still: error: can't bind udp socket: Cannot assign requested
> addressOn which distribution and (kernel) version did you try this? I've found
that the setsockopt (IP_TRANSPARENT) option to make this possible, does
not work (acts as NOOP as far as I could tell) on 2.6.32-46-generic
(Ubuntu 10.04), while it does work as intended on 3.2.0-53-generic
(Ubuntu 12.04).

-- 
Met vriendelijke groet / Kind regards

Arjen Zonneveld
System Administrator

SIDN | Meander 501 | 6825 MD | P.O. Box 5022 | 6802 EA | Arnhem
T +31 (0)26 352 55 00
arjen.zonneveld at sidn.nl | www.sidn.nl

nsd users - Sep 2013 - nsd4b5: reply from unexpected source

[nsd-users] nsd4b5: reply from unexpected source

[nsd-users] nsd4b5: reply from unexpected source