Hi. This is the webpage for my bind config files. It's not the best, nor the most complete, but it's what works for me.

It, like the firewall page, is fairly ugly. I'll fix this one at the same time as that one.

There are 4 files that you need to run a domain.

• named.conf - this is the bind config.
  Changes needed
  • Change clanspum.net to your domain
  • Change the reverse DNS zone to your IP. [1]
  • If you're not using 1and1.com, change the forwarders.
• 127.zone - the localhost zone.
  You can probably use this with no changes, unless you want 127.x.x.x to resolve to something. You don't.
• 142.248.160.217.in-addr.arpa.zone - Reverse DNS
  Changes needed
  • Use your IP address, not mine. [1]
  • Use your domain name, not mine.
  • Update the serial number [2]
• clanspum.net.zone - The domain zone
  Changes needed
  • Use your domain name, not mine.
  • Use your IPs, not mine.
  • Add whatever aliases you want.
  • Update the serial number [2]

Footnotes

1. Reverse DNS zones have their octets reversed. If you had the IP 1.2.3.4, your reverse DNS would be in 4.3.2.1.in-addr.arpa.
2. Tradition says your serial number is the date you changed the zone, in YYYYMMDD form. The idea is, when you update, you're assured that the new serial number is greater than the old one. You don't have to follow this schema, but you have to do two things:
   1. Always increment the number when you make an update
   2. Make sure it doesn't overflow the integer the serial is held in. I think that it is an unsigned 32 bit integer, so you've got some room.
   Other common schemes are YYYYMMDDHH, YYYYMMDDNN (where NN starts at 0, and is the count of how many times that day the zone has been updated), or N (where N is the total number of updates).