Advanced BIND configuration

I just now switched to using "views" in BIND. I'm fairly proud of my dns server configuration right now. The server is practically split into 2 servers where a caching server is listening on loopback and the DollarDNS hosted domains on the ethernet IP. It also splits the DollarDNS domains so that local addresses are returned for local queries. This is demonstrated using the DNS Crawler as shown below:

http://www.dollardns.net/cgi-bin/dn...s=256&submit=DS

http://www.dollardns.net/cgi-bin/dn...s.net&submit=DS

This config also sports an advanced logging configuration far superior to the example shown in http://www.dollardns.net/bind/

Several options are also used which aren't mentioned in the example config. So here's my DNS server config which I use for personal and client use. Perhaps you can take some tips from it.

http://www.dollardns.net/bind/advanced/named.conf

I think you meant to use Localhost on the first link?
http://www.dollardns.net/cgi-bin/dn...s=256&submit=DS

I havent looked at the conf yet, so perhaps its in there but I'm wanting to allow my clients to modify their DNS records, the way you have it on your services, but i'll perhaps be using PHP instead.

How do you call up an individuals record? are they custom confs that are loaded seperately from your main configuration.

I'm guessing it is, but multiple files or do you have some system of pulling out each users and editing it from a single file.

I used to have DNSCrawler resolve localserver to 127.0.0.1. Now DNSCrawler relies on the server for all resolution so that reference was removed. I've edited my link to use a more appropriate server to query the local zone for dollardns domains. Thanks for pointing that out.

This is how I pull things off:

First an account is created:

1) /var/named/usr/$user directory is created
2) /var/named/usr/$user/zones.conf is created and is empty
3) /var/named/usr/$user/zones.db is created and is empty
4) /var/named/usr/users.conf is appended with an "include" statement including /var/named/usr/$user/zones.conf

User creates a master zone

1) /var/named/usr/$user/zones.db is appended with a zone record
2) /var/named/usr/$user/$zone.zone is created based on the master zone template
3) /var/named/usr/$user/$zone.conf is created with zone configuration defaults. It's in key=value format.
4) /var/named/usr/$user/zones.conf is generated with BIND zone syntax based on the contents of zones.db and each $zone.conf. This file is viewable via the "View Zones Configuration" link in the Zone Manager.
5) BIND's "rndc reconfig" is executed and the change takes effect immediately.

User edits master zone

1) /var/named/usr/$user/$zone.temp is created with the new zone contents
2) BIND's named-checkzone.exe is executed to check the temp zone file for syntax errors.
3a) If there's errors, these errors are formatted and returned to the user.
3b) If there's no errors it writes the contents to /var/named/usr/$user/$zone.zone and executes "rndc reload $zone IN host" to reload the zone so the changes take effect immediately.
4) /var/named/usr/$user/$zone.temp is deleted.

Well that's some of how the core works. It's a tight system.