From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041220 K-Meleon/0.9

Description of problem:
Bind refuses to start when a ppp interface exists on the system (in this case, a ppp interface created by the poptop PPTP server), with assertion failure.


Feb 21 14:11:05 everest named[29606]: starting BIND 9.3.1rc1 -u named
Feb 21 14:11:05 everest named[29606]: found 1 CPU, using 1 worker thread
Feb 21 14:11:05 everest named[29606]: loading configuration from '/etc/named.conf'
Feb 21 14:11:05 everest named[29606]: ifiter_getifaddrs.c:109: INSIST(ifa->ifa_a
ddr != ((void *)0)) failed
Feb 21 14:11:05 everest named[29606]: exiting (due to assertion failure)

With the ppp interface disconnected, bind starts normally.  Did not happen previously with 9.3.0 rpm.  Note that I do not have any way of testing a 'plain' ppp interface such as one used to dialup.  The rest of the interfaces are ethernet and loopback.

Version-Release number of selected component (if applicable):
bind-9.3.1rc1-1

How reproducible:
Always

Steps to Reproduce:
1. Connect PPTP client to server, which creates a ppp0 interface
2. Start bind via initscript
3. Startup fails
4. Disconnect PPTP client
5. Start bind via initscript
6. Startup completes with no errors 

Actual Results:  Bind failed to run

Expected Results:  Bind should be running

Additional info:

Kernel is 2.6.11-rc4-bk2, built from FC4 devel SRPM for Athlon XP 2000+ with all associated patches included in the SRPM, as well as mppe/mppc patch from http://www.polbox.com/h/hs001