Second share IP will not resolve?

[totaltouch]

Hi there,

I would like to ask you guys for some little support, because I can't find the answer.

At the moment I have two DA boxes. The domains DNS are external at a registar, I want to change this so DNS can be managed from DA.

Host 1 (datacenter 1, VPS):
minnie.anytime-anyplace.net
ns1.anytime-anyplace.net
79.170.94.90

Host 2 (datacenter 2, dedicated):
mickey.anytime-anyplace.net
ns2.anytime-anyplace.net
85.17.87.149

I pointed the A records for the nameservers at my registar, and even have the possibility to change the domain DNS to ns1 and ns2. Current testdomain: http://www.joomlagg.nl

Now I want to use different IPs for that domains. So, I added in IP management 85.17.87.179. I shared the IP and want to give it to the user. So far, so good. Then as soon as I change to the newly created IP, it is impossible to reach that domain.

What I checked:
- A records at my registar point to ips of hostmachines
- IP nr is added to DA and assigned to the reseller and user
- dig reverse dns works (as far as I can see)
- ping to domain works (give 85.17.87.179)

 

[floyd]

- ping to domain works (give 85.17.87.179)

dig joomlagg.nl returns 85.17.87.179
ping 85.17.87.179 does not work.

traceroute:

[root@server public_html]# traceroute 85.17.87.179
traceroute to 85.17.87.179 (85.17.87.179), 30 hops max, 40 byte packets
 1  * 12.238.72.242 (12.238.72.242)  1.630 ms  1.611 ms
 2  newwebsite.com (12.191.44.254)  8.246 ms  11.582 ms  12.485 ms
 3  12.89.29.157 (12.89.29.157)  21.120 ms  21.277 ms  21.365 ms
 4  cr1.wswdc.ip.att.net (12.122.135.170)  22.306 ms  23.739 ms  23.907 ms
 5  12.122.135.97 (12.122.135.97)  21.428 ms  21.862 ms *
 6  192.205.33.34 (192.205.33.34)  29.964 ms  28.629 ms  28.611 ms
 7  64.213.76.150 (64.213.76.150)  105.696 ms  129.717 ms  128.836 ms
 8  po100.sr1.evo.leaseweb.net (85.17.100.226)  131.190 ms  131.089 ms  130.970 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

 

[totaltouch]

Leaseweb is indeed the datacenter that I am hosting my dedicated server in. They also provided me with that new assigned IP address.

Any clue on how to resolve this problem? Where to start?

Thanx!

 

[floyd]

Leaseweb is indeed the datacenter that I am hosting my dedicated server in. They also provided me with that new assigned IP address.

Any clue on how to resolve this problem? Where to start?

Thanx!

Start with Leaseweb since they are not routing the ip to your server.

 

[Michael.Terence]

Likely the ARP cache at their router... when the cache clears it'll come up. If it is the ARP cache, you can ask them to clear it and it'll come up in a matter of minutes.

 

[floyd]

Likely the ARP cache at their router... when the cache clears it'll come up. If it is the ARP cache, you can ask them to clear it and it'll come up in a matter of minutes.

But that would only be true if the ip was recently used on another machine. If the ip is a "fresh" then there would be no ARP entry for it. But it very well could be the case. I have switched an ip from another machine before and forgot to clear the ARP cache.

 

[totaltouch]

Problem at datacenter

Hi guys,

You were right... The problem existed at the datacenter.
Reason they gave me: "Probably" someone else was using the IP or had been using the IP.

Well after all, they gave me a "fresh" IP.