Jag: Fix your nameservers!

[Joshua Clinard]

I was looking at a DNS report for a domain that was not working. Then I went to compare it to a domain that is working, and there sure it a lot of fails and warnings on that page. I was amazed! These problems need to be fixed. Especailly the missing SPF record. Maybe this is why I have been getting bounced e-mails I didn't send.

http://www.dnsreport.com/tools/dnsre...shuasplace.net

Then I took a look at Jaguarpc.com, and there are even problems there. The SOA is too long, and the SPF is still missing.

http://www.dnsreport.com/tools/dnsre...n=jaguarpc.com

I think one of the problems is that Jag uses way too many different nameservers. There are just too many to maintain, and have them all be correct. I think they should use replication, so that they all report the same thing. I get someone who knows what they are doing to set these things up.

[Eric]

If you want something changed in your DNS zone because dnsreport.com doesn't agree with the setup, then you can open a ticket to get it all straightened out.

We have not added any SPF support yet and even it doesn't guarantee someone will not be able to send out mail appearing as if it came from you. From what I know about SPF, it all depends on whether or not the incoming mail server supports SPF.

The SOAs could be shortened a bit, but we usually only deal with them on an individual basis. We do not need secondary nameservers constantly querying our primary nameserver at all times.

We only run 4 different physical DNS servers and they all run replicated data to some degree. To be quite honest, I'm not sure I've heard anyone ever complain before because of too much redundancy. I won't go into how it all works, but it's not like we have to make the same change on every machine when one thing is changed.

Like I mentioned above, if you notice something that you'd like changed with your zone file, please let our technicians know.