"This IP is being shared among many domains." on some computers

F

Frizzy

Verified User
Joined
Mar 22, 2014
Messages
8
Hello guys,

This week I moved my website to a new VPS with a new IP address and changed the DNS settings. This was done Monday (about 5 days ago). The problem is that some people still cannot visit the website. Those people call me, and I cannot checkout their PC for what is wrong, but they get the following error:
"This IP is being shared among many domains."

I googled it a bit and it looks like a DNS cache issue, but I guess after 5 days the DNS cache on their computers would have been refreshed? Or am I wrong?

Can you please look at the DNS settings, and maybe advise me what is wrong? This is quite a well-visited website and I don't like the fact that it is unreachable for some customers.

The website just moved is: www.fruitbomen.net

Thanks!
 
Schermafbeelding 2014-03-22 om 18.20.30.png
These are my DNS settings. Could you have a look what is wrong about them?
 
Well.. it obviously didn't because it made my website unreachable (even for me...)
 
I added NS records to my DNS.
Intodns says I'm fine, but my mac still cannot find the host:
HTML: 
host -t ns fruitbomen.net
fruitbomen.net has no NS record
 
I think I found and fixed the problem. The problem was that ipv6 was not correctly added to the domain in directadmin.
 
I reconfigured the domain to use ipv6 and tested it with a ipv6 proxy (which first gave the errorcode in the OP, but now displays the website correctly). One of my customers on the other hand still complains that he gets the same error message. Could this be some kind of cache (which solves itself) or do any of you guys have another idea what the problem could be?
 
Have your customer with the error make sure he doesn't have a listing for the domain in his local machine hosts file. In Linux, BSD and Mac OS servers it can be found at /etc/hosts. I'm not sure where it can be found on a Windows desktop/laptop this (windowsreference.com) may help you find it.

Jeff
 
Andrea, is that where it is in all versions of Windows? If so I'll put it into my notes for use in future replies.

Thanks.

Jeff
 
Yes, everytime is there, unless windows is installed in a non-standard path, in that case just the C:\Windows will be the different part :)

Regards
 
Normally people don't use that hosts file to point to domains, when it's used in the Netherlands, it's mostly to block certain malicious sites.

It can also be a cache issue. Let the customer clear all cache.
In windows:
ipconfig /flusdns
This should be done in a command prompt started as administrator (windows vista/7/8).

Also flush all browser caches.

The fastest way for windows machines is restart the modem or modem/router and restart your pc.
You can let your customer check with nslookup if it's pointing to the correct ip address afterwards.
 
Richard G said:
Normally people don't use that hosts file to point to domains, when it's used in the Netherlands, it's mostly to block certain malicious sites.
Click to expand...
But sometimes site owners (or others, prompted by site owners) use it to look at sites before they go live, and then forget to remove it.

Jeff
 
I don't see the benefit. When the site isn't live, you won't see it on a DA server anyway, not even with a hostfile because that only points to the ip.
So this only works if it's locally hosted or directly reachable via ip address. Correct?
 
Once you create the domain in DA Server it will create the virtualhost, no matter if domain has been registered or not.

Once DA Server is ready to host the domain, change the hosts file will permit you to access that domain on that server before domain get registered or dns propagated.

Regards
 
Richard G said:
I don't see the benefit. When the site isn't live, you won't see it on a DA server anyway, not even with a hostfile because that only points to the ip.
So this only works if it's locally hosted or directly reachable via ip address. Correct?
Click to expand...
To explain in more detail: A host file does exactly what DNS does, it directs packets to a specific IP# when you type a given URL into your browser. Once the packets get to the server, if the account is set up in DirectAdmin, the packets match up with your settings in the user-level httpd.conf file and the user sees the site.

We use host files itensively in testing and it's invaluable for sites such as Wordpress sites, which only work with the 'real' domain name as set up in Wordpress.

Jeff
 
if the account is set up in DirectAdmin,
Click to expand...
So then the website is already active. So if I understand correctly it's just for the time between creating the account and it being resolved through all DNS servers?
Maybe that's why most of us don't need it over here. It only takes about 2 hours to get trough dns, max 4 hours.
 
You must log in or register to reply here.
Back
Top