Bind 9.3 failure message when configured for views with virtual IPs.
Kevin Darcy
kcd at daimlerchrysler.com
Wed Oct 26 20:32:41 UTC 2005
Lenny wrote:
>I am running views and have 2 virtual IPs configured in named.conf.
>The virtuals service the views and are configured according to O'Riely.
>The virtual IPs are 'up' and pingable.
>I get the following error message after I stop and start named.
>I have a similar config running in another location which works fine.
>
>[ID 866145 daemon.warning] unable to create dispatch for reserved port
>143.231.xxx.xxx#53: address not available
>
>Netstat shows the domain service is listening on the above IP/port.
>
Sometimes it takes a while for the old named process to clean up and
exit gracefully, especially if the cache is large. Make sure the old
named has stopped running before starting another one.
- Kevin
More information about the bind-users
mailing list