Changing Registrar and Primary/Secondary DNS NameServers. Need your input(s)!
Posted : January 1, 2005 at 1:11 pm [America/Los_Angeles]
I just finished initiating a transfer of my indrayam.com domain from it’s current Registrar (EasyDNS) to GoDaddy. I also plan on switching to ZoneEdit nameservers in place of EasyDNS, thanks to Brian McCallister’s comment on one of my older blog entry.
So why am I doing this? Why do I care? Is EasyDNS NOT a good company to do business with? Quite the contrary. It’s an excellent company that has served me very, very well. I would recommend EasyDNS to anyone who is just starting off and would prefer not to deal with the hassle of seperate Registrar and Primary/Secondary DNS providers. It offers it all in one place and their service is exceptional. The only problem is it’s a tad too rich for my pocket ($35 per year per domain). Since I manage and sponsor almost 7 domains for my family and friends, it creates quite a gaping hole in my pocket at the end of the year 
I would like to complete this transfer with “minimum” downtime for my readers. However, there might be some, especially when I switch my Primary and Secondary DNS Nameserver information after the domain has been transferred to GoDaddy.
If you have done this exercise before and can suggest a few hacks as to how I can eliminate downtime for my end users, feel free to chime in.
- Anand
Category: Services and Software
2 Comments
I looked into ZoneEdit not too long ago, I was going to go with them myself but, I seen that if you go over 200MB of transfer/year it will count as 2 domains. I checked my stats on my website and I’m not sure how to figure out how much bandwidth I’ve used. I looked at Awstats and Webalizer and if im correct and the numbers are correct, I am going over 200MB/year. In the whole year of 2004 I seem to have used 207.42MB.
This isn’t a problem with me. I’m not trying to get out of paying anything, but what bothered me was this excerpt on their FAQ page:
QUOTE:”For example if a single domain goes over 200 MB of transfer during a year, then it counts as TWO domains, if it goes over 400MB, then it counts as three, etc. Usually DNS hits are cached, so even the busiest sites won’t go over the 200 MB limit.“
From putting 2 and 2 together, This excerpt from their FAQ doesn’t sound too truthful unless I’m wrong.
Posted by: David M. at January 2, 2005 @ 8:19 am
David:
It may be that you’re confusing bandwidth used by your site (as partially shown by AWStats or Webalizer) and the ZoneEdit’s bandwidth that will be used by clients requesting DNS information about your host. Needless to say, the two are different.
From ZoneEdit’s FAQ (also quoted by you):
Usually DNS hits are cached, so even the busiest sites won’t go over the 200 MB limit. 200 MB should get you about 1,000,000 DNS queries. A typical site uses 5 MB per year of DNS bandwidth.
That’s just how DNS works and I agree with what ZoneEdit claims here.
I guess what I am trying to say is that I am not sure how you’re measuring the bandwidth consumed by your domain hosted at ZoneEdit, but it surely should not be done using AWStats/Webalizer reports.
HTH
- Anand
p.s.
I am just testing ZoneEdit out right now. If it starts costing me, I may decide on using the DNS services of my ISP (ServerMatrix)
Posted by: Anand Sharma at January 2, 2005 @ 12:09 pm