DNS lokup failing for subdomain

Help! (Home for newbies)
1
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?

2

Restart/reload bind?
Are you even doing the DNS?
Name Server: NS1.NULLUSANXIETAS.COM
Name Server: NS2.NULLUSANXIETAS.COM

3

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.

1 Like
4

I am NullusAnxietas.com. :slight_smile:

So:

  1. NullusAnxietas.com resolves to the server and ns1/ns2 are successfully set up.
  2. That’s how magnolia.host itself is setup and is working
  3. Magnolia.host and cloud.magnolia.host were set up today, the former is working, the latter is not
  4. The magnolia.host virtual server and cloud.magnolia.host sub-server were both set up today in Virtualmin, the domain was regitered earlier today and ns setup there - all of the sites on my server use these nameservers, which are setup on the server and have been working for IIRC 18ish months just fine

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:

5

I get a weird error I’ve never seen before at mxtools. It maybe registrary settings or nameservers not setup correctly.

image
image1041×320 15.1 KB

For magnolia.host have you created the NS records ie magnolia.host. NS ns1.nullusanxietas.com

6

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)