Skip to main content
We are aware of an issue with a recent Apache update that causes proxied sites to return a "421 Misdirected Request" error. Please see the following article for more information and updates:
Websites show 421 Misdirected Request error while using EA Nginx

Sub-domain doesn't resolve on all servers

Michael Lechasseur

After a migration to a AlmaLinux 8 server, a subdomain created under it's own WHM/cPanel account doesn't resolve on some DNS servers. On most it does resolve. I assume I have misconfiguration somewhere. 

"Allow cPanel users to create subdomains across accounts" is now enabled under Tweak Settings. (I have only my own sites on the server..)

Under the main domain, there is no A record for the sub-domain created in the seperate account.
Under the subdomain account, there is an A record for the subdomain.

Is that the correct aproach? Any other required records to add?

Is there any sort of DNS rebuild script I should run? I'm hesitant to run "DNS clean-up" for fear of losing what setup I do have working.

I've restarted the DNS service and rebooted to no avail.

Thanks for any input.. I've attempted to use nslookup and dnschecker.org to help troubleshoot, but I'm not sure what specifically I'm looking for.

Thank you!

Comments

3 comments

Date Votes
  • cPRex Jurassic Moderator

    Hey there!  When you say a domain doesn't resolve "on some DNS servers" can you get me more details on how exactly you're testing that, or what failures you're seeing?

    My favorite online tool for DNS issues is intodns.com as that scans the domain in real-time and tells you exactly what is wrong.  I believe the error listed there should help get you pointed in the right direction when you scan your main domain.

    I've edited the post to remove that subdomain.

    0
  • Michael Lechasseur

    Thanks for pointing me to the intodns.com. It's so helpful.

    I've corrected the A record for my ns2 to match the IP made at the registry for the DNS.

    Other than an online tester like dnschecker.org I don't have a way to verify why my subdomain wasn't loading. The issue for some resulted in error DNS_PROBE_FINISHED_NXDOMAIN in the browser window, which apparently cause by being unable to resolve the IP from the domain name.

    Locally, users on the Rogers ISP were getting the error. If I try to use their DNS (64.71.255.204 and 64.71.255.198 from my colleague's laptop).

    Using nslookup on my ISP I don't get a response from their DNS server. I assume because I'm not connected using their network.

    I'd like to find another method to test using their DNS servers.

    0
  • cPRex Jurassic Moderator

    You can always perform direct queries against any nameserver.  For example, if we want to see what Google says cPanel is pointed to, we can do this:

    # dig +short cpanel.net @8.8.8.8
    208.74.123.84
    208.74.121.151

    and get the answer directly from the 8.8.8.8 server.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post