Reverse DNS (PTR) Problems Exist - server

I face an anonymous issue in my reverse PTR record in WHM Panel.
I Update all PTR record Using SSH command and adding a DNS Zone
Just You can See the image
here is SSH Command and result
DNS Zone name
DNS Records
Now when I visit the Email Deliverability menu from whm panel than my DKIM & SPF Record is valid
But My Reverse DNS (PTR) Problems Exist
And I face two different errors in same place.
But It shows randomly
Some time shows these errors
There is no reverse DNS configured for the IP address (50.2.223.14) that the system uses to send this domain’s outgoing email.
To fix this problem, create the following PTR record at “rdns1.serverhubdns.com” and “rdns2.serverhubdns.com”:
When I refresh this page again and again the errors changed randomly and show these error
The system sends the domain “eothan.brmidia.info” in the SMTP handshake for this domain’s email. “eothan.brmidia.info” does not resolve to any IP addresses.
To fix this problem, create a DNS “A” record for “eothan.brmidia.info” whose value is “50.2.223.14”.
And when I try to add DNS A record here shows A record already exits
How can I solve this issue?

Related

Reverse IP configuration in a VPS with several registered domains to avoid spam mails

Hello everyone in the community.
I have a headache that you can't imagine with this topic and I need your help.
I have a VPS server contracted at OVH, where I have access to the WHM and the Cpanel.
I currently have two hosted domains, I have created for each one their account in Cpanel, so each domain has its own configurations: Ftp, Mail etc...
The problem is that the mail that comes out of any of these domains are going directly into SPAM. I've read a lot on the internet, there's talk about configuring the PTR, configuring a reverse IP and so on.
The thing is that I am confused because I have two different domains, with all their different characteristics and the OVH server is one with one IP and already has its reverse IP.
So when I check the CPANEL of each account in the Email Deliverability option it tells me that there is a problem with the PTR.
The truth is that I have no idea how to change this for each domain, each domain appears in the DNS zone of the WHM and I can edit or add what I need but I see that everything is fine.
I don't know what to change or how to change it. I hope you can guide me. Thank you
Your cPanel/WHM server ip address has to have a valid PTR record which should matche your server's hostname. If the PTR doesn't match the hostname then that's a reason your emails go to SPAM. You should also check your server ip address to see if it's listed in any blacklist. You can check that on mxtoolbox.com for example. You also need to have valid DKIM, SPF and DMARC dns records for your domains.

ISPConfig set up reverse DNS

I have an Ubuntu 16.04 server with ISPConfig 3.1.
I set up many websites and emails, but when I send an email to a certain email address I have the following error:
Your server IP address [186.156.31.17] does not have a valid reverse
550-DNS entry [pc-17-31-156-186.cm.vtr.net]. see
550-http://spamauditor.org/best-practices/check_dynamic_reverse_dns/
for
more 550-information. Protection provided by MagicSpam 2.1-8.3 550
http://www.magicspam.com (in reply to RCPT TO command)
How can I set up reverse DNS in ISPConfig? I learned that I need a PTR record but I'm not sure how to do it correctly.
This isn't something you can configure from your end unless your ISP has specifically given you the ability to do it.
Linode, for example has a button for it, but if you don't, you would need to contact your ISP.
Normally individuals don't have access to the rDNS records

AWS EC2 Reverse DNS (PTR) Failing

