Can you test propagation for me?

[solomon]

Hi

Can you check this link and tell me what you see please?
www.firenzafloraldesign.co.uk (http://www.firenzafloraldesign.co.uk)

We've just secured a new client who is not happy with her current choice of web company so we've transfered her domain over to our domain name hosts (ipstag FIBRANET) and changed the DNS to point to our nameservers (ns and ns2.webattention.net).

I started the domain transfer and changed the DNS record on Tuesday (should I have waited until the transfer was complete before changing the DNS record?). The domain only finished transfering about 36 hours about but the DNS still hasn't propagated for us from where we're sitting and it really should have done! It could just be our ISP not refreshing their information yet but they're usually faster than this.

Can you check out the site and tell me what you see please? If you all see the *ahem* not so pretty blue holding page then something's going wrong - if you all see the pretty pink holding page then that's good news.

Thanks for taking this moment to help - if there's a problem I need to get onto it ASAP! - cheers.

[Kevey]

I see the pink page.

[solomon]

phew! thanks!

anyone else?

[TheBearMay]

Screenshot attached...

[solomon]

Excellent work TheBearMay, thanks. It's beginning to look like the problem is with our ISP because we're still getting her old hosts holding page.

If anyone is seeing the blue page I'd be interested to know :) cheers!

[pcthug]

Nope, I get pink too

[Kevey]

Try viewing your customer's site through a proxy such as http://www.w3privacy.com/

Here's your site: http://www.w3privacy.com/w3proxy2.php?url=http%3A%2F%2Fwww.firenzafloraldesign.co.uk&SUBMIT=Browse+Anonymously+

At least you'll sleep better knowing it's working!

Also, when I moved my site awhile ago I found that my cache was causing problems. When I deleted the cache everything worked as desired. It shouldn't take too long to propagate through the Internet.

[solomon]

Cheers guys.

Kevey, I tried the site you mentioned but sadly I'm getting a 404 :(

Anyway - it's late here in the UK and I'm off to bed to sleep better knowing it's working ;) (still doesn't explain why I can't see it!)

[pcthug]

Through a Google Proxy: http://translate.google.com/translate?u=http://www.firenzafloraldesign.co.uk/&langpair=en%7Cen&hl=en

[solomon]

ok - I haven't gone to bed yet ;)

I get the old blue holding page through that proxy! Is this understandable?

I'm usually more of a codemonkey than a server/network guy and sadly I just do not understand this side of things :( I know what to do to get things working but when things don't behave as I expect I'm at a loss!

Thanks for your help again.

[bathurst_guy]

Could be your ISP - as I'm guessing you have cleared your cache (Y)

[solomon]

one of the first things I did ;)

...but I'm getting the same results from 2 different PCs on the same side of our router

[Kevey]

That's really weird. Try a different browser (excuse to download opera or firefox) or try control-f5 in your current browser to reload the page instead of refresh. Really confusing that you see the blue page through a proxy...the proxy should bypass your ISP, not reach back to it for cache. Strange indeed!

[solomon]

Thanks for your suggestions Kevey, but I'm a web developer - I already use Firefox by default (and I've checked in IE) and I hard refresh pretty much everytime as a matter of habit! ;)

I check again this morning and it still hasn't propagated! Could it be something with our router?

[TheBearMay]

Doubt the router. Do you use a proxy server? If so, may need to flush its cache.

[solomon]

Well - after hours of hunting and searching, I think I've figured out the source of the problem - it's my ISP - they've obviously got a caching problem on a particular server.

Just to blow the whistle a little - my ISP is NTL.

Despite the fact I called NTL's so-called 'technical support' (who, in fairness, tried all sorts of solutions - even giving me IPs of their different proxy servers) they could not help me resolve the issue. I called my mate (who happens to design networks for another well known ISP) who gave me a list of NTLs other proxy server IPs to use (one's that MTL's own tech support guy obviously didn't know about) and I got through to the new server with my first attempt! :)

This (in my feeble mind) doesn't explain why I still saw the old holding page through the google proxy recommended by pcthug.

All I need to do is sit and wait until NTL get their finger out of their @r5e and refresh their stinking cache! :)

Thanks for all your help guys - you've been great!

[jamestmfbong]

Go to check out this ESSENTIAL link www.checkdns.net for server administrators.