Quote:
Originally Posted by Cassie
I don't know how and I don't know why, but this seems to have resolved itself. It doesn't seem to be anything that tech sup did here or on anywhere else. Perhaps it was just a case of waiting for the dns to resolve on my isp's server but I don't really see why or how that happens.
Whatever - it is sorted.
I am just a little disappointed once again in some of the responses I have had from tech sup etc. - this includes (non) responses from 123-REG & NTL as well as here. It just seems that whenever I try and move sites or domains to you here that there is always a problem which takes countless emails and lots of time and hair pulling to resolve. I guess we are back to the same subject as many of the threads on this forum - difficulty in understanding each other.
|
next time when you point a domain to our servers then make sure you open a ticket in our support department and request someone to take care of propagation of your domain. If you get a reply from them saying the domain has propagated then you should verify same from
megaproxy.com and reply accordingly. Most of the times domains dont propagate on our local systems as we keep on refreshing our website expecting it to resolve from new server while the old DNS cache keeps on refreshing. Your domain starts resolving from new server for everyone else but not for you as the cache never gets sufficient time to clear out.
When I change DNS for any of the websites then I force DNS refresh using following command on command prompt of my desktop :-
ipconfig /flushdns
fire this command couple of times and your DNS cache will clear immediately.