Not Propagated - Rejected

I am solving this issues for the past 3 days now I bought domain from other website and I am pointing to my reseller's nameservers but it's not propagated. Unfortunately your request to update name servers on xxxxxxxx.net has been declined by the respective registry operator. There are various reasons why this may occur, however this type of problem usually happens when: 1. The name server names that are provided are incorrect or 2. The name servers provided have not been set up with the zone of your domain name or 3. The DNS provided by your hosting provider has not been set up to DNS appropriate DNS standards To correct your configuration, please follow this check list: 1. Please ensure that a minimum of 2 name servers have been provided. If your hosting provided is using 3 or more name servers, please provide the details for all name servers. 2. The name servers IP addresses must be static, and the name server host names must resolve to these IP addresses. 3. The provided name servers must be authoritative for the domain name. This means that your domain name zone record of shareyourpost.net must exist on all name servers. 4. Name servers submitted must match the ones indicated in the zone file of your domain name. 5. The DNS servers hosting the zone should not give the following responses: i) not responding or server failure ii) not reachable iii) non-existent domain (NX) iv) host not found v) permit ICMP requests (allow pings) " this requirement only applies to a select few ccTLD providers Many registry operators will not permit the delegation of your domain name unless all name servers are responding correctly. 6. The primary (Master) name server must be the same as indicated in the Start of Authority (SOA) as shown in the zone record for your domain name. Only a few ccTLD operators enforce this DNS standard, so this problem is quite common. 7. At least one MX or A record must exist in the zone file for your domain name. Some registry operators will not approve the name server change unless both an A record and a MX record exists in the zone file of your domain name. 8. The domain name of the name server host name provided in the SOA cannot be a CNAME. This type of scenario is a non-standard DNS configuration, and it is not a common problem. 9. Where a MX record is listed, it must not have a matching CNAME. This type of scenario is a non-standard DNS configuration, and is not a common problem. 10. The zone serial number for xxxxxxxx.net must be the same on all name servers. Only some ccTLD providers perform this check, however to ensure correct operation of your domain name, it is highly recommended that the zone details are the same across all name servers. Please make these appropriate checks and corrections, and re-submit your name server update. Alternatively, you may use our free DNS forwarding service to point traffic to your web (www) and mail (mx) servers. This action can also be initiated by logging into our web site.
Thanks in advance.

Infopro

March 05, 2015 10:29

Have you asked at your Domain Registrar or Hosting Provider about this? You might start there.

host4marketers

March 05, 2015 11:12

Yes, that email came from my domain registrar...

March 05, 2015 11:22

Automated message then I would think. if you're unsure of what those instructions explain, asking them for assistance in understanding them might be useful. As you can see by the message, it could be one or more of several issues. No way of knowing which one from this end. You'd have to go thru all your settings mentioned in that email to see if you can find a mistake in your configuration. Pop your domain into this checker: /http://www.intodns.com/ See any issues there?

March 05, 2015 11:34

Thanks for being responsive Infopro... happy to be here than my registrars support... lol. I made some adjustment on my WHM DNS settings and waiting for the effect. will be back here again after few hours to see the result. Thanks much.

March 05, 2015 12:13

Happy to help. GL!

March 06, 2015 15:03

I'm back... Unable to Update Nameservers We encountered some issues when setting nameservers. The reported problem is: 3031166 Nameserver 'ns1.xxxx.com' could not be registered. I already set the ns1, ns2, and ns3 on my WHM did I miss something?

March 06, 2015 15:15

Are the nameservers configured properly at your Domain Name Registrar? Are you with namecheap by chance? /https://community.namecheap.com/forums/viewtopic.php?f=6&t=5477

March 06, 2015 15:38

I tried the nabber

cPanelMichael

March 06, 2015 17:07

You may also find this thread helpful: Tutorial - Setting Up Name Servers Thank you.

Not Propagated - Rejected

Comments

Didn't find what you were looking for?