...This might be a silly question, but why don't you just upgrade your 1&1 account to a hosting acount?lex007 said:cheers guys:
Atlanta1.....! I need it for a year? I have the page made/the domain name/need to host it.
It's with 1&1? Can you sort this & how much moola?
Well that's not going to be much good for lex007 if he wants the site live by tonight - before the DNS change has time to propegate. You should be telling him to do that - AND - set up a redirect from where the domain is currently pointing. If he can't do that (if he's currently got the name servers set to sedo for example) then he can't have his site online by this evening and you should be open with him about that.netserve said:Set the name servers to ns1.nsnoc.com and ns2.nsnoc.com and drop a mail with the domain to support at nsnoc.com with your
netserve said:Set the name servers to ns1.nsnoc.com and ns2.nsnoc.com and drop a mail with the domain to support at nsnoc.com with your account number (get it from www.domaincity.co.uk/signup.php3) I'll get it ready and send ftp details to you.
12 months hosting free of charge because I'm in a good mood today![]()
mishmash said:Well that's not going to be much good for lex007 if he wants the site live by tonight - before the DNS change has time to propegate. You should be telling him to do that - AND - set up a redirect from where the domain is currently pointing. If he can't do that (if he's currently got the name servers set to sedo for example) then he can't have his site online by this evening and you should be open with him about that.
Following a change I've generally seen that traffic (web and email) tails off from the old server pretty quickly but doesn't drop to nothing for a couple of days. I wouldn't rely on a change having taken place until 2 days had elapsed. I certainly wouldn't call up a client on another continent and expect them to be able to see the new site within a couple of hours.BTFUK said:Whats the longest that you've had a nameserver change take? I know the golden rule is allow 24 - 48 hours, but i've never had one take much longer than 2 hours tops.
There's a whole range of places where there could be a cache, from the users own computer to their ISP's DNS servers. Generally I think the slowest/most problematic one is the propagation of the DNS change to ISP's DNS servers.Jeewhizz said:THe issue isn't a NS change, its the user's system. My bb modem caches the DNS until midnight... So if i visit a site now, and the NS changes in 5 mins, I don't get the new server until tomorrow.
Some ISP's also cache. NTL is one of them.
aquanuke said:My ISP dosent cache,
We use essential cookies to make this site work, and optional cookies to enhance your experience.