Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Writing a brief best practices technical document for in house.

  • A Records for hostname / IP mapping
    * -can also add subdomain, ftp, cpanel, etc depending on setup
  • MX Records (if sending and/or receiving email at this domain)
  • NS & SOA records for Nameservers
  • TXT & possibly CNAME for SPF / DKIM authentication depending on setup and needs

Are there any missing DNS records that should be added to most record sets? Any changes or additions?

share|improve this question

closed as primarily opinion-based by MadHatter, Jenny D, EEAA, Ward, mdpc Jul 17 '13 at 19:08

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

Personally I find this question a bit subjective. Other than SOA and NS records, the rest are optional as far as I'm concerned. Do I need a record for FTP? Not if I don't have an FTP server and even then I could call it whatever I want. This is a bit like asking "What kind of cheese should I have on my sandwich?". – joeqwerty Jul 17 '13 at 16:36
Thanks Joe. That's why I'm asking. Obviously a lot are subjective but are any important ones missing or misconfigured? And how about Havarti? – csi Jul 17 '13 at 16:51

PTR for reverse dns lookups

AAAA for IPv6 hosts (you clearly aren't doing IPv6 today, but certainly any new best practices should mention this).

In some ideal world, RRSIG, DNSKEY, et al, for DNSSEC

share|improve this answer
PTR would be necessary only if sending outbound mail from the domain or would I need it in other situations? – csi Jul 17 '13 at 16:48
It's not strictly necessary under any circumstances, although you are correct that it's often used as a spam check. However, if you are talking "best practices" you should definitely have PTR records for all your IPs. – Dan Pritts Jul 17 '13 at 18:01

SPF should be included in your list. You can use TXT for older systems but newer systems (client and server) support the SPF resource record. RFC4408 suggest using both.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.