At work, we have about 30 or so with Register.com. Only two of them are on their “primary” servers which means if I make a change they are supposed to update the server within 15 minutes. These have 1 hour TTL time. The rest are on their “Free” servers which can in theory take up to 47 hours to update (both update once every 24hours 12 hours appart).
The only reason why the corp is with them is due to some of the other country support. Otherwise, I would move them all over to Godaddy.
At $43 per year for the privledge of Register.com… I’d stick to Godaddy.
A 1 hour TTL will be increasing the DNS traffic quite considerably. I tend to set 24 hour TTLs on the grounds that DNS changes are rarely needed and usually planned well in advance, so you can reduce the TTL a few days before the change (to 15 minutes last time I did it) to get a quick change once the server IP is changed and then change it back to 24 hours once you’re sure the change doesn’t need to be undone.
No hassle domain name (takes mere minutes to setup!)
Can register domain name with search engines
Previous visitors notice nothing… all links still function as before
Disadvantages:
Creates another layer which needs to be working for site visits (i.e. godaddy.com goes bye bye and no visitors through domain name even though site is up and working)
Masking masks refer stats (I can no longer tell where people are coming from)
Unable to bookmark individual pages
Possible page rendering glitches with Firefox (looking into work arounds for those)**
** Got that working again… had to change some of my Javascript to be WC3 compliant
Even if they do provide the same type of service, bocking another Registrar would be a violation of ICANN rules. One registar cannot block access to another. It would be foolish for a Registrar to do that.
My guess is that it is network routing related. There have been a lot of overseas networking issues the past couple weeks.
once Ambient thought i had insitaged a DOS attack (yeah right, with a dail up 28k connection?)
and they blocked my IP address…but it was only assigned from my ISP, and so all users of the ISP I was using could not get to their web site.
That’s a common problem. A server in the hosting facility and in the same Class C sub-net as my server got hacked and was being used as a spamming agent. At least one of the big spam blacklisters blocked the complete Class C net which caused me some problems!
I transferred one from Register to godaddy. Took from Saturday afternoon to Monday afternoon. Very smooth, just had to ignore godaddy’s hundreds (it seemed) of offers for additional cost services and register’s tearful entreaty not to transfer, warnings of dire consequencies if I did, and a 30% off renewal offer. Godaddy added a year to the expiration date, hooked it up to the previous DNS addresses and if there was any interruption of service it was very small.
Yep… I would like it much if they toned that down. I wonder how many plunk down more money for that “stuff”.
One other thing… as your domain come up for renewal… you will start getting 90 day, 60 day, 30 day, 15 day… email notices that you need to renew soon… I have them ALL filtered to a mailbox where I dump them since I let the autorenew take place when they expire.
I used to pay off all of the renewals for the month at the first of the month, but I’ve since just let them renew automatically when they expire. A lot less headaches. The renewal is alway for 1 year and at a whopping 8.99 for com and net … its no big deal. sometimes you catch them with a promotion to make it even cheaper.
If only I could convince my primary job employer to swtich over from register.com, my life would be much easier. sometimes I wonder if they actually know what DNS is … I’ve got some real horror stories about them.
The only niggle I have with e-rice is that he has about a 5 second delay built into the ftp login process (at least on “my” server). In reality it hasn’t caused any problems, it’s just not what I have been used to. Otherwise it’s just great.