Incorrect Subdomain Redirects to New Subserver Index Page (NGINX/LEMP)

[WoozyFace]

SYSTEM INFORMATION
OS type and version	Debian Linux 12
Webmin version	2.202
Usermin version	2.102
Virtualmin version	7.20.2
Server/Installation type	Nginx LEMP
Kernel and CPU	Linux 6.1.0-26-amd64 on x86_64

Hi everyone,

This is a continuation of an issue I discussed in a previous thread: Issues Disabling Apache after Failed Installation on Virtualmin.

To recap briefly: when I add a new virtual subserver for correct-domain.com, I’m noticing that subdomains under .incorrect-other-domain.com (e.g., randomstuff.incorrect-other-domain.com) are incorrectly redirecting to the new subserver’s index page, making it seem like that’s the new default location.

I’ve followed the Virtualmin Troubleshooting FAQ as much as I could. Everything IP-related and the relevant settings seemed correct according to the FAQ, but the last step was Apache-related, and since I’m using a LEMP stack, I wasn’t sure how to proceed there.

Is there something specific to Nginx that I should be checking to resolve this issue? I might be able to dig through some config files, but I’d love a bit more guidance, especially for those who might be even less familiar with these configurations. Any advice on how to stop these subdomains from redirecting would be greatly appreciated!

Thanks in advance!

[Stegan]

@WoozyFace

Is there something specific to Nginx

No nothing
The sub servers should be pointing to their own sub-server default page:
eg. my-subserver.main-server.com but just to check things go to the “List Virtual Servers” Page and make that page more useful by changing the settings (click on the cog icon in the top left), then check the ‘Domain type’ in the columns to show. Go back to other list, it should now be showing the sub-server slightly indented under the main server.

If you click on the sub-server and go back to the main Virtualmin menu under “Web Configuration → Preview Website” it should open the default page.
assuming that you have not added anything to your website yet
(always a simple check before you add content to potentially the wrong place)

[WoozyFace]

The issue seems to be resolved since I started to use the NS & DNS module bind9. Guess that it had something to do with the a *.domain.com A record.