It really depends on what you want/need.
If you would like to host your own DNS servers, then multi location is a
good idea:
Example: Master NS1 in LA and Slave NS2 in Miami.
I have no idea about GoDiddy but my US based domain hosting company
let's me specify my own ns servers, as their DNS hosting is a little
limited for what I need.
Just whack Bind9 onto both systems in master/slave setup, and away you
go. DNS isn't really complicated so you should be up and running in no
time. ;-)
Once that's done a good online tool for checking certain parts of the
domain is: https://mxtoolbox.com/ but then don't forget your local tools
such as nslookup and dig!!
Regards,
Kaya
On 1/18/19 6:38 PM, Chris Bennett wrote:
I have had problems with setting up DNS for myself and I need it to be
authoritative.
I have my domains registered with Godaddy and they do not support for
domains not hosted on their servers. I have been using their DNS without
big problems, except that I'm not getting proper results with regards to
email. I've got a pretty bad problem with spam. I now have two servers,
each with a different company.
Will that then solve the problems with PTR, DKIM and DMARC?
I also particularly hate the web GUI that Godaddy uses and it's SOA
record is much too long timewise.
Should I set it up with just one of my servers or both?
One is in Los Angeles and the other is in Miami.
Do I need to use a different one to cover the other server or can I just
use the same one to cover the email stuff like DKIM and DMARC?
Since I'm having problems from the ground up, this seems like a good
idea to start at.
I'm also seeing conflicting advice on whether I should use multiple A
records for subdomains, like www. smtp. etc. or CNAME.
Plus it's not clear to me whether to use records like _smtp.tcp or not
bother with those.
I have spent a lot of time reading pages on all of these subjects but I
have yet to find a complete example of all DNS records for a site.
Would anyone care to share one with me?
Thanks,
Chris Bennett
