Re: named unable to bind to address?

[Andreas Gustafsson <gson%gson.org@localhost>]

John D. Baker wrote:
> Playing with my "@reboot" crontab entry, since 'cron' is started last,
> the elapsed time since 'named' was first started is enough and no
> additional delay is needed.  As such, it simply restarts 'named' and
> then external queries are received/answered.
> 
> I still shouldn't need this.  Why is the address "not available" when
> the first attempt to start 'named' is made?

Perhaps this is fallout from the change announced on current-users
in May with the subject line "HEAD UP - IPv4 addresses now have flags"?

  http://mail-index.netbsd.org/current-users/2015/05/02/msg027329.html

-- 
Andreas Gustafsson, gson%gson.org@localhost