ReverseDNS Question

[scarlett]

When I'm setting up the ReverseDNS for a server - for mail servers, is it acceptable for it to be the codename for the server? Or does it have to be mail.domain.tld? Like, say my server name was jack.... is jack.mydomain.tld acceptable? Or will it give me problems with MTAs on other hosts accepting my e-mails? It's not just hosting the mail server, but all services including web and MySQL.

 

[RDO Servers]

Your rDNS records can be set to anything you want. The only thing that makes much difference is mail. Even then, you just have to make sure you're consistent.

i.e. you can set your mail as ethgergreg.domain.com, as long as all of your other mail records are also set the same.

 

[hostslim]

The best way to make it the same as your domain. For instance mail.yourdomain.tld or yourdomain.tld

 

[m3server]

This is really your choice. We have found over the years it has worked best for us to keep it simple.

server name bob.m3server.com
rev dns bob.m3server.com

No reason to make things complicated.

 

[ElixantTechnology]

Remember to update your exim settings to reflect the RDNS; best practice is to have everything reflect your servers host name. Note that some DNSBL will list you for improper configurations among other things. Be sure a valid A record is pointing to your RDNS [AND] you aren't using a standardized RDNS such as 1.1.1.1.domain.com or 1-1-1-1.domain.com as some DNSBL will list you for this as well.

What I do for my IP blocks is assign a standard PTR such as:

158-69-157-32.in-addr.elixant.net

Not only does this help in indentifying addresses, but also creates a standardized PTR that motivates customers to set their own. The above is *not* recommended if you are meaning to run an email server.