The Server resolves to the IPv4 and not to the Floating IP in the Digital Ocean instance.
The Admin Panel can be seen with ipv4/admin but the domain/mail not loading, I can see the A record is set to the IPv4 and not the Floating IP.
Anything I missed?
Using an external tool, such as gwhois.org, does it show the expected name server and DNS records?
What does the browser show when you navigate to
This site can’t be reached.
The admin dashboard loads only with ipv4/admin, not with floatingip/admin.
No, example .com/admin doesn’t load.
You have some local networking or caching issue. Everything loads fine from here.
You can see robohike.com ?
/mail load as expected.
so strange, Its actually working on a different network.
I am assuming you are aware that you are using an unusual naming scheme from the MiaB default (
ns1.box.example.com, etc.). Though not a problem when managed correctly, and not the cause of what you are currently seeing, it may create some unexpected errors in the future, even if only in the MiaB status checks or dashboard.
If you have only recently changed your NS records, your local caching resolver may still be using the previous record TTL. It could even be just your browser or computer.
Yes, I want the main domain to show the login page, and not box.robohike.com.
Can we do it with box.robohike.com hostname too ?
If by login page you mean the webmail, all domains hosted on MiaB will navigate to the Roundcube login with
example.com/mail including subdomains, so long as there is an A record pointing to MiaB.
I see, and will the exmple.com will auto route to example.com/mail ?
If the A record points to MiaB, then yes.
Ok, thanx a ton for your prompt reply, really appreciate that.
I just realized I may have misread this question.
If you want to redirect all requests for
example.com/mail/, one way is to create the file
/home/user-data/www/example.com/index.html and add:
<meta HTTP-EQUIV="REFRESH" content="0; url=//example.com/mail/" />
<p>Redirecting to webmail.</p>