From owner-freebsd-questions Wed Aug 15 13: 2:58 2001 Delivered-To: freebsd-questions@freebsd.org Received: from hotmail.com (f78.law10.hotmail.com [64.4.15.78]) by hub.freebsd.org (Postfix) with ESMTP id 0AC9F37B419 for ; Wed, 15 Aug 2001 13:02:41 -0700 (PDT) (envelope-from ex279@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 15 Aug 2001 13:02:40 -0700 Received: from 205.228.172.82 by lw10fd.law10.hotmail.msn.com with HTTP; Wed, 15 Aug 2001 20:02:40 GMT X-Originating-IP: [205.228.172.82] From: "Todd Reed" To: freebsd-questions@freebsd.org Subject: DNS Configurations Date: Wed, 15 Aug 2001 15:02:40 -0500 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_6a8_6e83_bc3" Message-ID: X-OriginalArrivalTime: 15 Aug 2001 20:02:40.0833 (UTC) FILETIME=[3D2E8B10:01C125C5] Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_6a8_6e83_bc3 Content-Type: text/plain; format=flowed I'm not sure if my DNS server configurations are correct. I have the following files in /etc/namedb directory: cache.dns db.127.0.0 db.65.64.1.160 db.neaclinic.com make-localhost named.conf named.root PROTO.localhost.rev I've attached some of my DNS files. I've never setup. I'm also not sure about the proper way to test it before we go live. We currently have an existing DNS server, but we are changing Internet Service Providers, and need to limit our downtime. That's why I'm trying to build a new DNS server, so when we change our information with Network Solutions, things will go smooth and the only down time is reconfiguring the other devices behind the router and DNS server. _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ------=_NextPart_000_6a8_6e83_bc3 Content-Type: text/plain; name="db.127.0.0"; format=flowed Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="db.127.0.0" 0.0.127.in-addr.arpa. IN SOA hera.neaclinic.com t_reed.neaclinic.com. ( 1 ; Serial 10800 ; Refresh after 3 hours 3600 ; Retry after 1 hour 604800 ; Expire after 1 week 86400 ) ; Minimim TTL of 1 day 0.0.127.in-addr.arpa. IN NS ns1.neaclinic.com. 0.0.127.in-addr.arpa. IN NS ns2.neaclinic.com. 1.0.0.127.in-addr.arpa. IN PTR localhost. ------=_NextPart_000_6a8_6e83_bc3 Content-Type: text/plain; name="db.65.64.1.160"; format=flowed Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="db.65.64.1.160" 1.64.65.in-addr.arpa. IN SOA hera.neaclinic.com. t_reed@neaclinic.com. ( 1 ; Serial 10800 ; Refresh after 3 hours 3600 ; Retry after 1 hour 604800 ; Expire after 1 week 86400 ) ; Minimum TTL of 1 day 1.64.65.in-addr.arpa. IN NS ns1.neaclinic.com. 1.64.65.in-addr.arpa. IN NS ns2.neaclinic.com. 165.1.64.65.in-addr.arpa. IN PTR hera.neaclinic.com. 170.1.64.65.in-addr.arpa. IN PTR poseidon.neaclinic.com. 175.1.64.65.in-addr.arpa. IN PTR hermes.neaclinic.com. 180.1.64.65.in-addr.arpa. IN PTR priapus.neaclinic.com. 185.1.64.65.in-addr,arpa. IN PTR demeter.neaclinic.com. 188.1.64.65.in-addr.arpa. IN PTR ares.neaclinic.com. 190.1.64.65.in-addr.arpa. IN PTR moirae.neaclinic.com. ------=_NextPart_000_6a8_6e83_bc3 Content-Type: application/octet-stream; name="db.neaclinic.com" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="db.neaclinic.com" bmVhY2xpbmljLmNvbS4gSU4gU09BIGhlcmEubmVhY2xpbmljLmNvbS4gdF9y ZWVkLm5lYWNsaW5pYy5jb20uICggDQoJMQkJOyBTZXJpYWwNCgkxMDgwMAkJ OyBSZWZyZXNoIGFmdGVyIDMgaG91cnMNCgkzNjAwCQk7IFJldHJ5IGFmdGVy IDEgaG91cg0KCTYwNDgwMAk7IEV4cGlyZSBhZnRlciAxIHdlZWsNCgk4NjQw MCApCTsgTWluaW11bSBUVEwgb2YgMSBkYXkNCg0KbmVhY2xpbmljLmNvbS4J SU4gTlMJCW5zMS5uZWFjbGluaWMuY29tLg0KbmVhY2xpbmljLmNvbS4JSU4g TlMgIAluczIubmVhY2xpbmljLmNvbS4NCg0KTG9jYWxob3N0Lm5lYWNsaW5p Yy5jb20uCUlOIEEgCTEyNy4wLjAuMQk7IEROUyBTZXJ2ZXINCmhlcmEubmVh Y2xpbmljLmNvbS4JCUlOIEEgCTY1LjY0LjEuMTY1CTsgRE5TIFNlcnZlcg0K cG9zZWlkb24ubmVhY2xpbmljLmNvbS4JCUlOIEEJNjUuNjQuMS4xNzAJOyBX ZWIgU2VydmVyDQpoZXJtZXMubmVhY2xpbmljLmNvbS4JCUlOIEEJNjUuNjQu MS4xNzUJOyBFbWFpbCBTZXJ2ZXINCg0Kd3d3Lm5lYWNsaW5pYy5jb20uCQlJ TiBDTkFNRQlwb3NlaWRvbi5uZWFjbGluaWMuY29tLg0KbWFpbC5uZWFjbGlu aWMuY29tCQlJTiBDTkFNRQloZXJtZXMubmVhY2xpbmljLmNvbS4NCndlYm1h aWwubmVhY2xpbmljLmNvbQkJSU4gQ05BTUUJaGVybWVzLm5lYWNsaW5pYy5j b20uDQoNCg0KbmVhY2xpbmljLmNvbS4JCQlJTiBNWAkxMAloZXJtZXMubmVh Y2xpbmljLmNvbS4NCg== ------=_NextPart_000_6a8_6e83_bc3 Content-Type: text/plain; name="named.conf"; format=flowed Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="named.conf" // $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.2 2001/03/05 13:34:52 asmodai Exp $ // // Refer to the named(8) man page for details. If you are ever going // to setup a primary server, make sure you've understood the hairy // details of how DNS is working. Even with simple mistakes, you can // break connectivity for affected parties, or cause huge amount of // useless Internet traffic. options { directory "/etc/namedb"; // In addition to the "forwarders" clause, you can force your name // server to never initiate queries of its own, but always ask its // forwarders only, by enabling the following line: // // forward only; // If you've got a DNS server around at your upstream provider, enter // its IP address here, and enable the line below. This will make you // benefit from its cache, thus reduce overall DNS traffic in the Internet. /* forwarders { 127.0.0.1; }; */ /* * If there is a firewall between you and nameservers you want * to talk to, you might need to uncomment the query-source * directive below. Previous versions of BIND always asked * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ // query-source address * port 53; /* * If running in a sandbox, you may have to specify a different * location for the dumpfile. */ // dump-file "s/named_dump.db"; }; // Note: the following will be supported in a future release. /* host { any; } { topology { 127.0.0.0/8; }; }; */ // Setting up secondaries is way easier and the rough picture for this // is explained below. // // If you enable a local name server, don't forget to enter 127.0.0.1 // into your /etc/resolv.conf so this server will be queried first. // Also, make sure to enable it in /etc/rc.conf. zone "." { type hint; file "named.root"; }; zone "0.0.127.IN-ADDR.ARPA" { type master; file "localhost.rev"; }; zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" { type master; file "localhost.rev"; }; // NB: Do not use the IP addresses below, they are faked, and only // serve demonstration/documentation purposes! // // Example secondary config entries. It can be convenient to become // a secondary at least for the zone where your own domain is in. Ask // your network administrator for the IP address of the responsible // primary. // // Never forget to include the reverse lookup (IN-ADDR.ARPA) zone! // (This is the first bytes of the respective IP address, in reverse // order, with ".IN-ADDR.ARPA" appended.) // // Before starting to setup a primary zone, better make sure you fully // understand how DNS and BIND works, however. There are sometimes // unobvious pitfalls. Setting up a secondary is comparably simpler. // // NB: Don't blindly enable the examples below. :-) Use actual names // and addresses instead. // // NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf). // The directory containing the secondary zones must be write accessible // to bind. The following sequence is suggested: // // mkdir /etc/namedb/s // chown bind.bind /etc/namedb/s // chmod 750 /etc/namedb/s /* zone "domain.com" { type slave; file "s/domain.com.bak"; masters { 192.168.1.1; }; }; zone "0.168.192.in-addr.arpa" { type slave; file "s/0.168.192.in-addr.arpa.bak"; masters { 192.168.1.1; }; }; */ ------=_NextPart_000_6a8_6e83_bc3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message