Title: Fix “NameServer Is Not a Valid Nameserver” Error in Demo API  
PrimaryCategory: Domain Names  
Type: Informational  
Tags: demo_api, nameserver_error, domain_registration, tld_validation, com_net  
Source UI Terms: None  
Source Reference: Fix “NameServer Is Not a Valid Nameserver” Error in Demo API  

Key Info:  
When using the Demo API to register domain names, you may encounter the error:  
`{&quot;status&quot;:&quot;error&quot;,&quot;error&quot;:&quot;NameServer is not a valid Nameserver&quot;}`. This error occurs because the Demo environment validates the nameservers at the Registry. If the nameserver provided is not recognized as valid by the Registry for the domain&#39;s TLD, the API returns this error.

The most common scenario leading to this error is when attempting to register a .COM or .NET domain name using nameservers from the same TLD. The Demo environment checks nameserver validity against the Registry and throws an error if the nameserver is invalid for the domain&#39;s TLD.

Solution:  
To resolve this, use nameservers that belong to a different TLD than the domain you are registering. For example, if you are registering a .COM or .NET domain, use nameservers under a different TLD such as .ORG or .IN. By providing nameservers of a different TLD, the Demo API bypasses the Registry&#39;s validation check and accepts the nameserver.

Summary:  
The “NameServer is not a valid Nameserver” error in the Demo API happens because nameserver validation is performed at the Registry. To fix it, use nameservers from a different TLD than the domain being registered.

Evaluation Pairs:  
Q: What does the “NameServer is not a valid Nameserver” error mean in the Demo API?  
A: It means the Demo API validated the nameserver with the Registry and found it invalid for the domain&#39;s top-level domain (TLD).

Q: How can I fix the nameserver validation error when registering a .COM/.NET domain in the Demo API?  
A: Use a nameserver from a different TLD, such as .ORG or .IN, for the registration so the Demo API does not validate it at the Registry.

Q: Why does the Demo environment check nameservers differently than production?  
A: The Demo environment performs Registry validation on nameservers and generates this error to test validation logic, requiring different TLD nameservers to bypass the check.

When the Demo API returns a “NameServer is not a valid Nameserver” error. This article explains how to resolve this issue.
 
Issue :
You may encounter the below error message while trying to register Domain names via the Demo API Environment -
 
Exact Error :   {&quot;status&quot;:&quot;error&quot;,&quot;error&quot;:&quot;NameServer is not a valid Nameserver&quot;}
This usually happens when you try to register a Domain name via API in the Demo environment. The calls made in the Demo environment too validate the Name Servers at the Registry. The Demo environment runs a check if the Name Server is valid at the Registry and if it is not then it throws an error that the Name Server is not a valid Name Server.
 
Solution :
The solution to this is simple. If you are registering a .COM/.NET Domain name, then you have to simply use a Name Server of some other TLD like .ORG or .IN. If the Domain name and the Name Servers are of different TLD&#39;s, then our Demo Environment does not validate the same at the Registry.

When the Demo API returns a “NameServer is not a valid Nameserver” error. This article explains how to resolve this issue.