A subdomain as an account's primary domain is not resolving locally

[RonanRBR]

I have an account with domain.tld as the main domain, so I created a second account with the main domain as sec.domain.tld.
Externally this domain sec.domain.tld resolves and pings normally to server's IP, but locally the shell cannot resolve and cannot ping to sec.domain.tld

This behavior did not happen before, I even have other old accounts in this similar situation and the local ping is able to resolve normally.
Any idea if it's a misconfiguration I've done or any idea what's causing this behavior?

Ps 1. I've already created an A record in the domain.tld zone pointing sec.domain.tld to the same server IP and it didn't work.
Ps 2. If I create a subdomain in the main account, like ter.domain.tld, works and the server can resolve locally, but if I create it as the main domain of another account it can't resolve locally.

CentOS 7.9 - cPanel WHM 98.0.5

 

[cPRex]

Hey there! This almost sounds like your resolver is either bad or hasn't yet received the DNS updates for that domain. Can you check /etc/resolv.conf on the server and try using these two entries in place of what is there to see if that changes the behavior?

nameserver 8.8.8.8
nameserver 8.8.4.4

Rather than remove the entries that are already there, you can just comment them out with "#" symbol for testing.

 

[RonanRBR]

Hey there! This almost sounds like your resolver is either bad or hasn't yet received the DNS updates for that domain. Can you check /etc/resolv.conf on the server and try using these two entries in place of what is there to see if that changes the behavior?

nameserver 8.8.8.8
nameserver 8.8.4.4

Rather than remove the entries that are already there, you can just comment them out with "#" symbol for testing.

I don't think so, because when I put ter.domain.tld as a subdomain of the main domain, it works and the server manages to resolve it for itself. But if I put ter.doamin.tld as the main domain, on the same server it can't resolve.
And as I said, before it was working and nothing has been changed, there are even old accounts that work.

 

[cPRex]

Well that just doesn't make any sense now does it? What if you try this from your local machine:

dig +trace sub.domain.com

That will tell you how and where it is trying to look up the DNS, and will show you if it completes normally.

 

[RonanRBR]

Well that just doesn't make any sense now does it? What if you try this from your local machine:

dig +trace sub.domain.com

That will tell you how and where it is trying to look up the DNS, and will show you if it completes normally.

It doesn't really make any sense.

Directly in server

[root@amy: /etc]# dig +trace sec.ronanrbr.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.5 <<>> +trace sec.ronanrbr.com
;; global options: +cmd
;; Received 12 bytes from 10.10.10.10#53(10.10.10.10) in 0 ms

[root@amy: /etc]# ping sec.ronanrbr.com
ping: sec.ronanrbr.com: Name or service not known

My local machine:

[root@RonanRBR: /etc/httpd]# dig +trace sec.ronanrbr.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.5 <<>> +trace sec.ronanrbr.com
;; global options: +cmd
.                       600     IN      NS      i.root-servers.net.
.                       600     IN      NS      a.root-servers.net.
.                       600     IN      NS      d.root-servers.net.
.                       600     IN      NS      c.root-servers.net.
.                       600     IN      NS      b.root-servers.net.
.                       600     IN      NS      j.root-servers.net.
.                       600     IN      NS      k.root-servers.net.
.                       600     IN      NS      g.root-servers.net.
.                       600     IN      NS      m.root-servers.net.
.                       600     IN      NS      f.root-servers.net.
.                       600     IN      NS      e.root-servers.net.
.                       600     IN      NS      h.root-servers.net.
.                       600     IN      NS      l.root-servers.net.
;; Received 811 bytes from 192.168.1.254#53(192.168.1.254) in 57 ms

com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
com.                    86400   IN      DS      30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com.                    86400   IN      RRSIG   DS 8 1 86400 20210908050000 20210826040000 26838 . D6us9++tdr1BJzQMVzcl3F8a81/FQsD0m4Bwc20Lks2QXr3T3pZ6Cuv2 g/b0HGYYT+YhlNEEMHUH/A3HG9oh8cfxamK07iX+6uQkxnI+rOJ0hH6w /04oWQhePfxF5hq9xKbKF7ZUDi7A6HQh8AYaWa7pM+DpGc9TakGunSzK uO3995Cjb0THoGS0jMTNRmYdV1SqGz20y1j4953UlMcTivYSCuDg/gkQ VXNfH2OVKKyEiBdJzxzGvo9OOcCx3fZ1N3JzGhV0D/eCdwpBm+NKMbB+ XJ5mIccepOPq2zYuvByv2PQ6IB683S9Q6h4Xw5DrSQwrb4Ws0zycGHKt GvqMuA==
;; Received 1176 bytes from 199.7.91.13#53(d.root-servers.net) in 78 ms

ronanrbr.com.           172800  IN      NS      ns1.7links.com.br.
ronanrbr.com.           172800  IN      NS      ns2.7links.com.br.
ronanrbr.com.           172800  IN      NS      ns3.7links.com.br.
ronanrbr.com.           172800  IN      NS      ns4.7links.com.br.
ronanrbr.com.           86400   IN      DS      26009 13 4 4C574004C7BE1D9AEE48173E2265D34CB229ECD6B0D8AD9EFE6B2D2F 7AAD4EB4C3A641E47706FC3A19CA0C5BA6FC56AF
ronanrbr.com.           86400   IN      RRSIG   DS 8 2 86400 20210831045106 20210824034106 39343 com. BE7Gw68Vnu6j86N5ezGPVlHrlf2u8b+iYMpVuFMW9IkLsaMZ5I3VUf+X oGiBYLJyWuZwW9TwS7YLqux7b6rtis+6WWkeKtB5SKKmZmemMHxHTgZ8 zgRDaeyKVo8axIHtpwf7x4kG5VkeJ40QJ2uEu9F4zNW3SSGQkSDLWNLu S/r06mwk4pzl0MqGgTxQoWcCg3CK5wHU+JoL7y0m9BHJbw==
;; Received 389 bytes from 2001:503:231d::2:30#53(b.gtld-servers.net) in 173 ms

sec.ronanrbr.com.       14400   IN      A       50.28.33.206
;; Received 61 bytes from 50.28.33.206#53(ns1.7links.com.br) in 115 ms

 

[cPRex]

Just for fun, did you try updating the resolvers to see if that changes the behavior? That's really the only thing that would determine how domains get looked up from the command line.

 

[RonanRBR]

Just for fun, did you try updating the resolvers to see if that changes the behavior? That's really the only thing that would determine how domains get looked up from the command line.

[root@amy: /etc]# cat resolv.conf
; generated by /usr/sbin/dhclient-script
nameserver 10.10.10.10
nameserver 208.67.222.222
nameserver 8.8.8.8

But when I create a subdomain within the main account, it manages to resolve the dns. Furthermore it is the local server.

 

[cPRex]

Okay, and even with the 8.8.8.8 in there, you get the same behavior?

 

[RonanRBR]

Okay, and even with the 8.8.8.8 in there, you get the same behavior?

[root@amy: /etc]# cat resolv.conf
; generated by /usr/sbin/dhclient-script
nameserver 8.8.8.8
nameserver 10.10.10.10
nameserver 208.67.222.222

 

[cPRex]

I'm not sure what else could be causing that behavior from what we've seen up to this point. You're always welcome to submit a ticket to our team so we can take a look and do some testing directly on the machine.