Temporary domains not provisioning instantly like they used to

R

RADRaze2KX

Verified User
Joined
Jan 4, 2024
Messages
34
I'm not sure where else to put this. Basically, when I created an account in WHMCS and provisioned service and it sent it to our directadmin server, it used to be accessible instantly. Now it seems to take 5-10 minutes. I'm not sure if this is because I changed our Name Servers on enom to point to the nameservers on our server instead of their nameservers (dns1-5.name-services.com), or if it's because of something else. Does anyone have an idea of where to start troubleshooting this odd issue?

Temporary domain example:
JohnDoe.ourwebhost.com

WordPress files are there, but the dns doesn't seem to have resolved in our hosting server yet for some reason.

Setup is:
CloudLinux 8.9 + CageFS
DirectAdmin
Imunify360
KernelCare+

Domain registrar is enom
 
Might have to do with the crons (?) these get pushed every 5 minutes with the correct setup, maybe put it on 1 minute?
 
Yep, domain creation and all that was successful from WHMCS -> DirectAdmin. I can see Softaculous deployed the data as expected. It's just when I try to access it, it doesn't show up.
 
It seems to work after rebooting the server, but... that's definitely not the way to go :( I checked the logs and the only thing I can see that might be wrong is that the SSL cert is not issuing.
 
Could you be so kind as to tell me, under the DirectAdmin Control Panel > Admin > Server Manager > Server Settings (tab on the page), under "NS1" and "NS2", should that be set to the server's nameservers (ns1.myserver.com) or should it be set to the domain registrar's (enom, in this case)?

In each website, the NS records are set to ns1.myserver.com and ns2.myserver.com ... something doesn't seem right about that. Shouldn't one of these be set to enom? Enom is also set to ns1.myserver.com ... maybe that's where the delay is?
 
I just noticed when trying to transfer a site to the server, it failed to get past verifying the FTP info, until I cancelled it and put in the server IP as a fallback. This definitely seems like a nameserver resolution issue but I'm not sure what the proper configuration is.
 
Well, do you use your own nameservers or do you use ENOMS ?

If you use your own, do you have one server or two?

And if it shows up in Directadmin, normally Directadmin did it's thing, its up to the rest to work.
Check if the ip is correct for the new domain with for example : https://dnschecker.org/
 
Our own. One, with one IP currently. I'm still in the testing phase. I'll add a second IP to the system once I have all the bugs ironed out. I found the General DNS guide and it seems everything is set up correctly. The only other thing I can think of is... at one point the hostname/domain was set to servername.myserver.com, and I changed it to myserver.com ... Since then, I've had issues getting SSL to work for the hostname.

I had forgotten that I set it up with servername.myserver.com specifically with the intention of having servername2.myserver.com and servername3, etc for all future servers. Now I can't seem to change the domain back to servername.myserver.com ... I think I screwed up big :(
 
The hostname should always be something like:

hostname.domain.com (or something else like this.domain.com)
Not
Domain.com

And nameservers should be like:

ns1.domain.com
ns2.domain.com
 
Oh and if you want a second DNS you can take a look at :

DirectSlave/GO 3 - public beta

Original DirectSlave thread: http://forum.directadmin.com/showthread.php?t=43924 ================================================================================== UPDATE: DirectSlave Updated to version 3.4.2-Advanced! → BUGFIX: pid file was not written when running under Linux systemd...
forum.directadmin.com forum.directadmin.com
the software is free, but you will need a second server.
 
If you give us the domain we can help you more instead of guessing.
 
@ericosman I owe you two beers now, I think that's the second time you've helped me solve an issue here. Thanks!

So the issue was the Server Hostname had been renamed to just "domainname.com" and I changed the default domain to "servername.domain.com"

It was backwards. To fix this, I had to delete the default domain, then rename the server hostname to "servername.domain.com"

Then, when I tried to re-add the default domain to the admin user, it kept saying it already existed. I checked everywhere:
  • /etc/virtual/domains
  • /etc/virtual/domainowners
  • /etc/virtual/domain.com
  • any /var/named/*.nzf file if rndc is used for adding/removing zones
Well, not everywhere, I thought "domain.com" was a directory, but it's not. It's literally "/etc/virtual/name-of-the-domain.com" ... Once I realized that, I was able to delete it from the directory, then I could re-add it to the admin user's domain. I probably would've caught this but the first thread I found didn't have "domain.com" emphasized as anything, so I thought it was a directory. *sigh*

Fired up a test user and it propagated right away. I also think that solved the myriad of SSL issues I've been experiencing as well since I flip-flopped them the first time. Thanks again, guys!
 
The issue is back unfortunately. I think it has to do with our primary SSL not working. I also may have deleted something in our DNS that I shouldn't have. Should the hostname of the server be set as an A record of a CNAME in the Default Domain's DNS records?
 
*sigh* fixed. Had to add the hostname to the DNS's. serverhostname.mydomain.com ... I thought I did that yesterday but I didn't. The issue is most likely stemming from the SSL certs being issued to the server hostname rather than the domain name. I'm not sure if it should be that way or not. @ericosman, any wisdom you can provide?
 
RADRaze2KX said:
a CNAME in the Default Domain's DNS records?
Click to expand...
Never use a CNAME for a hostname. Best is too use cnames as little as possible.

You might want to create a certificate for your hostname if you did not already. Certificates for your domain name are generated seperately.

What exactly is still going wrong at the moment?
 
You must log in or register to reply here.
Back
Top