Blue Plesk Screen After Migration

[tungsten]

Hey all,

We are running into an issue with Plesk MM. We are moving 65 sites (a chunk at time each night) down to a new box. For the most part the domains are rolling out perfectly.

However we have 3 domains out of the last 40 that are refusing to roll properly. After almost 30 hours their DNS routes find out new server but we are still seeing the Plesk default page (the blue one). What is even odder is that the traceroute to the domains is ending at the NS.domain.com server IP and not getting the last hop to the actual IP on the box that holds the domain.

Here is an example:

http://www.patrickkeenan.net/ was migrated over 24 hours ago without errors.

named.conf is showing correct information:

zone "patrickkeenan.net" {
type master;
file "patrickkeenan.net";
allow-transfer {
75.126.162.93;
common-allow-transfer;
};
};

However the traceroute when running from here is stopping at:

traceroute to patrickkeenan.net (75.126.204.98), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 1.326 ms 1.037 ms 1.145 ms
2 24.79.64.1 (24.79.64.1) 19.626 ms 14.244 ms 9.208 ms
3 rc1sc-ge2-0-0-3.wp.shawcable.net (64.59.181.194) 10.623 ms 9.765 ms 13.773 ms
4 rc2nr-ge12-0-0.wp.shawcable.net (66.163.73.169) 15.459 ms 13.820 ms 15.444 ms
5 rc2ch-pos5-0.il.shawcable.net (66.163.76.26) 44.510 ms 45.100 ms 32.562 ms
6 te-7-2.car1.Chicago1.Level3.net (4.79.208.149) 78.629 ms 65.353 ms 61.014 ms
7 ae-32-54.ebr2.Chicago1.Level3.net (4.68.101.126) 73.131 ms 84.354 ms 88.586 ms
8 ae-78.ebr3.Chicago1.Level3.net (4.69.134.62) 74.662 ms 81.772 ms 72.924 ms
9 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 64.180 ms 61.936 ms 72.317 ms
10 ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) 69.877 ms 82.020 ms 74.753 ms
11 ae-2.ebr2.Dallas1.Level3.net (4.69.132.106) 86.236 ms 84.531 ms 90.203 ms
12 ae-72-72.csw2.Dallas1.Level3.net (4.69.136.142) 90.117 ms ae-92-92.csw4.Dallas1.Level3.net (4.69.136.150) 86.985 ms ae-62-62.csw1.Dallas1.Level3.net (4.69.136.138) 79.818 ms
13 ae-2-79.edge3.Dallas1.Level3.net (4.68.19.72) 81.845 ms ae-4-99.edge3.Dallas1.Level3.net (4.68.19.200) 90.892 ms ae-1-69.edge3.Dallas1.Level3.net (4.68.19.8) 78.811 ms
14 te7-2.cer01.dal01.dallas-border.com (4.71.198.18) 88.665 ms 97.501 ms 91.001 ms
15 po1.dar02.dal01.dallas-datacenter.com (66.228.118.203) 88.907 ms 92.575 ms 93.510 ms
16 po54.fcr02.dal01.dallas-datacenter.com (66.228.118.174) 112.685 ms 106.703 ms 90.440 ms
17 visuallizard2.net (75.126.204.98) 92.235 ms 94.557 ms 94.868 ms

Since migration we have:
We have restored the default DNS records for that domain.
We have restarted BIND about 10x.
Apache has been restarted about 20x.
Rebooted the box.

Is there anything else we can do to push this through? Is there another spot I should be looking for a clue in Plesk or CENTOS 4.5?

Any help would be awesome.

 

[tungsten]

For anyone else that might be encountering this issue, it was a propagation issue. It seems our local Cable provider has some LONG refresh times.

When we checked the site through a proxy server, everything was fine.