Maintained by: NLnet Labs

[Unbound-users] Can't Bind Socket Error

Paul Stewart
Thu Oct 9 18:24:54 CEST 2014


Thanks Andreas....

We wanted to ensure that the system was "tuned" due to the amount of DNS
clients that would be using it.  Roughly 8,000 endpoints are querying the
pair of Unbound instances at this point.

I wasn't sure how "robust" the defaults were out of the box as our
experience with other types of software have always been that the default
configurations are for much smaller usage than what we need. 

Take care,
Paul


-----Original Message-----
From: Unbound-users [mailto:unbound-users-bounces at unbound.net] On Behalf Of
A. Schulze
Sent: Thursday, October 09, 2014 12:01 PM
To: unbound-users at unbound.net
Subject: Re: [Unbound-users] Can't Bind Socket Error


Paul Stewart:

> We just started migrating some of our customer base over to Unbound.

I assume you have an internal instance up and running and have good reasons
no not use default values.

Otherwise I suggest to start with an /empty/ unbound.conf and set only
necessary values.
Unbound has good defaults...
Or check, you are using most of them until you really need to change
defaults.

At first I would remove any interface / outgoing-interface setting on a host
with only one ip-address.

Andreas

_______________________________________________
Unbound-users mailing list
Unbound-users at unbound.net
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users