Re: named unable to bind to address?

["John D. Baker" <jdbaker%mylinuxisp.com@localhost>]

On Mon, 17 Aug 2015, John D. Baker wrote:

> 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?

On Mon, 17 Aug 2015 19:47:36 +0300, Andreas Gustafsson <gson%gson.org@localhost>
wrote:

> John D. Baker wrote:
> > 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

That seems to be the case.

But

On Mon, 17 Aug 2015 11:54:41 -0500 (CDT), Jeremy C. Reed <reed%reedmedia.net@localhost>
wrote:

> I don't know why your bge1 isn't available yet. Maybe look in your dmesg 
> for more details about it and share here.

Looks fairly ordinary to me (both interfaces shown since I've run with
each of them with the same result):

[...]
bge0 at pci1 dev 6 function 0: Broadcom BCM5703X Gigabit Ethernet
bge0: interrupting at ioapic1 pin 12
bge0: HW config 00000115, 00000000, 00000000, 00000000 00000000
bge0: ASIC BCM5702/5703 A2 (0x1002), Ethernet address xx:xx:xx:xx:xx:xx
brgphy0 at bge0 phy 1: BCM5703 1000BASE-T media interface, rev. 2
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bge1 at pci1 dev 8 function 0: Broadcom BCM5703X Gigabit Ethernet
bge1: interrupting at ioapic1 pin 13
bge1: HW config 00000115, 00000000, 00000000, 00000000 00000000
bge1: ASIC BCM5702/5703 A2 (0x1002), Ethernet address xx:xx:xx:xx:xx:xx
brgphy1 at bge1 phy 1: BCM5703 1000BASE-T media interface, rev. 2
brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
[...]

The only slightly odd thing I noticed was that the device was being
marked "up" before the IPv4 address was assigned.  Changing it so address
assignment came first and then marking it "up" made no difference.

> (By the way, named has automatic-interface-scan and interface-interval 
> options that may help for later interface listening (defaults yes and 60 
> seconds).)

I noticed that in the full sequence of messages, 'named' tries twice to
bind to the external address--once at the beginning and once again near
the end of its startup procedure.  It fails both times.  I see no evidence
in the log files that it ever tries again afterward, though.

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

From gson%gson.org@localhost Mon Aug 17 11:57:27 2015
Date: Mon, 17 Aug 2015 19:47:36 +0300
From: Andreas Gustafsson <gson%gson.org@localhost>
To: John D. Baker <jdbaker%mylinuxisp.com@localhost>
Cc: current-users%NetBSD.org@localhost
Subject: Re: named unable to bind to address?

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

From reed%reedmedia.net@localhost Mon Aug 17 11:57:29 2015
Date: Mon, 17 Aug 2015 11:54:41 -0500 (CDT)
From: Jeremy C. Reed <reed%reedmedia.net@localhost>
To: John D. Baker <jdbaker%mylinuxisp.com@localhost>
Cc: current-users%NetBSD.org@localhost
Subject: Re: named unable to bind to address?

As another workaround, maybe use sleep with some amount of seconds in 
your named startup script to delay its startup to make sure your bge1 is 
up.

(By the way, named has automatic-interface-scan and interface-interval 
options that may help for later interface listening (defaults yes and 60 
seconds).)