I am hosting an Ubuntu 18.04 server myself in my own private cloud. I used Gandi and followed the directions to a T for configuring glue records and pointing DNS back to ns1.box.mydomain.com. Reverse dns is not working at all. It’s been 24 hours since I updated the glue records and dns. Any help would be greatly appreciated. About to give up!
root@box:~# nslookup x.x.x.x
** server can’t find x.x.x.x.in-addr.arpa: NXDOMAIN
All private info removed from below: (x.x.x.x, mydomain)
System
✖ SSH Login (ssh) is running but is not publicly accessible at x.x.x.x
✖ Public DNS (nsd4) is not running (port 53).
✖ Incoming Mail (SMTP/postfix) is running but is not publicly accessible at x.x.x.x
✖ Outgoing Mail (SMTP 465/postfix) is running but is not publicly accessible at x.x.x.x.
✖ Outgoing Mail (SMTP 587/postfix) is running but is not publicly accessible at x.x.x.x.
✖ IMAPS (dovecot) is running but is not publicly accessible at x.x.x.x:993.
✖ Mail Filters (Sieve/dovecot) is running but is not publicly accessible at x.x.x.x:4190.
✖ HTTP Web (nginx) is running but is not publicly accessible at x.x.x.x:80.
[show more](https://box.mydomain.com/admin#)
✖ HTTPS Web (nginx) is running but is not publicly accessible at x.x.x.x:443.
[show more](https://box.mydomain.com/admin#)
✖ The SSH server on this machine permits password-based login. A more secure way to log in is using a public key. Add your SSH public key to $HOME/.ssh/authorized_keys, check that you can log in without a password, set the option 'PasswordAuthentication no' in /etc/ssh/sshd_config, and then restart the openssh via 'sudo service ssh restart'.
✓ System software is up to date.
✓ Mail-in-a-Box is up to date. You are running version v0.54.
✓ System administrator address exists as a mail alias. [administrator@box.mydomain.com ↦ info@mydomain.com]
✓ The disk has 38.62 GB space remaining.
✓ System memory is 91% free.
Network
✓ Firewall is active.
✓ Outbound mail (SMTP port 25) is not blocked.
✓ IP address is not blacklisted by zen.spamhaus.org.
box.mydomain.com
✓ DNSSEC 'DS' record is set correctly at registrar.
✖ Nameserver glue records are incorrect. The ns1.box.mydomain.com and ns2.box.mydomain.com nameservers must be configured at your domain name registrar as having the IP address x.x.x.x. They currently report addresses of [Not Set]/[Not Set]. It may take several hours for public DNS to update after a change.
✖ This domain must resolve to your box's IP address (x.x.x.x) in public DNS but it currently resolves to [Not Set]. It may take several hours for public DNS to update after a change. This problem may result from other issues listed above.
✖ Your box's reverse DNS is currently [Not Set], but it should be box.mydomain.com. Your ISP or cloud provider will have instructions on setting up reverse DNS for your box.
? The DANE TLSA record for incoming mail is not set. This is optional.
✓ Hostmaster contact address exists as a mail alias. [hostmaster@box.mydomain.com ↦ administrator@box.mydomain.com]
✓ Domain's email is directed to this domain. [box.mydomain.com has no MX record, which is ok]
✓ Postmaster contact address exists as a mail alias. [postmaster@box.mydomain.com ↦ administrator@box.mydomain.com]
✓ Domain is not blacklisted by dbl.spamhaus.org.
✖ The TLS (SSL) certificate for this domain is currently self-signed. You will get a security warning when you check or send email and when visiting this domain in a web browser (for webmail or static site hosting).
mydomain.com
✓ DNSSEC 'DS' record is set correctly at registrar.
✖ The nameservers set on this domain are incorrect. They are currently [Not Set]. Use your domain name registrar's control panel to set the nameservers to ns1.box.mydomain.com; ns2.box.zcloudservices.com.
✖ This domain's DNS MX record is not set. It should be '10 box.mydomain.com'. Mail will not be delivered to this box. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.
✓ Postmaster contact address exists as a mail alias. [postmaster@mydomain.com ↦ administrator@box.mydomain.com]
✓ Domain is not blacklisted by dbl.spamhaus.org.
✖ This domain should resolve to your box's IP address (A x.x.x.x) if you would like the box to serve webmail or a website on this domain. The domain currently resolves to [Not Set] in public DNS. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.
✖ www.mydomain.com: This domain should resolve to your box's IP address (A x.x.x.x) if you would like the box to serve webmail or a website on this domain. The domain currently resolves to [Not Set] in public DNS. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.
✖ autoconfig.mydomain.com: This domain should resolve to your box's IP address (A x.x.x.x) if you would like the box to serve webmail or a website on this domain. The domain currently resolves to [Not Set] in public DNS. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.
✖ autodiscover.mydomain.com: This domain should resolve to your box's IP address (A x.x.x.x) if you would like the box to serve webmail or a website on this domain. The domain currently resolves to [Not Set] in public DNS. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.
indicate a problem. Some of those are drop-dead problems … all those port-not-accessible lines are problems. The rest of the world has to be able to contact your server at ports 22, 25, 53, 80, 443, 465, 587, 993, 995, 4190 - if you’re running behind a firewall, those ports have to be open through to your box. (You may need to contact your server provider to open those ports.)