NameCheap nameserver tool is broken? Anyone else seeing this?

[aww]

I've been waiting for a week for namecheap to fix this with no answer in sight as apparently it's a bug in their api.

Does anyone have working nameservers registered with namecheap (enom etp/reseller)?

I mean working with their own DNS
ns1.example.com
ns2.example.com

I've got it registered properly but it will not resolve (ping fails) for over it a week now. Tried deleting and re-creating it to no avail.

Only helpful thing that I've spotted is that when you check the nameserver via enom's own lookup

http://www.enom.com/domains/RegNameServer.asp

You just get "OK" when a properly working nameserver
will say "OK LINKED"

NameCheap takes forever to respond and I doubt their ability at all to solve this. Maybe I'll try writing enom directly but I doubt they will help me directly since it's through a reseller (and they may not be allowed to help anyway).

 

[AzN]

http://www.internic.net/whois.html
Query here as Nameserver, does it show up?

 

[aww]

http://www.internic.net/whois.html
Query here as Nameserver, does it show up?

Nope.

Nameserver registered with NameCheap, doesn't resolve.

Registered directly though eNom, resolves.

I'm trying to find someone else with a namecheap account & nameserver that can confirm.

 

[floatingworld]

...currently not aware of nameserver problems but will try a few checks over the weekend...however I find I need to send email follow up to get EPP code after using NC form. GD in comparison is instant re EPP code request.

 

[aww]

floatingworld, with enom when you request EPP code, make sure your whois email address physically exists (not just wildcarded).

Unlike their support emails, etc. the EPP for some reason checks for a physical address. If you are using cpanel or something like that, make a physical mailbox and then forward that address anywhere you'd like.

 

[SharonTucci]

NameCheap takes forever to respond and I doubt their ability at all to solve this. Maybe I'll try writing enom directly but I doubt they will help me directly since it's through a reseller (and they may not be allowed to help anyway).

Wow, my average Namecheap support response time is around 20 minutes. I've not had to wait more than a couple of hours even within several years. Have you actually contacted them about this?

 

[aww]

I've not had a namecheap response in less than 12 hours on any question. Granted I've only asked a few as I am a relatively new customer.

I think my biggest irritation with this is that I have to ask the question in the first place and instead of examining the nameservers with their own interface for the settings, they ask me a stupid question like what IP the nameserver is set to (and then I have to wait another several hours for a reply to my reply to them).

 

[aww]

New record - 24 hours with no response from them.
eNom says they can't do a thing to help me and it's all NameCheap's problem.

Sigh. Completely fustrating.

I guess as soon as my domains hit 60 days, I'm transfering out of NameCheap.

 

[Name Trader]

All of my domains at NameCheap are just parked. They all resolve normally. I get mixed response times from NameCheap, but on the whole they're usually less than 24hrs.

 

[aww]

Two days (additionally) I finally got an answer that indirectly helped me figure out the problem.

eNom's interface by default provides a wildcard A host record. NameCheap does not even mention the wildcard let alone suggest it so I didn't have one.

So it's not specifically their fault but I wish that was more clear and that they had responded a bit faster than 24+ hours to my queries.

Problem solved.

 

[NP02139]

Two days (additionally) I finally got an answer that indirectly helped me figure out the problem.

eNom's interface by default provides a wildcard A host record. NameCheap does not even mention the wildcard let alone suggest it so I didn't have one.

So it's not specifically their fault but I wish that was more clear and that they had responded a bit faster than 24+ hours to my queries.

Problem solved.

If that solved the issue, then you didn't have a *nameserver registration* problem.

Nothing on the domain's nameservers will affect that domain's own nameservers.

Nameservers are registered at the Registry, and therefore the only records they rely on are those in the *Registry's* nameservers. For .COM(Versign) thos are a.gtld-servers.net, b.gtld-servers.net, etc.