| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Ubuntu 22.04.5 |
| Virtualmin version | 2.303 |
I’ve created sub-servers and subdomains (as parent sites) plenty of times on this server, all has worked fine.
The parent site - magnolia.host - is working fine. But I created cloud.magnolia.host - and it appears properly set up in virtualmin - but DNS is refusing to acknowledge it exists.
All features are enabled, DNS records appear to exist including the A record.
Where do I start?
Restart/reload bind?
Are you even doing the DNS?
Name Server: NS1.NULLUSANXIETAS.COM
Name Server: NS2.NULLUSANXIETAS.COM
How are you confirming that?
You should generally do something like:
host sub.domain.tld
From some other system. (Or nslookup, if you’re afflicted by Windows.)
My guess would be the DNS servers being managed by Virtualmin aren’t actually the DNS servers for the zone. Check that with:
whois domain.tld
This should be actual domain, not the subdomain name, since you need to look up the name servers for the zone, not the A records for the subdomain.
I am NullusAnxietas.com. 
So:
I had not previously restarted the server, but have now.
clouda.magnolia.host DNS in Virtualmin:
I chopped off the IP, but it is the main server’s shared.
I’ve also compared the records for nullusanxietas.com and cloud.nullusanxietas.com.
My knowledge of DNS is not expert, it’s midrange. so I notice the main domains have NS records, subdomains appear not to. This is true for cloud.nullusanxietas.com which is working as well as cloud.magnolia.host which is not.
Running bash locally on my system here:
EDIT: typo
I also registered magnoliahost.com — sorry for the typo, but cloud.magnolia.host results just above.
EDIT2: Dang it, I’d typed it wrong both times.
It’s failing NOW, but it had worked just a few mins ago before a server reboot:
FROM EARLIER:
Magnolia.host was working fine - I installed wordpress and built a site earlier today. Now it’s not loading in the browser. WTF???
dns propagation checker still shows it fr a couple, but it dropped off in the past few minutes - the ONLY thing I did was a server reboot!
edit: Remains set up at the registrar:
Also, I’d checked whois, but to clarify:
I get a weird error I’ve never seen before at mxtools. It maybe registrary settings or nameservers not setup correctly.
For magnolia.host have you created the NS records ie magnolia.host. NS ns1.nullusanxietas.com
Oops, thought I’d pasted a screenshot of that:
Ns are indeed ns1/2.nullusanxietas.com
I appreciate folks looking at this very much <3
And in a weird way, I feel slghtly better about it not being something SUPER stupid, at least. lol (or at least, seems that way so far)
I still don’t know what the heck caused problems, except that I set up MX records pointing to MXROUTE services. Just MX and… I forget now which of SPF/DMARC/DKIM. But none of the A or NS records, for example, for which I’d posted screenshots…
I don’t know why changing the MX records caused the domain to eventually disappear from external DNS providers, i.e. no longer able to be looked up…
At some point, I’ll experiment with a less important domain than my primary business domain, I suppose. I don’t know why messing with the MX records would cause the domain to stop working, but that’s apparently the cause as it happened three times - I deleted and recreated the virtual server, and it worked - until I messed with the MX records, then as caching ran out, the domain stopped being accessible from browsers or global DNS propagation checks.
Mostly coming back to add this in case anyone else runs across this problem and winds up in this thread.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
