Diagnosis says Reverse DNS is not correctly configured

What type of hardware are you using: VPS bought online
What YunoHost version are you running: 12.0.6
How are you able to access your server: The webadmin
SSH

Describe your issue

Hi, I’ve configured reverse DNS as instructed with my provider. However, Diagnosis keeps telling me it’s not. What seems to be the issue?

Share relevant logs or error messages

Reverse DNS is not correctly configured for IPv4. Some emails may fail to get delivered or be flagged as spam.

Current reverse DNS: static.xxx.xx.xx.xx.clients.your-server.de
Expected value: mysubdomain.mydomain.tld
You should first try to configure reverse DNS with yunohost.texttheater.net in your internet router interface or your hosting provider interface. (Some hosting providers may require you to send them a support ticket for this).
Some providers won't let you configure your reverse DNS (or their feature might be broken…). If you are experiencing issues because of this, consider the following solutions:
- Some ISP provide the alternative of using a mail server relay though it implies that the relay will be able to spy on your email traffic.
- A privacy-friendly alternative is to use a VPN *with a dedicated public IP* to bypass this kind of limits. See https://yunohost.org/vpn_advantage
- Or it's possible to switch to a different provider

No reverse DNS is defined in IPv6. Some emails may fail to get delivered or be flagged as spam.

You should first try to configure reverse DNS with yunohost.texttheater.net in your internet router interface or your hosting provider interface. (Some hosting providers may require you to send them a support ticket for this).
Some providers won't let you configure your reverse DNS (or their feature might be broken…). If your reverse DNS is correctly configured for IPv4, you can try disabling the use of IPv6 when sending emails by running yunohost settings set email.smtp.smtp_allow_ipv6 -v off. Note: this last solution means that you won't be able to send or receive emails from the few IPv6-only servers out there.

Fixed it – in case this helps others:

  • For IPv4: Seems like I was just too impatient; after about 24h the warning disappeared.
  • For IPv6: I had entered the Reverse DNS incorrectly (in Hetzner Cloud in my case). Turns out the pre-set value of xxxx:xxxx:xxxx:xxxx was not enough, I had to add the suffix ::1. This then also took a few hours before the warning disappeared.
1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.