Hi all,

Is there actually anyone working on the support department of ENOM?
I've opened a support ticket on monday. They responded with a question and since then nothing. I've updated my ticket on Tuesday, today...
nothing.

I registered a .BE domain with them for a client of mine. (alongside the .eu and .com)
I cannot however change the nameservers to mine on the .BE. (while it works perfectly on the .COM & .EU ... and other domains I have for that matter)

I always get the following:
nRRPResponseCode 507
Nameserver ns1.########.com cannot be registered (removde my nameserver for privacy reasons)


I also tried other nameservers I use frequently. None work.
My client is a getting to wait since he wanted to use that .BE as his main domain. (.com & .eu should only point to the same website)
Hence I suspect there is something wrong on their side.


Anyone else got this error ? I searched the forum and found only 1 post.

:mad: :confused:


greets

Just an idea: you could ask the registry (dns.be) why they reject your nameservers. For example .de has some requirements on the SOA record or else they won't accept your nameservers AND the domain has to be active in the dns server prior registration.

I've no idea how long eNom needs to track the problem, but after all: ygwypf (you get what you pay for) ;-)

Moniker accept Be. The only 'rare' extensions i have now, are in moniker.

Just an idea: you could ask the registry (dns.be) why they reject your nameservers. For example .de has some requirements on the SOA record or else they won't accept your nameservers AND the domain has to be active in the dns server prior registration.


could be but I have another 5 .be's I manage under 2 other nameservers and even this these nameserver enom generates an error.
This rather tells me there's something wrong on enom's side...


and I do not agree on the "ygwypf" issue. Enom is big and a lot of people do business with them. Besides I bought the domain at industry standard prices.


anyway I guess I have no other option but to wait for enom... if not, I'll be forced to transfer the domain somewhere else...


thanks for the tip though ;)

grts

It sometimes take a while to diagnose and fix problems with individual country-code domains. This is because eNom has to work directly with the country registrar, which are not usually very fast themselves.

I would suggest you contact your parent reseller (whomever created your eNom reseller account for you) and ask them for assistance. It is their job to work with you and eNom to get help when needed.

I would suggest you contact your parent reseller (whomever created your eNom reseller account for you) and ask them for assistance. It is their job to work with you and eNom to get help when needed.
Agreed!
I've already contacted them. I currently still work with Resellerzoom but I find the way they helped me way off limits. The guy who helped me was rude.
He closed the ticket after each reply and giving me answers I already knew acting if I didn't know what I was talking about.

Closing a ticket without asking first if all is alright is IMHO very rude. (theoretically following the ITIL principles this isn't even allowed! a support desk needs to put it on "resolved" and if the support requester doesn't close the ticket himself it may be closed automatically after x days... anyways... enough of that)


I guess i'll have to wait.
Although if enom is waiting for an answer by dns.be they could at least update the ticket telling me they're working on it...
now I'm left in the dark...


greets

I agree that eNom should update the ticket and let you know what's going on. However, I do understand what might be happending.

Often, the "tech guys" in the cubicles who deal with these issues with the country registrars are not very "support or service" oriented. They are tech people, and so tech things are their priority and consideration. When they get a ticket assigned to them, they often don't update it until the job is resolved.

It's very annoying since you (and I've been there myself a few times!) are in the dark, while they are working on it.

What you can do is update the ticket and ask for status update. This will trigger it to go back to customer service people, who will manually find out status from whomever (tech person) is assigned to the ticket.

yes I did that about 4 times :)

but I finally got a response.
They closed it and said I have to ask for support with godaddy (the registrar where the domain of the nameservers is located...)

and ask godaddy to register these nameservers with dns.be...

what a ride...
now on to godaddy... I'm curious how long that will take :)

**sight*** ;)

Godaddy has a ton of support "specialists", so you'll probably get a pretty fast response.

Whether they know what they are doing... now that is another matter and is usually a crap shoot for complicated support issues like this one.

You might get lucky and get the ticket assigned to someone who cares about their job, though. :)

Agreed!
I've already contacted them. I currently still work with Resellerzoom but I find the way they helped me way off limits. The guy who helped me was rude.
He closed the ticket after each reply and giving me answers I already knew acting if I didn't know what I was talking about. Do you have the ID of the ticket where you received these rude responses?