From owner-freebsd-bugs Wed Aug 8 5:53:22 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 0CEBC37B403 for ; Wed, 8 Aug 2001 05:53:18 -0700 (PDT) (envelope-from msinz@wgate.com) Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id QJNXLPDK; Wed, 8 Aug 2001 08:52:36 -0400 Received: from wgate.com (localhost [127.0.0.1]) by sinz.eng.tvol.net (8.11.3/8.11.3) with ESMTP id f78CrGL10397; Wed, 8 Aug 2001 08:53:16 -0400 (EDT) (envelope-from msinz@wgate.com) Message-ID: <3B71363C.EB14B13C@wgate.com> Date: Wed, 08 Aug 2001 08:53:16 -0400 From: Michael Sinz Organization: WorldGate Communications Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-bugs@FreeBSD.ORG Cc: dillon@backplane.com Subject: FreeBSD 4.4 prerelease broke bind Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The current build of FreeBSD 4.4 (prerelease) majorly broke us here. The DNS server cores whenever DHCPD does an update packet (sending a name for a newly conencted or updated IP address) In FreeBSD 4.3 (latest before the bind 8.2.4 MFC) things worked great. In the current 4.4, bind 8.2.4 replaced 8.2.3 and all hell breaks loose. named starts up (only after we remove all of the .log files in its database directory) and then starts to run. We Aug 7 17:34:01 Server-0-2 named[2298]: starting (/etc/namedb/named.conf). named 8.2.4-REL Mon Aug 6 09:53:51 EDT 2001 root@tics36.eng.tvol.net:/usr/obj/usr/src/usr.sbin/named Aug 7 17:34:01 Server-0-2 named[2298]: limit files set to fdlimit (1024) Aug 7 17:34:02 Server-0-2 named[2299]: Ready to answer queries. Aug 7 17:34:43 Server-0-2 dhcpd: No hostname for 172.31.191.251 Aug 7 17:34:47 Server-0-2 dhcpd: if IN A tics-191-251.tics35.eng.tvol.net domain doesn't exist add 150 IN A tics-191-251.tics35.eng.tvol.net 172.31.191.251 add 150 IN TXT tics-191-251.tics35.eng.tvol.net "00b8084f86117dc0d53be0931cfae03a4e": success. Aug 7 17:34:47 Server-0-2 dhcpd: delete IN PTR 251.191.31.172.in-addr.arpa. add 150 IN PTR 251.191.31.172.in-addr.arpa. tics-191-251.tics35.eng.tvol.net: success. Aug 7 17:37:11 Server-0-2 dhcpd: if IN A tics-191-253.tics35.eng.tvol.net domain doesn't exist add 575131708 IN A tics-191-253.tics35.eng.tvol.net 172.31.191.253 add 575131708 IN TXT tics-191-253.tics35.eng.tvol.net "0011ba341b1cbfc959be170e3195560019": success. Aug 7 17:37:11 Server-0-2 dhcpd: delete IN PTR 253.191.31.172.in-addr.arpa. add 575131708 IN PTR 253.191.31.172.in-addr.arpa. tics-191-253.tics35.eng.tvol.net: success. Aug 7 17:37:11 Server-0-2 named[2299]: d_rcnt-- == 0 Aug 7 17:37:11 Server-0-2 named[2299]: d_rcnt-- == 0 Aug 7 17:37:11 Server-0-2 /kernel: pid 2299 (named), uid 0: exited on signal 6 (core dumped) (there are other, unreleated items in syslog - these are those that matter the others are just from other machines being active at the time...) Anyway, as you can see, a simple dynamic update blows DNS right out of the water. No more name server (at which point all sorts of things fail as we get no more lookups of other items, such as the nfs server or the web server or...) Anyway, this is a heads up that 4.4 prerelease is, for our use atleast, DOA. (I have not yet had time to try to track this down - there are some major differences between bind 8.2.3 and 8.2.4 so it was non-obvious at first glance - having had just a few minutes to look into it) -- Michael Sinz ---- Worldgate Communications ---- msinz@wgate.com A master's secrets are only as good as the master's ability to explain them to others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message