new subdomains not resolving and letsencrypt 400

[johnking]

I'm on Centos:

CentOS Linux release 7.9.2009

I moved from a Centos 6 Box, everything moved fine, including subdomains, everything works as it should. However when creating new subdomains they do not resolve correctly nor will letsencrypt cooperate (400 or 429 codes returned).

The newly created subdomains either resolve to other subdomains (https) or resolve correctly but serve content from another subdomains directory (http).

https://test.example.com --> https://older.example.com

http://test.example.com --> http://test.example.com but serves files out of another subdomains directory

I did create A records and CNAME records for newly created subdomains.

A new public_html directory is created for the created subdomain as are httpd and nginx conf files.

[grayfolk]

I'm on Centos:

CentOS Linux release 7.9.2009

I moved from a Centos 6 Box, everything moved fine, including subdomains, everything works as it should. However when creating new subdomains they do not resolve correctly nor will letsencrypt cooperate (400 or 429 codes returned).

The newly created subdomains either resolve to other subdomains (https) or resolve correctly but serve content from another subdomains directory (http).

https://test.example.com --> https://older.example.com

http://test.example.com --> http://test.example.com but serves files out of another subdomains directory

I did create A records and CNAME records for newly created subdomains.

A new public_html directory is created for the created subdomain as are httpd and nginx conf files.

Did you create also A or CNAME records for aliases?

[johnking]

Did you create also A or CNAME records for aliases?

Yes, in DNS panel

I can't create an alias under the domain as it is already existing domain.

Error: Web domain
test.example.com exist

DNS is working fine but the subdomain is being served from the wrong directory.