Re: DNS-SD and Dynamic Updates

15 msg	NSEC3 support for BIND
4 msg	interface-interval
5 msg	Subnetted Reverse DNS - Going crazy
17 msg	help with bind
2 msg	Secondary NS on Windows and Linux Bind
2 msg	Re: L.ROOT-SERVERS.NET has changed IP address t...
1 msg	[SOLVED] (Was: Re: [FreeBSD 7.0-BETA1] strange ...
2 msg	[FreeBSD 7.0-BETA1] strange behavior in hostnam...
2 msg	BIND/DLZ/MYSQL
9 msg	BIND 9.4.x empty zones
7 msg	named slow resolving to internet
8 msg	named hangs
3 msg	Timed out while zone transfer
3 msg	named-checkzone 9.4.1-P1 appears to treat 'out ...
4 msg	host from BIND 9.4.1-P1 is confused by multiple...

DNS-SD and Dynamic Updates
\ Nathan Merritt (30 Oct 2007)
. \ Mark Andrews (30 Oct 2007)
. . \ Nathan Merritt (2 Nov 2007)

2 msg	forwarder {};
2 msg	SMP and 9.4.1-P1
2 msg	Bind 9.4.1-P1 allowing ddns running on Linux an...
3 msg	Why named bind(2)s 0.0.0.0 and :: adresses?

Subject:	Re: DNS-SD and Dynamic Updates
Group:	Bind-users
From:	Mark Andrews
Date:	30 Oct 2007

> Hey everybody -
> I'm running Bind 9.3.4 (-2etch1) on Debian with kernel version 2.6.18-4.
> I've been trying to set up DNS-SD on our production servers and have ran
> into a snag. There are two slave servers, two caches and a master
> authoritative server. I enabled update-forwarding on the caches and slaves
> to the master, and set up a key based authentication system. When I actually
> try to test things out via nsupdate, I get the following error server side:
>
> named[3975]: socket.c :1898: unexpected error:
> named[3975]: internal_accept: fcntl() failed: Too many open files
> named[3975]: zone bonjour.bowdoin.edu/IN/default : could not forward dynamic
> update to 10.140.226.26#53: unexpected error
>
> A quick googling pointed me to another user with a similar unresolved
> problem.
>
> http://readlist.com/lists/isc.org/bind-users/0/4480.html

No. That is a completely different problem.

> Anyone figure out what was going wrong between then and now?
>
> Thanks so much,
> Nathan Merritt

You have to many file descriptors open.

Are you running lots of virtual interfaces on this box?
Named uses 2 descriptors per interface (1 UDP and 1 TCP)

Assuming this is the problem limit the number of descriptors
named listens on (see listen-on and listen-on-v6).

Otherwise you have lots of incoming TCP connections
see tcp-clients.

Otherwise you have lots of simultious zone transfers
see transfers-per-ns, transfers-in, transfers-out.

Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews