Creating ns1 & ns2 with Bind

// $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;
	};
};
*/

$TTL	86400
@       IN      SOA     localhost. root.localhost.  (
                                      1997022700 ; Serial
                                      28800      ; Refresh
                                      14400      ; Retry
                                      3600000    ; Expire
                                      86400 )    ; Minimum
              IN      NS      localhost.

1       IN      PTR     localhost.

Dec  5 21:26:35 2aa named[64980]: the default for the 'auth-nxdomain' option is
now 'no'

options {
	directory "/etc/namedb";
	auth-nxdomain yes;
};

zone "." {
	type hint;
	file "named.root";
};

zone "0.0.127.IN-ADDR.ARPA" {
	type master;
	file "localhost.rev";
	notify no;
};

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";
};

zone "sthost.co.uk" {
	type master;
	file "s/sthost.co.uk";
};

sthost.co.uk. IN SOA sthost.co.uk. root.sthost.co.uk. (
		2	; Serial
		10800	; Refresh after 3 hours
		3600	; Retry after 1 hour
		604800	; Expire after 1 week
		86400 )	; Minimum TTL of 1 day

;; ANSWER SECTION:
mail.sthost.co.uk.		IN MX	10 mail.sthost.co.uk.

;; AUTHORITY SECTION:
sthost.co.uk.	IN NS  ns1.sthost.co.uk.
sthost.co.uk.	IN NS  ns2.sthost.co.uk.

;; ADDITIONAL SECTION:
ns1.sthost.co.uk.	IN A	212.73.244.31
ns2.sthost.co.uk.	IN A	212.73.244.32

options {
	directory "/etc/namedb";
        version "";
        pid-file "/var/run/named.pid";
        allow-transfer { 212.73.244.32; };
	
        auth-nxdomain no;
};

zone "sthost.co.uk" in {
	type master;
	file "s/sthost.co.uk";
};

zone "0.0.127.in-addr.arpa" in {
	type master;
	file "localhost.rev";
        allow-transfer { none; };
	notify no;
};

zone "." in {
	type hint;
	file "named.root";
};

$TTL	86400
sthost.co.uk. IN SOA sthost.co.uk. hostmaster.sthost.co.uk. (
		200112061630	; Serial
		10800	; Refresh after 3 hours
		3600	; Retry after 1 hour
		604800	; Expire after 1 week
		86400 )	; Minimum TTL of 1 day
sthost.co.uk.		IN	NS	ns1.sthost.co.uk.
sthost.co.uk.		IN	NS	ns2.sthost.co.uk.
ns1.sthost.co.uk.	IN	A	212.73.244.31
ns2.sthost.co.uk.	IN	A	212.73.244.32
sthost.co.uk.		IN	A	212.73.244.31
www.sthost.co.uk.	IN	A	212.73.244.31
sthost.co.uk.		IN	MX	10	ns2.sthost.co.uk.