First off, let's see what root servers say about your NS.
$ whois zenodine.net
Name Server.......... NS15A.BOCA15-VERIO.COM
Name Server.......... NS15B.BOCA15-VERIO.COM
Now let's ask ns15a.boca15-verio.com:
$ dnsq any zenodine.net ns15a.boca15-verio.com
255 zenodine.net:
273 bytes, 1+5+2+4 records, response, authoritative, weird ra, noerror
query: 255 zenodine.net
answer: zenodine.net 86400 A 208.55.91.110
answer: zenodine.net 86400 MX 50 mail-fwd.boca15-verio.com
answer: zenodine.net 86400 NS ns15a.boca15-verio.com
answer: zenodine.net 86400 NS ns15b.boca15-verio.com
answer: zenodine.net 86400 SOA feed15.boca15-verio.com hostmaster.boca15-verio.com 2001081315 7200 3600 604800 86400
authority: zenodine.net 86400 NS ns15a.boca15-verio.com
authority: zenodine.net 86400 NS ns15b.boca15-verio.com
additional: mail-fwd.boca15-verio.com 7200 A 208.55.91.60
additional: mail-fwd.boca15-verio.com 7200 A 208.55.91.61
additional: ns15a.boca15-verio.com 7200 A 208.55.91.50
additional: ns15b.boca15-verio.com 7200 A 208.55.91.51
Oh no, verio.com sucks, because they have misconfigured your zone record. Like I always said, BIND people or the people who run BIND mostly don't have a clue about DNS.
1) weird ra:
That means recursion is available with a setting of recursion yes; within the options { in named.conf.
Doing recursion is just lame, waste of resource, like running open relay SMTP for anyone in the world (including spammers) to use your dns cache. In addition, recursion is highly vulnerable to DoS attack to your DNS.
2) feed15.boca15-verio.com:
This field is so-called MNAME and it MUST be your primary DNS's FQDN. That said, it should be ns15a.boca15-verio.com instead.
Now that you know verio.com sucks so it makes sense to run your own DNS.
>> IP's = 8
You mean you have 8 static IPs? What are they?
>> resolv.conf File created everytime server is booted.
Because your box is configured to ask a DHCP server. Just set IP manually then you're fine.
>> version"";
>> auth-nxdomain no;
>> recursion no;
These options are great. Where did you find them? In addition, you should add fetch-glue no; and allow-transfer { ip.of.your.secondary; };
named.conf, change the following:
zone "0.0.127.in-addr.arpa" {
type master;
file "localhost.zone";
}; to:
zone "0.0.127.in-addr.arpa" {
type master;
file "localhost.zone";
allow-transfer { none; };
notify no;
};
localhost.zone file:
$TTL 3D
0.0.127.in-addr.arpa. IN SOA ns1.zenodine.net. webmaster.zenodine.net. (
20010507; Serial
8H ; Refresh
2H ; Retry
4W ; Expire
3D ); Minimum
0.0.127.in-addr.arpa. IN NS ns1.zenodine.net.
0.0.127.in-addr.arpa. IN NS ns2.zenodine.net.
1.0.0.127.in-addr.arpa. IN PTR localhost.
zenodine.net file change to:
$TTL 86400
zenodine.net. IN SOA ns1.zenodine.net. webmaster.zenodine.net. (
2002022304 ; serial
12H ; refresh (setting 24H is way too high)
1800 ; retry
2W ; expire (don't set 1 week - 604800)
1D ); default_ttl (move that closing ) on this line)
zenodine.net. IN NS ns1.zenodine.net.
zenodine.net. IN NS ns2.zenodine.net.
ns1.zenodine.net. IN A server-ip-address-1-here
ns2.zenodine.net. IN A server-ip-address-2-here
zenodine.net. IN A server-ip-address-1-here
localhost.zenodine.net. IN A 127.0.0.1
www.zenodine.net. IN A server-ip-address-1-here
zenodine.net. IN MX 0 ns2.zenodine.net.
Your mail.zenodine.net has no A record, you can't do that. mail.zenodine.net also hasn't been delegated to have its own zone.
With these settings, your DNS is all set. You can contact verio.com and tell them to ***** off and update the new changes. Later on when everything is up and running you should contact verio.com again and ask if they can change the PTR records for your assigned IPs to the appropriate FQDN, so you can have a matching reverse DNS. Like I always said, having a matching reverse DNS is not required, but it makes huge difference if you have them.