Hello,
Before discussing PTR records with your ISP, let’s first verify that the DNS configuration is correct. From a Linux shell, replace the examples below with your actual mail server hostname, domain, and public IP address.
Check that the mail server hostname resolves to the public IP:
dig +short mail.example.com A
The output should be your public static IP address.
Check that the reverse DNS (PTR) points back to the mail server hostname:
dig +short -x 203.0.113.10 PTR
The output should be:
mail.example.com.
Check the MX records for each mail domain handled by NS8:
dig +short example.com MX
The output should contain your mail server hostname.
Check the SPF record:
dig +short example.com TXT
Look for a record similar to:
"v=spf1 mx -all"
Check the DKIM record generated by the Mail application. The selector name can be found in the Mail UI:
dig +short mail._domainkey.example.com TXT
Check the DMARC record:
dig +short _dmarc.example.com TXT
Once you have verified these records, please share the output (masking any sensitive information if needed).
Regarding the Hyper-V setup, if the Debian web server and NS8 Mail are both behind the same public IP, you cannot forward ports 80 and 443 from the MikroTik to two different servers at the same time.
A few questions:
- Is the Debian web server hosting public websites?
- Is NS8 only being used for Mail?
- Are both servers using the same public IP address?
If NS8 is only handling email, it usually requires SMTP ports (25, 465, 587, 993, etc.). However, Let’s Encrypt certificate validation and webmail access may still require ports 80 and/or 443, depending on your setup.
Please provide a network diagram or a description of the current port forwarding rules on the MikroTik and we can suggest the most suitable solution.
Thanks in advance, and good luck with the ISP call tomorrow. The key point to explain is that the PTR record must resolve your public IP address back to the same mail server hostname used by the SMTP server during mail delivery.