Named errors after adding IPv4 alias - solved by restarting named

John john at
Wed Feb 17 21:39:35 UTC 2010

It seems that if you add an alias to an interface once named is up
and running, it will cause named, on an hourly basis from the time
named was first started (that is, if it was started at 07:32 after
the hour, then every hour after the alias is added at about 07:32
after each hour), named will say:

Feb 16 22:07:32 elwood named[626]: could not listen on UDP socket: permission denied
Feb 16 22:07:32 elwood named[626]: creating IPv4 interface fxp0 failed; interface ignored

A "kill -1" does not help.  If you do a full "stop" and "start" on named,
that will take care of the problem.

Is this something that should be addressed within named, or is this
such a rare event (adding an IP alias on an interface that named is
using) that it should just be let go?

John Lind
john at starfire.MN.ORG

More information about the freebsd-questions mailing list