[ale] (caching) nameserver wierdness after new ip from dhcp

[Ken Cochran]

Hi folks, hope not OT (OS is FreeBSD):

I have a "wierdness" happening, kinda wonder if I might've been
rooted or something.  :(  (Doesn't look like I have, else I
think it would've tripped the nightly system security scans.
Also, I've refreshed the named binary.)

In the wee hours of the morning, my upstream cablemodem provider
dhcp'ed me a new ip-address.  Ok, fine...  (Dhclient seems
working fine from what the system log & tcpdump are showing.)

I can ping/traceroute (to) my system from outside (proper stuff
shows up in tcpdump too) but I can't ping/traceroute *from*
my system to anywhere (not even by ip-address).  I can ping
"myself" (the newly assigned ip-address) just fine.

Ok, so name service isn't working (I run a local cache-only
DNS, BIND 8.3.7, ya, old but someday...), so I kill &
restart named.  The appropriate named startup messages appear
in the messages-log, e.g. "listening on [new ip-address]."
Here's the wierd part: tcpdump shows DNS "priming" requests
(to the various *.root-servers.net addresses) with a *source*
ip of my *previous ip-address, not the new one.  So far, *no* NS
requests show the proper source address; they all show the old
ip-address & not the new one.  Also, so far, behavior survives
reloading, restarting & completely killing & restarting named,
as well as restarting named with a new copy of its binary.

Umm... what else can I think of...  No external IPs are in the
named config and/or zone files, only local 192.168 & 127 things.

Ideas?  Thanks...

-kc