Order Accept Encountered Problems No nameservers are defined for the server this domain is assigned to. Please correct and try again.

[battles]

We've had our ENOM connection for years now. No changes to our default nameservers.
Suddenly - we cannot register domains.

Order Accept Encountered Problems
No nameservers are defined for the server this domain is assigned to. Please correct and try again.

 

Anyone else experiencing this?

[WHMCS Dan]

This indicates no nameservers are set when ordering the domain name.

We have details on how to configure default nameservers to use here: https://help.whmcs.com/m/system/l/784165-specifying-the-default-nameservers-to-use-when-ordering

 

[battles]

Can confirm those have been in place for years now. No changes made to our default name servers.

[WHMCS Dan]

In that case it may be that the client removed the nameservers in the order process.

Please feel free to drop us a support ticket and we can take a look and best advise.

[battles]

Thanks I will do. I also tried to place the order on the customers behalf from the client screen and ran into the same error

 

thanks!

[velocity08]

Having exactly the same issue

have tried the same steps

have you had any success in resolving this issue by any chance?

ta

[Pnrhost Support]

On 11/22/2020 at 11:15 AM, velocity08 said:

Having exactly the same issue

have tried the same steps

have you had any success in resolving this issue by any chance?

ta

For me it was because the domain i wanted to register was already set as the hostname on one of the vps service for a client, so i simply had to rename the hostname from within whmcs

[Dale Grimmond]

I was having the same issue. 

It turned out that I had to enter a phone number into the users profile and it worked!

I take it the error message can be a tad generic at times.

[johnc]

We had the same issue.

One client already had shared hosting(example.com) with us but the domain is with other registrar.
Later, client ordered transferring the domain(example.com) and paid its invoice.
However, from admin, we could not process transferring accept order with next error message.

No Nameservers are defined for the server this domain is assigned to. Please correct and try again.

The above error message is misguiding.

On 1/11/2021 at 5:00 AM, Pnrhost Support said:

For me it was because the domain i wanted to register was already set as the hostname on one of the vps service for a client, so i simply had to rename the hostname from within whmcs

We tried what @Pnrhost Support suggested and changed domain "example.com" to "1example.com" in shared hosting.
This step by-passed WHMCS side validation but another message received from Registrar

[601] Failed to create order: DomainPassword

We had a look database tblorders, the order record's  transfersecret value was not there.

Thus, we manually update like the following. (s:11 means string length of "example.com")

a:1:{s:11:"example.com";s:8:"AuthCode";}

Then, we could process [accept order] in WHMCS admin. 

I assume that WHMCS does not save Auth Code correctly when there is exising domain in another service.
 

Edited April 15, 2021 by johnc

[Dale Grimmond]

The problem is exactly what Pnrhost Support said. The client already has a service associated with the domain name.

In my case, the client had hosting in place then transferred their domain at a later date.

I simply changed the domain from example.com.au to _example.com.au then transferred the domain then once complete i changed the hosting package back to the real domain.

[wildhoster]

This problem is ridiculous. My site is going live next week and I don't know if my clients are going to run into brick walls creating an order. 

Can anyone confirm that this only happens when an admin is making an order, or does it apply to all orders?

Is there a fix for this? This is a major problem obviously!

 

[Rk Barnwal]

I can't register a new domain... I have Connect Reseller.  It's says "Registrar Error 401 - Unauthorized - Unauthenticated user" 

Please give me any solution.. 

[wildhoster]

This community doesn't seem to be very active or helpful. This is a clanging error that must have a simple solution.

I can't transfer a domain in because of this error. Tried filling in nameservers everywhere. Also 'reset to default nameservers' does nothing. (default nameservers are correctly specified)

[wildhoster]

I solved this issue after contacting support. The problem was I hadn't entered the default nameservers information in the server settings.

Go to: System Settings > Servers* (listed under products/services) > Edit (Small icon on the right). Add your nameservers and click 'Save changes'.

* Obviously if you have more than one server, you'll need to select the appropriate one to edit. I only had one, hence I overlooked this requirement.

[natanet]

even the default nameserver is already there.. if the customer remove ns1 and ns2.. yes error will occur..

so the solution might be edit the template tpl and add required=true for each nameserver field

[Jade D]

On 1/10/2021 at 8:00 PM, Pnrhost Support said:

For me it was because the domain i wanted to register was already set as the hostname on one of the vps service for a client, so i simply had to rename the hostname from within whmcs

exactly the same issue

[Vander Host]

On 10/01/2021 at 8:00 PM, Pnrhost Support said:

For me it was because the domain i wanted to register was already set as the hostname on one of the vps service for a client, so i simply had to rename the hostname from within whmcs

Thank you! Similar problem, client had placeholder VPS domain name, similar to new one I wanted to register.

[DongTL]

Faced same issue if purchase service and domain registration together

[Rami Alloush]

For me the problem as @wildhoster described.

When buying Domain and Hosting together, the server needs to have default nameservers set (it seems the domain takes the values from there automatically).

Thanks 

[WHMCS John]

Hi all,

I've created a help guide with steps to resolve this error: https://help.whmcs.com/m/provisioning/l/1588279-troubleshooting-a-no-nameservers-are-defined-for-the-server-this-domain-is-assigned-to-error

[AnthonySmith]

On 8/09/2022 at 11:06 AM, WHMCS John said:

Hi all,

I've created a help guide with steps to resolve this error: https://help.whmcs.com/m/provisioning/l/1588279-troubleshooting-a-no-nameservers-are-defined-for-the-server-this-domain-is-assigned-to-error

In the case of WHMCS being the server I can confirm this does not resolve the problem, only changing the hostname in the virtual server product then accepting the order again resolves it.

[AnthonySmith]

Appologies my previous reply should have read:

In the case of SolusVM being the server I can confirm this does not resolve the problem, only changing the hostname in the virtual server product then accepting the order again resolves it.

[Web_Vendors]

I'm facing this error;       An issue was encountered while registering the private nameserver.  Anyone who can assist please

[Jade D]

On 1/10/2021 at 8:00 PM, Pnrhost Support said:

For me it was because the domain i wanted to register was already set as the hostname on one of the vps service for a client, so i simply had to rename the hostname from within whmcs

Aha well spotted and thanks for sharing, this resolved the issue for an order 🙂