how to configure new dns files?

how to configure new dns files?

Post by David Paig » Tue, 21 Nov 2000 04:00:00



All,

I just installed a new firewall (fbsd 4.1) and the dns
programs (e.g. bind) have rev'd and use new file formats.  :-(

I have my old set of named files, but I can't seem to get
the new named to work.  When I attach to it (using nslookup)
querys for my domain timeout, but others work fine.

Any ideas what I am doing wrong?  Attached are named.conf and
the file for my domain.

Thanks,
-David

----- cut ----- here ----- for ----- named.conf -----
// $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.1 2000/07/15 07:49:29 kris 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 {
                207.149.236.6:
                207.149.236.7:
        };
*/
        /*
         * 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 runs 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 "heathen.com" {
        type master;
        file "s/heathen.db";
        masters {
                63.170.215.42;
        };

};

zone "0.168.192.in-addr.arpa" {
        type master;
        file "s/lan.rev";
        masters {
                192.168.2.1;
        };

};

zone "215.170.63.in-addr.arpa" {
        type slave;
        file "s/northwest.rev";
        masters {
                207.149.236.6;
        };

};

zone "37.240.216.in-addr.arpa" {
        type slave;
        file "s/idiom.rev";
        masters {
                209.209.60.131;
        };
};

*/

----- cut ----- here ----- for ----- heathen.db -----
;
; Authoritative data for heathen.com domain
; belonging to David Paigen
;
heathen.com.    IN      SOA     ns.idiom.com.        support.idiom.com.  
(
                                2000112001      ;       serial
                                108009          ; refresh       - 3 hours
                                3600            ; retry         - 1 hour
                                360000          ; expire        - 100 hours
                                86400 )         ; minimum       - 1 day
        IN      MX                      10 sweep.heathen.com.
        IN      MX                      20 foible.heathen.com.
        IN      MX                      50 idiom.com.
        IN      NS                      ns.idiom.com.
        IN      NS                      sweep.heathen.com.
        IN      A                       63.170.215.42
;
localhost                       IN      A               127.1
foible                          IN      A               216.240.37.98
sweep                           IN      A               63.170.215.42
;
;
; Define CNAMES, etc.
;
ns.heathen.com.                 IN      CNAME           sweep.heathen.com.
nntp.heathen.com.               IN      CNAME           sweep.heathen.com.
smtp.heathen.com.               IN      CNAME           sweep.heathen.com.
mail.heathen.com.               IN      CNAME           sweep.heathen.com.
ftp.heathen.com.                IN      CNAME           sweep.heathen.com.
www.heathen.com.                IN      CNAME           sweep.heathen.com.
--
David Paigen                    Software Manager, Eloquent
pai...@heathen.com

 
 
 

how to configure new dns files?

Post by Nero Imhar » Wed, 22 Nov 2000 04:00:00


LOL (sorry)

The important parts of named.conf are all commented out ;-)

Note that everithing between /* and */ is a comment and that
such a comment can span multiple lines.

--Nero

 
 
 

how to configure new dns files?

Post by Bill Vermilli » Wed, 22 Nov 2000 04:00:00




>I just installed a new firewall (fbsd 4.1) and the dns
>programs (e.g. bind) have rev'd and use new file formats.  :-(
>I have my old set of named files, but I can't seem to get
>the new named to work.  When I attach to it (using nslookup)
>querys for my domain timeout, but others work fine.
>Any ideas what I am doing wrong?  Attached are named.conf and
>the file for my domain.

Two things. Look in the system logs - /var/log/messages for any
hints, and secondly get nslint from the ports.  I find the latter
almost indispensable.

Bill

--

 
 
 

how to configure new dns files?

Post by David Paig » Wed, 22 Nov 2000 04:00:00




Quote:>LOL (sorry)

>The important parts of named.conf are all commented out ;-)

Thanks, Nero.  After several hours and turning on what seemed like
hundreds of debug options, I finally noticed that.  I felt really
silly.  :-)

-David
--
David Paigen                    Software Manager, Eloquent

 
 
 

1. DNS -Problem to configure a secondary dns server

    Hello, I'm trying to configure a computer with FreeBSD 3.3-stable to
work as secondary dns server. When I init the daemon named I found the
following message in the file /var/log/maillog:
Oct 25 10:24:40 mulhacen2 named[130]: reloading nameserver
Oct 25 10:24:40 mulhacen2 named[130]: /etc/namedb/named.boot:1: syntax error
near ;
Oct 25 10:24:40 mulhacen2 named[130]: Ready to answer queries.

    My file named.boot is too short, by the moment, and has the following
lines:

;       $Id: named.boot,v 1.3.6.2 1997/12/23 21:05:55 jkh Exp $

directory /etc/namedb
primary dominio.es         dominio.hosts
primary 0.0.127.IN-ADDR.ARPA    dominio.local

    I'm looking for the problem but I don't find it, could someone help me?.
Thanks in advance.

2. Motif 1.2.4 for Linux coming Soon!

3. New DNS named.root file

4. My modem is not responding

5. consistent read() on file while rename() file.new -> file?

6. inb/inb_p and outb/outb_p

7. How to configure a Print Server to print a file as a file

8. Ssh newbie question: publickey authentication method fails

9. configuring dns server

10. Configuring support for second domain through MMDF /DNS

11. DNS, NIS? Problems configuring in.named.

12. To Configure A Multi Zone DNS On A Subnet?

13. change to new gid or new group name all files of given group name or gid