Hello,

I'm thinking of registring some domain names and change nameservers of my existing ones.
What you think of mydomain.com as domain registrar and dns services?

Thank you,
Johnny

I have used mydomain.com for DNS service, and they are providing one of the best free DNS services. They have been around for years and proved to be serious.

The servers are stabile and a decent interface is provided. Updates are slow so when you update a domain record should you wait a day or two before the changes are working.

JohnnyMartins,

You can use search option to find the feedback about them:

http://www.webhostingtalk.com/search.php?s=

I think you can use the dns service of mydomain.com.

Mydomain.com does not appear to be helpful in fixing problems.
If something goes wrong, you will be stuck!

See
http://www.webhostingtalk.com/showthread.php?t=510940
http://forum.mydomain.com/viewtopic.php?t=6168

I highly recommend MyDomain.com. They're reliable and reasonably priced. I have approx 2000 domains and they are 1 of 3 of my preferred registrars. The other 2 being Enom and NameCheap. Responses to problem tickets range from a few hours to a few days, but they are always eventually resolved. I use them for registering domains and I use their free dns services.

My oh my!!! What an oldie!!! It looks like u4eahost really doesn't like them if he's posting the same 5 liner posts in every mydomain.com thread he could find...

My oh my!!! What an oldie!!! It looks like u4eahost really doesn't like them if he's posting the same 5 liner posts in every mydomain.com thread he could find...

At least I went the extra mile not to copy-paste,
http://www.webhostingtalk.com/showpost.php?p=3861485&postcount=6
http://www.webhostingtalk.com/showpost.php?p=3861495&postcount=3

My webhosting contract with "mydomain.com" still runs but I cannot host my website. The bandwidth meter is stuck over the monthly bandwidth allowance and the MyDomain technical support has no interest (no "eta") as to when it will be fixed.

If they were decent with their job, they would calculate the correct monthly bandwidth balance and let my website run. Their response, "We will just give you 100MB, alright?". :uzi:

I even offered a Perl script to calculate correctly the bandwidth. No, it was not a 5-liner Perl script. :smash:

I do not understand how they make a mistake in calculating the bandwidth. Do they mixup different customers, or does the calculation process fail to work so they "estimate" the bandwidth consumption?

http://simos.info/blog/archives/521

u4eahost >> common knowledge on these forums is that you should buy domains from registrars and hosting from hosting companies. Unfortunately, you're one of many who mixed one with another and got what you got - incompetent hosting. You aren't the first, and, unfortunately, not the last to make that kind of mistake.

P.S. The original question in this thread was about *registering domains*, not hosting.

P.P.S. Your post in 'Domain Name Forum' seems really out of the place. People here discuss registrars, not hosting companies. You should agree that mydomain is rather good and trustworthy registrar...

...snip...

P.P.S. Your post in 'Domain Name Forum' seems really out of the place. People here discuss registrars, not hosting companies. You should agree that mydomain is rather good and trustworthy registrar...

In that respect, what about the issue of moving your domain away from a registrar. Are registrars proactive to release a domain for the final step of the transfer to take place?

My experience with MyDomain for the Domain transfer showed they are not proactive to release a domain. Three days passed with my domain in limbo (unusable) and I had to call them up to ask them to release it. If you park domains, you don't care about this, if you host them, it's important.

I understand 'limbo' was your own mistake (not updated nameservers as you changed your host, for example). Please correct me if I am wrong.

I understand 'limbo' was your own mistake (not updated nameservers as you changed your host, for example). Please correct me if I am wrong.

Well, when I initiated the transfer and I was at the last step that mydomain.com should acknowledge the release, I could find no more my domain in any of the MyDomain nameservers, nsX.mydomain.com (x=1,2,3,4). I do not know if you suggest to buy third-party DNS service for the 5-7 days of the transfer.

