From owner-freebsd-questions Mon Sep 25 18:55:47 2000 Delivered-To: freebsd-questions@freebsd.org Received: from munich.v-net.org (u57n248.hfx.eastlink.ca [24.222.57.248]) by hub.freebsd.org (Postfix) with ESMTP id 7DA1337B424 for ; Mon, 25 Sep 2000 18:55:24 -0700 (PDT) Received: from unisys (Windozzze [192.168.8.2]) by munich.v-net.org (8.9.3/8.9.3) with SMTP id WAA01792 for ; Mon, 25 Sep 2000 22:55:17 -0300 (ADT) (envelope-from matt@researcher.com) From: "Matt Rudderham" To: Subject: BIND v. 8 Date: Mon, 25 Sep 2000 22:56:32 -0300 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0005_01C02743.D95CBEC0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C02743.D95CBEC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I recently purchased DNS & BIND by O'Reilly and it has proven very resourceful. I am trying to setup bind to be authoritive for my Sub-Domain which will be delegated to me as soon as I have Named running. All appears to be well in my config, but after starting bind, I am getting the following: Sep 25 22:10:37 MUNICH named[317]: bind(dfd=2, [my oip].53 Address already in use Sep 25 22:10:37 MUNICH named[317]: bind(dfd=2, [192.168.8.1].53 Address already in use Sep 25 22:10:37 MUNICH named[317]: bind(dfd=2, [127.0.0.1].53 Address already in use Any idea what could be causing this? Attached is my named.conf. Let me know if I should attach my db files. Thanks - Matthew Rudderham ------=_NextPart_000_0005_01C02743.D95CBEC0 Content-Type: application/octet-stream; name="named.conf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="named.conf" // $FreeBSD: src/etc/namedb/named.conf,v 1.6 1999/08/27 23:24:02 peter = Exp $=0A= //=0A= // Refer to the named(8) man page for details. If you are ever going=0A= // to setup a primary server, make sure you've understood the hairy=0A= // details of how DNS is working. Even with simple mistakes, you can=0A= // break connectivity for affected parties, or cause huge amount of=0A= // useless Internet traffic.=0A= =0A= options {=0A= directory "/etc/namedb";=0A= =0A= // In addition to the "forwarders" clause, you can force your name=0A= // server to never initiate queries of its own, but always ask its=0A= // forwarders only, by enabling the following line:=0A= //=0A= // forward only;=0A= =0A= // If you've got a DNS server around at your upstream provider, enter=0A= // its IP address here, and enable the line below. This will make you=0A= // benefit from its cache, thus reduce overall DNS traffic in the = Internet.=0A= =0A= forwarders {=0A= 24.222.0.33;=0A= };=0A= =0A= /*=0A= * If there is a firewall between you and nameservers you want=0A= * to talk to, you might need to uncomment the query-source=0A= * directive below. Previous versions of BIND always asked=0A= * questions using port 53, but BIND 8.1 uses an unprivileged=0A= * port by default.=0A= */=0A= // query-source address * port 53;=0A= =0A= /*=0A= * If running in a sandbox, you may have to specify a different=0A= * location for the dumpfile.=0A= */=0A= /* Uncommented the Below Line 9-24-2000 */=0A= dump-file "s/named_dump.db";=0A= };=0A= =0A= // Note: the following will be supported in a future release.=0A= /*=0A= host { any; } {=0A= topology {=0A= 127.0.0.0/8;=0A= };=0A= };=0A= */=0A= =0A= // Setting up secondaries is way easier and the rough picture for this=0A= // is explained below.=0A= //=0A= // If you enable a local name server, don't forget to enter 127.0.0.1=0A= // into your /etc/resolv.conf so this server will be queried first.=0A= // Also, make sure to enable it in /etc/rc.conf.=0A= =0A= zone "." {=0A= type hint;=0A= file "named.root";=0A= };=0A= =0A= zone "0.0.127.IN-ADDR.ARPA" {=0A= type master;=0A= file "db.127.0.0";=0A= };=0A= =0A= zone "munich.v-net.org" {=0A= type master;=0A= file "db.munich";=0A= };=0A= =0A= zone "248.57.222.24.IN-ADDR.ARPA" {=0A= type master;=0A= file "db.24.222.57.248";=0A= };=0A= =0A= =0A= // NB: Do not use the IP addresses below, they are faked, and only=0A= // serve demonstration/documentation purposes!=0A= //=0A= // Example secondary config entries. It can be convenient to become=0A= // a secondary at least for the zone where your own domain is in. Ask=0A= // your network administrator for the IP address of the responsible=0A= // primary.=0A= //=0A= // Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!=0A= // (This is the first bytes of the respective IP address, in reverse=0A= // order, with ".IN-ADDR.ARPA" appended.)=0A= //=0A= // Before starting to setup a primary zone, better make sure you fully=0A= // understand how DNS and BIND works, however. There are sometimes=0A= // unobvious pitfalls. Setting up a secondary is comparably simpler.=0A= //=0A= // NB: Don't blindly enable the examples below. :-) Use actual names=0A= // and addresses instead.=0A= //=0A= // NOTE!!! FreeBSD runs bind in a sandbox (see named_flags in rc.conf).=0A= // The directory containing the secondary zones must be write accessible =0A= // to bind. The following sequence is suggested:=0A= //=0A= // mkdir /etc/namedb/s=0A= // chown bind.bind /etc/namedb/s=0A= // chmod 750 /etc/namedb/s=0A= =0A= /*=0A= zone "domain.com" {=0A= type slave;=0A= file "s/domain.com.bak";=0A= masters {=0A= 192.168.8.1;=0A= };=0A= };=0A= =0A= zone "8.168.192.in-addr.arpa" {=0A= type slave;=0A= file "s/8.168.192.in-addr.arpa.bak";=0A= masters {=0A= 192.168.8.1;=0A= };=0A= };=0A= */=0A= =0A= ------=_NextPart_000_0005_01C02743.D95CBEC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message