Date: Sun, 25 Jan 2009 12:13:48 +1100 From: Mark Andrews <Mark_Andrews@isc.org> To: FreeBSD Stable <freebsd-stable@freebsd.org> Cc: freebsd-net@freebsd.org, lev@freebsd.org Subject: Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address Message-ID: <200901250113.n0P1DmHe060610@drugs.dv.isc.org> In-Reply-To: Your message of "Sat, 24 Jan 2009 15:10:44 -0800." <497B9FF4.30605@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <497B9FF4.30605@FreeBSD.org>, Doug Barton writes: > Lev Serebryakov wrote: > > Hello, Freebsd-stable. > > > > BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of > > errors on every start and doesn't answer on requests for 30-60 seconds > > after that. Errors are like this: > > It's not necessary or desirable to paste in so many examples of the > same message. It's also not good to cross post the same message to > multiple lists. > > > Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib > /bind9/lib/isc/unix/socket.c:1567: unexpected error: > > Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53: Device > not configured > > That message is fairly clear, the system has told named that it can > talk to the outside world, but there isn't anything there for named to > talk to. As you already pointed out in another message, the IP > addresses are for the root name servers. The first thing named does > when it starts up is to verify the information in the hints file. > > > Main problem is, that mount_nfs failed on startup on this router > > because bind is not ready due to these errors and all system goes to > > single-user mode :( > > Any time you are using NFS you should maintain the addresses of the > critical hosts in /etc/hosts. Yes, I realize that's anachronistic > (especially for a DNS guy) but it works. Obviously you should make > sure to update them as needed. Or keep a local copy of the zone which contains them. If you have a copy in /etc/hosts there should be procedures to keep /etc/hosts in sync with the DNS. > > Computer is Soekris net5501, with 6 network interfaces (vr0-vr3 on > > board, em0 and ath0 attached). Only vr0 and vr1 are used, but adding > > fake addresses to vr2 and vr3 doesn't help at all. > > > > Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect t > o two > > providers. > > > > But previous installation (on faster hardware) doesn't show these > > errors at all! > > I've never used mpd myself, but you might want to try adding the > following line to /usr/local/etc/rc.d/mpd and see if it helps: > > # BEFORE: named mpd should also be fixed as the error code being returned is not approprate. network unreachable is what should be returned. > Doug > > -- > > This .signature sanitized for your protection > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200901250113.n0P1DmHe060610>