Does anyone know how to force an NTL proxy to update it's cache for a website?
I have just changed a domain which I own (number-seven.net) but I am still getting the registrar's holding page when I try to browse to the site.
number-seven.net works but
www.number-seven.net does not, the A record does exist and works and both addresses trace back to the correct server IP:
Code:
> nslookup number-seven.net
Server: cache2.ntli.net
Address: 194.168.8.100
Non-authorative answer:
Name: number-seven.net
Address: 70.84.159.228
> nslookup www.number-seven.net
Server: cache2.ntli.net
Address: 194.168.8.100
Non-authorative answer:
Name: number-seven.net
Address: 70.84.159.228
I can also get to services not on port 80, so the only explanation I can think of for the thing not working is a crap ntl proxy. I can change the registrar's holding page and see the changes so the proxy is obviously updating it's cache ... just from the wrong server. When I go to
www.number-seven.net in my browser I get this:
Code:
> netstat
...
TCP MyComp:xxx redirect.123-reg.co.uk:http ESTABLISHED
...
Which leads me to think the proxy hasn't bothered to update the dns records for the address, which is pretty stupid since cache2.ntli.net returns the correct IP
Does anyone know of a way of getting the thing to work properly, the last time this happened it took about 2 weeks for it to start working.
SK