Have searched everywhere, can't find answer.
I have the domain mydomain.com. The root and www records point to my main server, which runs my website.
I am now using a separate AWS ec2 instance to set up an email server for my domain. This is running on the subdomain mail.
My dns looks like this:
A # webserverip
A www webserverip
A mail ec2ip
To prevent my server from getting flagged for spam, I submitted the amazon reverse dns form here: https://aws.amazon.com/forms/ec2-email-limit-rdns-request
I gave them the ip of my ec2 mail server, and put "mail.mydomain.com" in the "Reverse DNS Record for EIP 1" box.
However, I keep receiving emails back from them saying:
When attempting to map the reverse DNS entry, we notice that this is failing because the PTR record doesn't match the A record for that domain.
We currently require the forward A record to match the PTR record for all reverse DNS entries.
I really don't understand what I am doing wrong. The "mail" subdomain has an A record pointing to my ec2 server ip. Any assistance would be greatly appreciated!
(I am using cloudflare for my dns if this makes any difference)
You can follow these steps to configure the DNS for your EC2 dedicated mail server on AWS:
STEPS
Add two A host records for pop.mydomain.com and
smtp.mydomain.com that point to your elastic IP and assign your
MX record to the smtp.mydomain.com host.
Add a CNAME record (not A host record) for mail.mydomain.com that points to the DNS entry assigned by AWS (e.g., ec2-XXX-XXX-XXX-XXX.REGION.compute.amazonaws.com).
Submit your rDNS request for smtp.mydomain.com mapping to your EIP.
Don't forget to add the SPF TXT record for your mail server. For example, v=spf1 mx a
Once you're done with this setup, you should have a proper mail server configuration in terms of DNS that would pass SMTP tests and avoids being flagged as spam.

temperror when email is sent to hotmail & end up in junk/spam folder

When i send emails to hotmail main inboxes it ends up in spam/junk folder with the following in the header:
Authentication-Results : hotmail.com; spf=temperror (sender IP is X.X.X.X)
smtp.mailfrom=marieke#X.X; dkim=temperror header.d=X.com; x-hmca=none
However, both the Dkim and Spf are good since at least one week, and it shows "pass" when an email is sent to gmail. By the past, the domain was hosted on a different server with a different spf and dkim record in the DNS.
Is it possible that microsoft servers don't do a DNS lookup or perhaps a DNS lookup from time to time?
There are several reasons why it happens:
First of all, the microsoft DNS lookup takes some time due to the TTL of DNS records, perhaps several weeks.
Then, my mistake was to set up two A records for my smtp server hostname rather than one. Consequently due to round robin, the Forward Confirmed Reverse DNS Lookup failed from time to time as the wrong IP address was returned from time to time. Consequently if you have a smtp mail server, you should only have one A record (and one AAAA record), meaning one IP address for it.
IPv4:
One server hostname = Only ONE IP address (A record)
One IPv4 address = Only ONE server hostname (Reverse DNS)
IPv6:
One server hostname = Only ONE IP address (AAAA record)
One IPv6 address = Only ONE server hostname (Reverse DNS)

Own mailserver for newsletters SPF record issues

At our business we are running a server for sending newsletters. Setting up the server and sending bulk e-mails is not the issue. That's all working fine.
I run a test on www.mail-tester.com to see how good the mail will pass spam filters. But unfortunately, we are running stuck on the SPF records.
Our setup:
ISP: Business fiber connection with fixed IP. The ISP has setup our hostname as "mail.ourbusiness.com" (fictional domain name)
Website: Our website www.ourbusiness.com is hosted in a datacenter and has nothing to do with our ISP.
The following errors occur:
You're not fully authenticated
We found an SPF entry on your server but it has still not been propagated
Your message is not signed with DKIM
See list of the complete fault message.
It say's that our business IP is successfully associated with mail.ourbusiness.com (so that's good).
Now my question: What should our SPF record be? I can find enough information about SPF records, but I have totally no clue of what I need to put into it!
Oké, solved this issue regarding the SPF record. mail-tester.com has now validated the mail successfully and gives it a 8.8 out of 10.
I did the following in the DNS of our domain ourbusiness.com.
Added A record form subdomain mail.ourbusiness.com with the content the IP address of our ISP.
Added SPF record for subdomain mail.ourbusiness.com
A record
mail.ourbusiness.com A 123.123.123.123
** SPF record **
mail.ourbusiness.com TXT v=spf1 a include:mail.ourbusiness.com ~all