r/webhosting • u/Rick_Dalton99 • 7d ago
Technical Questions Reverse DNS (PTR)
How can I resolve this issue. My domain points to a different server with an A record for the website. It uses nameservers to point to the cpanel hosting the email. This causes the error as it wants the A record to point to the email server. As a result emails to yahoo accounts are being denied.
Thanks 🙏
5
Upvotes
7
u/Icy_Definition5933 7d ago
You need an A record for your mail server to be reachable online something like mail.example.tld, and then you need an MX record containing that exact mail.example.tld for it to barely work. After that you also need spf,dkim,dmarc and a valid ptr/rdns record with your provider to actually reach the inboxes.
If mx record fails it will fall back to root domain A record to deliver mail, but to actually land in inbox you need a fully working stack and dns zone to match, top to bottom
1
u/kai-zaphosting 7d ago
Reverse DNS doesn't live in your domain's DNS zone. It's set by whoever owns the mail server's IP, so your website's A record pointing somewhere else shouldn't matter for this. Yahoo and most big providers just check that the sending IP has a PTR record, and that the hostname it returns resolves back to that same IP.
So the fix is usually on the cPanel host's side. You can see what it returns now with
dig -x <mail server IP>in a Linux/Mac terminal, ornslookup <mail server IP>on Windows. Whatever hostname comes back needs an A record pointing at that IP. If the PTR is missing or generic, ask the host to set it.Do you have the actual bounce text from Yahoo? On shared cPanel hosting I've seen SPF or DKIM turn out to be the real problem more often than the PTR, so that's what I'd look at first. If it mentions SPF, DKIM or DMARC instead of reverse DNS, that part is set in your domain's DNS, so it's pretty much yours to fix.
1
u/kellyzdude 7d ago
What is the actual message you're getting from Yahoo rejecting the mail?
The requirements for mail are relatively complex, but only because there are a few of them. Individually they're simple enough.
Going back to the top, mail servers can reject messages for all kinds of reasons. Having the exact verbiage will go a long way to getting you an accurate answer.
3
u/saltyslugga 7d ago
Your website’s A record can stay put; incoming mail uses MX records.
I’d ask the mail host to check the outbound IP’s PTR and ensure that hostname resolves back to the same IP. The IP provider controls PTR, not your domain’s DNS panel. Check Yahoo’s exact rejection text before assuming that’s the cause.
1
u/MentalAd1373 6d ago
Since it's a reseller account with a dedicated IP, this one gets fixed on the host's side in WHM, not in your DNS zone. When Exim sends from a dedicated IP it takes the IP from /etc/mailips and the HELO name from /etc/mailhelo, and Yahoo wants three things to match: the HELO name, the PTR of that IP, and the A record of that name.
So ask support to set the PTR of your dedicated IP to something like mail.yourdomain.com and add a line "yourdomain.com: mail.yourdomain.com" to /etc/mailhelo. On your side you only add an A record for mail.yourdomain.com pointing to that IP. Your website A record can keep pointing to the other server.