Before I tear my hair out.

[cctvfitter]

Sorry if this is in the wrong area.

I have just created a new website for personal use at home .

ISP is virgin media.

The site is published and I can view it from any where in the world , except through my VM.

Changed the dns to google and all is ok , wont work at all with VM’s dns.

The website provider tells me the cache needs to clear on the VM superhub 3 , but it will just have to do its thing and clear in its own time.

Is there any way to force a cache clear?

Any help gratefully received.

Thanks Rob.

[robk]

If you have just created your domain name etc its very likely that you tested the site before the records were there, so your ISP/router have cached the duff info. This is why it works everywhere else. Potentially reboot router/flush dns may help however you will probably find its working fine is 12-24 hours time when the cached records time out.

[cctvfitter]

Cheers , thanks .

[ZeroHour]

This is useful: https://www.whatsmydns.net/

Although its not ISP based it does show what the big upstream DNS servers in countries can see.

[bald_pig]

VM have rubbish DNS servers, they used to fall over constantly when I was with them, you'll just have to wait unfortunately!

[MatthewL]

I've always allowed for 24 hours for DNS replication for domain names in the big wide world, shouldn't be as long but some ISP DNS is shocking.

[cctvfitter]

All sorted now VM has done its stuff , thanks for the advice.

[CAWJames]

Also, bear in mind if your VM internet is on a dynamic address rather than a static once, your website may just stop working when the IP changes, unless you are using a dynamic DNS service of course

[bald_pig]

Also, bear in mind if your VM internet is on a dynamic address rather than a static once, your website may just stop working when the IP changes, unless you are using a dynamic DNS service of course

 

The way I read it, the website isn't hosted on his ISP, it was just a case of the ISPs DNS not obeying the TTL times for the domain OP was using.

[CAWJames]

The way I read it, the website isn't hosted on his ISP, it was just a case of the ISPs DNS not obeying the TTL times for the domain OP was using.

 

Fair enough, does make sense but just in case he is self hosting