Looping: 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

2009-01-27 Thread Mark Andrews
Can the freebsd-stable subscriber at exchange.physicalsegment.com please stop looping email. If you want to re-inject email DO NOT use the To: or Cc: lines to determine where to send the email to. It just creates email loops. Mark Received: from mail pick

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

2009-01-26 Thread Alexander Motin
Lev Serebryakov wrote: 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: Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socke

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

2009-01-25 Thread Doug Barton
Lev Serebryakov wrote: > Hello, Doug. > You wrote 25 января 2009 г., 04:19:40: > >> I actually considered suggesting that option, but it's unclear to me >> whether or not named would answer at all, even for a local zone, given >> the situation described. > This named CARRIES (and is MASTER) for

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

2009-01-25 Thread Ian Smith
On Sun, 25 Jan 2009, Daniel O'Connor wrote: > On Sunday 25 January 2009 11:43:48 Mark Andrews wrote: Doug Barton wrote: > > > 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

Re[2]: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address

2009-01-25 Thread Lev Serebryakov
Hello, Doug. You wrote 25 января 2009 г., 04:19:40: > I actually considered suggesting that option, but it's unclear to me > whether or not named would answer at all, even for a local zone, given > the situation described. This named CARRIES (and is MASTER) for local zone, but it didn't answer i

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

2009-01-24 Thread Daniel O'Connor
On Sunday 25 January 2009 11:43:48 Mark Andrews wrote: > > 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.

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

2009-01-24 Thread Doug Barton
Mark Andrews wrote: > In message <497bbe2c.5060...@freebsd.org>, Doug Barton writes: >> Mark Andrews wrote: >>> In message <497b9ff4.30...@freebsd.org>, Doug Barton writes: Any time you are using NFS you should maintain the addresses of the critical hosts in /etc/hosts. Yes, I realize tha

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

2009-01-24 Thread Mark Andrews
In message <497bbe2c.5060...@freebsd.org>, Doug Barton writes: > Mark Andrews wrote: > > In message <497b9ff4.30...@freebsd.org>, Doug Barton writes: > >> Any time you are using NFS you should maintain the addresses of the > >> critical hosts in /etc/hosts. Yes, I realize that's anachronistic > >>

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

2009-01-24 Thread Doug Barton
Mark Andrews wrote: > In message <497b9ff4.30...@freebsd.org>, Doug Barton writes: >> 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 >> sur

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

2009-01-24 Thread Mark Andrews
In message <497b9ff4.30...@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 th

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

2009-01-24 Thread Doug Barton
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 s

Re[2]: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address

2009-01-24 Thread Lev Serebryakov
Hello, Daniel. You wrote 24 января 2009 г., 15:10:24: >> Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect >> to two providers. >> >> But previous installation (on faster hardware) doesn't show these >> errors at all! > I think this is an mpd problem - I had the same issue

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

2009-01-24 Thread Daniel O'Connor
On Saturday 24 January 2009 21:07:33 Lev Serebryakov wrote: > 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: > > Jan 24 12:18:12 gateway named[1455]: > /usr/src/lib/bind/

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

2009-01-24 Thread Lev Serebryakov
Hello, Lev. You wrote 24 января 2009 г., 13:37:33: > IP addresses are RANDOM and DIFFERENT on every restart. These IP > addresses are not mentioned in ANY config file on my computer, and > addresses on my network interfaces IS NOT from these networks. Ok, I'm stupid, it is root servers. Ok. Bu

BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address

2009-01-24 Thread Lev Serebryakov
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: Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket