Configure DNS

Configure DNS Organic Design procedure

Local caching DNS Server

Setting up a local caching DNS server is a good idea to ensure that DNS requests return quickly (especially useful if you have sites that make requests before returning the pages). It's also essential if you're running spam assassin because the domain black-lists (DNSBL) services operate over DNS and will often block requests made from large ISP's DNS servers. The most popular DNS server is Bind9 and is set up in caching configuration by default, or the unbound DNS resolver is very light weight and efficient.

First install bind9 or unbound:

apt-get install [bind9|unbound]

Change the ISP name servers in your /etc/resolv.conf file to use the new local server instead:

search com
nameserver 127.0.0.1

Note: Don't forget to check /etc/network/interfaces and comment out any DNS servers specified there too.

You can ensure that your new DNS server is indeed in local caching configuration with by checking that port 53 is only open to local requests with netstat -nlp|grep :53

tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      893/unbound
tcp6       0      0 ::1:53                  :::*                    LISTEN      893/unbound
udp        0      0 127.0.0.1:53            0.0.0.0:*                           893/unbound
udp6       0      0 ::1:53                  :::*                                893/unbound

Setting up local domains names

Requests under the organisation's domain name from the Internet must be forwarded to the ISP-assigned external IP address using an A-record. This may require Dynamic DNS if a static IP address arrangement has not been made with the ISP.

Requests made for the domain from within the LAN require the local server to be authoritative, but to refer all other requests to the ISP-assigned DNS servers.

The following example is for a domain called foo.co.nz which has an internal wiki and mail-server, but an external website on the IP address 1.2.3.5 and all other sub-domains (apart from wiki and mail) pointing at the external IP address 1.2.3.4. This example assumes that the domain is configured correctly for resolving external requests, and focusses on the configuration of the DNS server running internally on the LAN on IP address 192.168.1.1. The wiki, DNS server and mail-server are all running on the same machine.

Install Bind9 with apt-get install bind9, then edit /etc/bind/named.conf.options and set the forwarders to your ISP's domain name server, or a public name-server such as OpenDNS.com (also some easy to remember ones are 4.2.2.2 and 8.8.8.8) e.g.

forwarders {
    208.67.222.222;
    208.67.220.220;
};

Add the following zone configuration in /etc/bind/named.conf.local:

zone "foo.org" {
	type master;
	file "foo.db";
};

zone "1.168.192.in-addr.arpa" {
	type master;
	file "db.192";
};

The zone files reside in /var/cache/bind and are of the following format:

$TTL	1D
@	IN SOA ns1.foo.co.nz. root.foo.co.nz. (
                      200905081             ; Serial
                         604800             ; Refresh
                          86400             ; Retry
                        2419200             ; Expire
                         604800 )           ; Negative Cache TTL

		NS      ns1
		MX	10 mail.foo.co.nz.
ns1	IN	A	192.168.1.1
www	IN	A	1.2.3.5
wiki	IN	A	192.168.1.1
mail	IN	A	192.168.1.1
@	IN	A	1.2.3.4
*	IN	A	1.2.3.4
foo     IN      CNAME   foo.com

• Note: The "@" symbol means the naked domain
• Note: CNAME's work for subdomains and * but not for @

And the reverse lookup file, /var/cache/bind/db.192:

@ IN SOA foo.co.nz. root.foo.co.nz. (
                      200905081		; Serial
                         604800		; Refresh
                          86400		; Retry
                        2419200		; Expire
                         604800 )	; Default TTL

	IN	NS	ns1.foo.co.nz.
1	IN	PTR	foo.co.nz.

Notes

• Be sure to increase the serial number each time a zone file is edited or the changes will be ignored
• Remember to reload the zone files after making changes with service bind9 reload.
• Note the "1" in the last line of the reverse lookup is the last digit of the DNS server's IP address

Public DNS servers

OpenDNS

• 208.67.222.222
• 208.67.220.220

Google

• 8.8.8.8
• 8.8.4.4
• 2001:4860:4860::8888
• 2001:4860:4860::8844

DNSadvantage

• 156.154.70.1
• 156.154.71.1

Norton

• 198.153.192.1
• 198.153.194.1

Verizon

• 4.2.2.1
• 4.2.2.2
• 4.2.2.3
• 4.2.2.4
• 4.2.2.5
• 4.2.2.6

Dynamic DNS

It's often useful to be able to access machines on our local LAN's from other locations. Most of the LAN's we need to access machines on do not have static IP addresses, so a Dynamic DNS solution is used to keep a domain name up to date with the current IP address.

Our .com domain host is namecheap.com and they provide a free dynamic DNS solution allowing simple HTTP query-string based method of updating a sub-domain. We just add a single entry to /etc/crontab which looks like this (replace SUB, DOMAIN and PASS with your specific settings):

*/10 * * * * nobody wget -q --spider "http://dynamicdns.park-your-domain.com/update?host=SUB&domain=DOMAIN&password=PASS"

The subdomain will automatically be created when the first request is made if it didn't previously exist. The password is shown in the namecheap.com admin site in the "DynamicDNS" section for the appropriate domain.

See also

• Turn on query logging
• DynamicDNS.pl - the script we used to use to update DNS records only when router's external IP changes
• OpenDNS - free fast DNS servers that aren't Google