
|
View Full Version : Tucows not recognizing my nameservers
kiracm 08-09-2005, 05:26 PM I have been trying unsuccessfully since July 27 to get my nameservers changed on a domain registered with Tucows. When I try to change them, it states that the nameservers are unrecognized by the registry. I cannot transfer this domain to enom since it is a .org less than 60 days old. I have contacted Startlogic who sold me the domain. There is nothing they can do. I have contacted enom. There is nothing they can do, contact Tucows. I have sent them tickets with no response whatsoever. I have called them and keep getting shuffled through their automated system. The account that this domain name is set on is going to shut down as of Friday. I cannot transfer for another 30 days. This site receives 1000+ hits a day. I am getting VERY frustrated and do not know what to do. Any ideas?
svdorr 08-09-2005, 05:34 PM Okay, 2 things.
1. Are the name servers properly registered as name servers with you registrar?
2. It sounds like your domain in question is a .org. Are your name servers in a different TLD, meaning do they end in .com or .net?
If so, Tucows may need to do something on their end to allow a different TLD for your .org. I have read that some registrars need manually intervene to make this work. Enom, it works find with out getting them involved, as I have several .org domains with .com and .net name servers.
kiracm 08-09-2005, 05:38 PM My name servers are properly registered. I have several other domains on my server that have experienced no problems. The TLD for the nameservers are .com. Enom has told me that there is nothing they can do. I can't even get ahold of anyone at Tucows. Have any ideas how to get ahold of them besides spamming them with tickets? What exactly do I need to ask them to do to manually correct this?
Now also, the original nameservers are .com.
svdorr 08-09-2005, 05:43 PM What is the domain in question. If you don't feel comfortable posting it, you can PM me.
svdorr 08-09-2005, 05:56 PM Depending on what the exact error messag is, this FAQ might be the answer.
Q:What does "unable to verify existence of nameserver" mean?
A:Some registries such as .us, .info, .biz, .name, .org and .cc maintain their own databases of registered, valid name servers, rather then going by the VeriSign .COM/.NET Registry database.
If you are receiving "unable to verify existance of name server" error messages, it's likely due to the name server not being found in their database.
You can add your name servers to the various registries through the "Add Nameserver to All Foreign Registries " link in the resellers interface. Once added, you should be able to process your registrations.
kiracm 08-09-2005, 07:23 PM I am not a reseller with them. Any ideas how to do this outside of the reseller interface?
svdorr 08-09-2005, 08:04 PM StartLogic is the reseller. You should see if they can do what I mentioned in the FAQ. The message you PM'ed me suggests that this might be the resolution. See what they say and I will do some additional checking.
kiracm 08-09-2005, 08:12 PM I have contacted startlogic multiple times. They have told me there is nothing they can do, contact enom or tucows. I will call them back and see if they can do what is said in the FAQ. If not, I will be back :)
svdorr 08-09-2005, 08:15 PM Let us know what they say. Your name servers look good. I think the FAQ may help. After all is said and done, I suggest your find a different place to register your domains. As a reseller, they should be providing you support and from what you have said, they don't seem to be very helpful. Good luck and let us know. We'll get it figured out for you.
CD Burnt 08-09-2005, 10:00 PM just get a free zoneedit account and use their nameservers for a while.
or try a dnsmadeeasy account.
Domainitor 08-09-2005, 10:06 PM Speaking as a registrar (and no, not Tucows) I wouldn't be surprised if their (Tucows) policy is to require that the registrant of the domain under which the nameservers are defined be the party that registers the nameservers in the .org registry (in this case). For example, if ns1.example.com is the unregistered nameserver, then the registrant for example.com *should* be responsible for having their registrar add ns1.example.com to the .org registry. If, on the other hand, the registrar for example.com is not operational in .org, Tucows, it would seem to me, should register the nameserver on their behalf for you, their customer.
This is our general policy because if we register a nameserver object in the database, we "own" it, and while foreign nameservers (the nameserver's TLDs in a registry with a different TLD) don't need IP addresses, it's still "our" object and we'd rather not "own" the nameservers for someone else's domain....
FAF Hosting 08-10-2005, 03:44 PM Tucows doesn't seem to restrict what domains its resellers use for the "Add Nameserver to All Foreign Registries" command. I hae been a reseller with them for several years and recently had to do this for a nameserver of mine but the domain of the nameserver was registered with another registrar. Ideally it should be the responsibility of the owner of the nameserver you are trying to switch to, but your current registrar should be able to do it in less than a minute. In fact, I am willing to try under my account if you want me to, I would just need the nameserver name.
Other than that, using another nameserver that it is recognized is the best option or you can create nameservers under your domain name such as ns1.yourdomain.org and use the ip of the nameserver that you are trying to switch to. There are a couple of issues with that approach as the name server listed in the zone file would likely be different but in my experience it would probably resolve fine.
AlloyHosting 08-10-2005, 04:26 PM Hey,
With tucows i created name servers, and after 92 hours, they still wern't active. So i moved to my own little registar.
why dont you use some of the free dns services such as zoneedit.com afraid.org domaindns.com everydns.net and avoid this mess.
kiracm 08-15-2005, 02:34 PM I did not register this domain. If I had I would not be having this problem. However, enom resolved it for me. Thanks for everyone's advice :)
|