Re: Weird problems with BIND 8.3.1-REL
David O'Brien wrote: > > On Sat, Jun 22, 2002 at 02:52:19PM -0700, Doug Barton wrote: > > > version in the tree appears to be 8.3.2-T1B (which I just installed > > > a second ago). > > > > I just updated the bind8 port to 8.3.2-RELEASE, which I recommend that > > you run instead. I saw some weird problems with the pre-release versions > > Any reason to not import that version into /usr/src/contrib/bind? I'm actually working on that, but there are a few bogons I need to clean up first. -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Weird problems with BIND 8.3.1-REL
On Sat, Jun 22, 2002 at 02:52:19PM -0700, Doug Barton wrote: > > version in the tree appears to be 8.3.2-T1B (which I just installed > > a second ago). > > I just updated the bind8 port to 8.3.2-RELEASE, which I recommend that > you run instead. I saw some weird problems with the pre-release versions Any reason to not import that version into /usr/src/contrib/bind? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Weird problems with BIND 8.3.1-REL
Matthew Dillon wrote: > > I am having weird problems with BIND. It started happening about a month > and a half ago. named would start returning immediate host name lookup > failures for just about everything and never recover. That's not good. :) I assume you're using it as a resolver from the dump. > I dumped named in one of these instances. The dump file (500K) is > temporarily at: http://apollo.backplane.com/named_dump.db . If there > are any DNS gurus out there I would appreciate a look-see. Unfortunately, the db is generally not the problem. The only way to diagnose it is to up the debug level and log what's happening while it's actually broken. > Is anyone aware of any issues with named? I see that the current > version in the tree appears to be 8.3.2-T1B (which I just installed > a second ago). I just updated the bind8 port to 8.3.2-RELEASE, which I recommend that you run instead. I saw some weird problems with the pre-release versions of 8.3.2 that seem to be fixed now. I also added a new knob to the port so you can make -DREPLACE_SYSTEM_BIND install and have it update the stuff in /usr instead of installing to /usr/local. Good luck, Doug -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Weird problems with BIND 8.3.1-REL
I am having weird problems with BIND. It started happening about a month and a half ago. named would start returning immediate host name lookup failures for just about everything and never recover. I dumped named in one of these instances. The dump file (500K) is temporarily at: http://apollo.backplane.com/named_dump.db . If there are any DNS gurus out there I would appreciate a look-see. Is anyone aware of any issues with named? I see that the current version in the tree appears to be 8.3.2-T1B (which I just installed a second ago). -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
