There are a lot of problems with this zone, I'm not sure why it gets
completely loaded, I would think that it would have not loaded this zone.
> alzaredirect.com. IN NS 127.0.01
> IN NS NS1
> IN NS NS2
All of these NS records are suspect at best. I think that you would be
better off
NS1 and NS2 are not valid record entries as they are printed here, you
probably wanted:
IN NS ns1.edgefire.com.
IN NS ns2.edgefire.com.
> alzaredirect.com. IN A 64.224.206.4
> alzaredirect.com IN MX 13 mail.alzaredirect.com.
> alzaredirect.com IN MX 14 64.224.206.4
> alzaredirect.com. IN MX 15 alzaredirect.com.
This is already defined as mail.alzaredirect.com, there is nor eason to
repeat it with the IP and alzaredirect.com.
> 64.224.206.4 IN PTR .mail.alzaredirect.com
> 64.224.206.4 IN PTR .alzaredirect.com
> 64.224.206.4 IN PTR .ns.alzaredirect.com
PTR records belong in a reverse, or ARPA zone. They do not belong in the
forward zone, what you created are invalid entries for
64.224.206.4.alzaredirect.com. If these were valid PTR records, you would
also want them in reverse order. According to arin, Interland is responsible
for this reverse, but Interland doesn't seem to be answering for it. You
can't create reverse DNS unless interland is pointing to you to do it.
> www IN A 64.224.206.4
> mail IN A 64.224.206.4
> ns IN A 64.224.206.4
These records should be fine, but there are so many other problems in this
zone file, I doubt they would work.
-- Richard Maynard
|
