Default html page is not displayed for users that are on a different IP

Status
Not open for further replies.
A

acdomains

Verified User
Joined
May 2, 2007
Messages
14
Hi,

I've recently set up the DirectAdmin on a Fedora5. Everything seems to be working pretty good. :) But I've discovered an issue with default html page for new users that are assigned to the IP address that is different from the server one.
Instead of the default page "Welcome to the home of ..." I see the page with the following text at the top: "Hey, it worked ! The SSL/TLS-aware Apache webserver was successfully installed on this website."

Would you please suggest a solution for this issue?

Best regards,
Alexander
 
It's strange to receive such a strange answer for a certain question...

Let me give some more details on the issue. My server (that is running the Direct Admin) has multiple (10) IP addresses assigned. All of them are added through the [IP Management] menu in Direct Admin. One of the IPs (the one that is in the DA license) has a stutus 'server'. The problem occurs when one of the users gets assigned to the IP address that differs from the one with 'server' status - in this case the default html page is not as expected.

Thanks.
 
Did you just change the IP recently? If so, it still needs time to propogate from the DNS. The httpd server is now listening on the NEW IP:80 but the DNS is pointing you to the OLD IP:80 which no longer exists and pulls that page up. Give it about 4-24 hours for your ISP to update their DNS cache and it should start pulling up again. One way to fix this is go to the users httpd.conf in /usr/local/directadmin/data/users/username/ and copy-paste the new IPs virtual host and change the IP to the old ip so it is listening on both IPs and restart httpd then try again.
 
acdomains said:
It's strange to receive such a strange answer for a certain question...
Click to expand...
Actually it's not, and though I don't know where floyd got the idea to point you to that page, I've been pointing people to it for years.

Simply, if you don't let us have something real to search, we can't do any debugging. More often than not the problem is because of stale DNS cached in your own system or on your own network, or on your ISPs network, as all DNS includes TTL (time to live) settings before any nameserver goes back to check the source.

If you'd given us a domain name to test you would have gotten the answer, perhaps within minutes. And if you'd searched the forum you might have found a lot of other places where the same question was asked, and that answer was almost always that the poster had stale DNS.

This is a very active community, and we really do all want to help each other, but please make it easy on us.

Thanks.

Jeff
 
Thanks for you reply,

the problem appeared to be in our local DNS server located on the gateway of our LAN - it is updating really slow.

thanks again.
 
Status
Not open for further replies.
Back
Top