Subdomain takes 20 minutes to respond to PING

A

attDA

Verified User
Joined
Mar 17, 2010
Messages
6
Hi,
I have an urgent issue.
I'm using DirectAdmin & WHMCS to make automatic installation of a software that I'm developing.

The idea is to provide a free subdomain for my users so they can start working immediately. However, when I setup everything, the subdomain takes 20 minutes before it starts responding to ping, and to HTTP requests.


Therefore I have two questions:
1. Why is this happening?
2. How can I make it update immediately?

I'm running the installation from a PHP script using root privileges.
Thanks,
Avi.
 
What happens if you try the ping before the 20 minutes is up?

The common reason for this delay would be that the DNS isn't set up properly and is taking 20 minutes to set up.

Are you using wildcard DNS?

Immediately after setting up the domain you should try from a Linux/FreeBSD command line:
Code: 
$ dig sub.example.com +trace
and follow what you get.

Jeff
 
No clue what's hapenning

Jeff,
Did what you advised, and for the time being it seems to work.
Yet the scenario happens from time to time, I cannot replicate it.

Some subdomains are added to DirectAdmin, and begin being available only 15-20 minutes afterwards. How can I approach this problem?
What should I do? How do I configure the system/server so it resolves the new subdomains?

Alternatively, is there a command that refreshes the DNS tables on the server?


Regards,
Avi.
 
Well,

know the domain name should be helpfull for check your dns settings.

Otherwise, the dns propagation change from nameserver to nameserver so should happen that you see the new A record in few secs and another guy siwth different nameserver take 20mins...

If the problem is in the server (like create a subdomain and ping itself from the server) so maybe you got some problem in dns and you should check your namserver aswell in /etc/resolv.conf
 
Server configuration

Hi,
Thanks, I will check the configuration file for more information.

I just want to clarify that the DNS is a private one, which operates from the server itself. It does not depend on an external DNS to resolve domain names. Therefore I suspect the problem to be within the configuration of either DirectAdmin or the server itself.


Any other thoughts?
Cheers,
Avi.
 
Hi,
That was prompt :)

The problem is not with the domain of the server, rather the time it takes to resolve a new subdomain (or a domain that was already pointed to the DNS).
I made a test right now and it resolved almost immediately.

However, last night I had to wait ~12 minutes before a new subdomain could be resolved. Since I'm developing a web application that depends on subdomains availability (the application is installed immediately after a new user is created within DirectAdmin), this situation is a big problem for me.


Just for reference, I checked the domain with intodns.com, everything turned out just fine.

Avi.
 
sorry but maybe im not understanding well...

Everytime you add a subdomain he will add an A record to your DNS, so, for resolve that A record is normal that have to pass some mins.

Now, the thing i dont understand is.. if the server dont resolve itself (like in ssh you into server cant resolve a ping to subdomain.domain.tld) or if you cant resolve the subdomain from another computer...
 
Thank you for helping.

I'm having a problem to resolve the domain from another computer. The DNS is a private one, therefore the server itself handles the resolving of domain names.
All I need is to refresh the dns cache/tables immediately after a subdomain is created so it can be resolved immediately after it is created.

There are numerous services on the Internet under which you open subdomain, and it becomes available immediately.


Cheers,
Avi.
 
Im not so expert on dns so, ive made some search in the forum and ive read that the refresh depend from SOA record that is default set to 14400 that if im not wrong are 4 hours, so, you should make some test and try to decrease that value to like 1200 that should be 20mins...

Atm ive no more ideas, maybe tillo should give you so many more info, he is sure more expert then me on this :)
 
Oh, just a clarification, that modification can be done via ssh on the db file in /etc/bind/domain.tld.db (at least this is the path on debian, on other system maybe you got named instead of bind).

Regards
 
You must log in or register to reply here.
Back
Top