Used instructions from http://ubuntuforums.org/showthread.php?t=236093 to configure DNS server with BIND9.
Note that the instructions for the file /etc/bind/zones/rev.0.168.192.in-addr.arpa are missing a period after the last address (example.com should be example.com.). We also had to name our revers file “rev.3.39.64.in-addr.arpa” rather than “rev.0.3.39.64.in-addr.arpa”. Note this name change must be reflected also inside of the file /etc/bind/zones/rev.3.39.64.in-addr.arpa, and in the file /etc/bind/named.conf.local.
“example.com” = “team1.isucdc.com” in file /etc/bind/named.conf.options, “188.8.131.52” = “184.108.40.206” (proxy)
Changes to the file /etc/bind/zones/example.com.db (which is /etc/bind/zones/team1.isucdc.com):
example.com. IN SOA ns1.example.com. admin.example.com changed to example.com. IN SOA dns.team1.isucdc.com. admin.example.com
example.com. IN NS ns1.example.com. changed to team1.isucdc.com. IN NS dns.team1.isucdc.com
Removed: example.com. IN MX 10 mta.example.com
www IN A 220.127.116.11
dns IN A 18.104.22.168
mon IN A 22.214.171.124
rdp IN A 126.96.36.199
chat IN A 188.8.131.52
Checked for vulnerabilities to BIND9. There are four related to malformed queries; all can cause the server to fail. However, there are no workarounds at this time.