The new registrar (hey, it's NameCheap) would not allow to set the DNS server because the old registrar would not release, and the old registrar has already dumped my domain so I could not use the DNS servers.

And I cut 'n paste again....

As Stan has already mentioned. Your website should never be down during a domain transfer because you just point your domain's dns to wherever your website is currently being hosted. Even your hosting ip addresses will be included in the transfer, so there should be minimal (less than a minute) downtime. Your dns will resolve to your hosting from your old registrar until the new registrar's dns is propogated thru the net and is cached around the world. Then that will take over. It's the same ip hosting address in each case, so there will be no interruption of access to your website.

What NameCheap DNSes have in common with this? You must change them to the values you *host* gave you. Unless you haven't learned your lesson well and are purchasing hosting from the registrar (NameCheap in this case) again.

It appears I'll become an oldie through this thread :)

What I am saying is that no DNS server was carrying my domain, "thisdomain.com", during the time of the transfer. If there is no domain server that carries your domain, there is nowhere to point your domain registry records to.

When someone tries to connect to "http://www.thisdomain.com", their DNS resolver software finds the domain record for "thisdomain.com" and picks up the DNS servers assigned for this domain. There should be a DNS server that can say "Yep, I know www.thisdomain.com and its IP address is 1.2.3.4". Then, the browser will send an HTTP request to 1.2.3.4 and add "Host: www.thidsomain.com" in the HTTP headers, so the virtual host at 1.2.3.4 will send back the correct page for this customer. The Web server may host/park a few hundreds of virtual hosts, or in my case with MyDomain.com, over 3000 of them.

So, what I am saying is that the MyDomain.com nameservers did not have any records for my specific domain. Without such records, a visitors Web browser cannot find an IP address, cannot send an HTTP request with "Host: yourdomain.com", and cannot connect.

What I am saying is that no DNS server was carrying my domain, "thisdomain.com", during the time of the transfer. If there is no domain server that carries your domain, there is nowhere to point your domain registry records to.

Why not? Why were you not pointing to your hosting company's servers?

u4eahost, you don't need to explain such things to professionals like Stu or me. Thank you, however, that you made your point a little more clear.

When you create your child domain servers ns1/ns2/..../ns590.yourdomain.com, your request goes to the registry (in com/net case - Verisign, in .info case (as I understand we're speaking here about the .info) - Afilias). Then, having created nameservers, you can edit, delete, do anything you wish with them, using your current registrar's control panel, but at the end of the day all your editing will end at the registry, because it's the registry who keeps nameserver records.

So, if you're transferring domain with your own nameservers, you shoudn't have any downtime as well. *PROVIDED* that you have complete control over them and can change all the records (at least the most important ones: A and MX) in them freely.

I could explain this much earlier, but you have wrote something about MyDomain.com nameservers (nsX.mydomain.com), so I suspected you were using the ones provided to you by MyDomain.com

u4eahost, you don't need to explain such things to professionals like Stu or me. Thank you, however, that you made your point a little more clear.

When you create your child domain servers ns1/ns2/..../ns590.yourdomain.com, your request goes to the registry (in com/net case - Verisign, in .info case (as I understand we're speaking here about the .info) - Afilias). Then, having created nameservers, you can edit, delete, do anything you wish with them, using your current registrar's control panel, but at the end of the day all your editing will end at the registry, because it's the registry who keeps nameserver records.

So, if you're transferring domain with your own nameservers, you shoudn't have any downtime as well. *PROVIDED* that you have complete control over them and can change all the records (at least the most important ones: A and MX) in them freely.

I could explain this much earlier, but you have wrote something about MyDomain.com nameservers (nsX.mydomain.com), so I suspected you were using the ones provided to you by MyDomain.com

Indeed, I do not have my own DNS servers, so I was using those provided by mydomain.com. When I initiated the domain transfer, I found out that my domain's DNS records where no longer available at the mydomain.com nameservers, therefore I was stuck. This perhaps relates to the issue that my Website was blocked for "going over the bandwith limit" (this was a mistake of mydomain.com which they acknowledged but did not rectify whatsoever).

Indeed, I do not have my own DNS servers, so I was using those provided by mydomain.com. When I initiated the domain transfer, I found out that my domain's DNS records where no longer available at the mydomain.com nameservers, therefore I was stuck. This perhaps relates to the issue that my Website was blocked for "going over the bandwith limit" (this was a mistake of mydomain.com which they acknowledged but did not rectify whatsoever).

I am lost...

Can you answer one easy question then: why you haven't changed nameservers to your host's ones before the transfer?

Thank you.

I am lost...

Can you answer one easy question then: why you haven't changed nameservers to your host's ones before the transfer?

Thank you.

I do not understand what you mean with "my host's nameservers". I use shared hosting, therefore I do not have my own DNS service/server at my disposal; I use the default nameservers that the registrar provides. The gaining registrar (Namecheap) would not allow to configure a DNS server until after the domain transfer gets completed.

I do not understand what you mean with "my host's nameservers". I use shared hosting

You must either not received welcome letter from your hosting company or your host was so incompetent not to configure their own DNSes for you...

The standart situation for the fully hosted domain (not parked or redirected one) is to use nameservers that are configured at (and provided by) the hosting company. Using registrar's or even third party DNS is reserved for domain parking, redirecting or some kind of very advanced use for knowledgeable individuals/companies.

As soon as Mydomain released the domain and I could use the configuration options at Namecheap, I was able to activate my new webhosting account.

I think you have not understood the process of transferring a hosting account and you have not understood what Stan has been telling you. It is perfectly legitimate to have your domain registered one place and have your domain hosted somewhere else. You only need to configure the nameservers (of your new host) at the place your domain is registered. Wherever that might be.

I understand that the registrar and the webhosting company don't have to be the same; I use Namecheap which is registrar only.

"Mydomain", the domain registration component, does not provide name servers (no problem). So, when you change webhosting, you change the domain settings. When my website was blocked (erroneoysly, as admitted by Mydomain), I was not able to change the dns settings at the registrar part of Mydomain. Was this due to the webhosting being blocked? Maybe, as both user interfaces (registar + webhosting) are integrated. Was this a bug due to the changeover to Dotster? I don't know.