Hurricane Electric's IPv6 Tunnel Broker Forums

DNS.HE.NET Topics => General Questions & Suggestions => Topic started by: turismopt on August 30, 2017, 01:35:24 AM

Title: [SOLVED] DNS Issues - Unable to delegate new .PT domain on ns1.he.net
Post by: turismopt on August 30, 2017, 01:35:24 AM
Hi,

The new changes on the system makes system unusable for .PT domains.

The system is requiring that the domain is previously associated with the NS of HE.net, although the portuguese registrar DNS.pt, does exactly the same. For a domain to be pointed, it needs to be delegated on the Name Server (ns1.he.net , etc) 

Any ideas to solve this? This is something new.. I never had issues before ;D

DNS.PT evaluator to see if you can point the domain to a certain NS servers.

Domain: empregos.pt
NS: ns1.he.net
https://www.dns.pt/en/tools/technical-evaluator/


Evaluation Result:   Invalid technical information
Message:   DnsException: Error #4;
The server is not autoritary for the domain;
ns1.he.net
Title: Re: DNS Issues - Unable to delegate new .PT domain on ns1.he.net
Post by: snarked on August 30, 2017, 05:22:35 PM
See if this order of operations helps:
1)  Add he.net servers to zone.  Reload zone.
2)  Tell he.net servers to serve the zone.
3)  Tell the registrar to add the he.net servers.
Verify that it works.
4)  Remove other servers at registrar (if applicable).
5)  Remove other servers from zone.  Reload zone.

When reloading the zone, don't forget to bump the SOA serial first.
Title: Re: DNS Issues - Unable to delegate new .PT domain on ns1.he.net
Post by: turismopt on August 31, 2017, 02:27:43 AM
Thank you for your reply.

This was solved through HE.NET support.

"
Yes, this is relatively new. We require that new domains be delegated first for security reasons. The registrar sometimes requires that the zone file exist before delegation, also for security reasons.

The way around it is to do exactly as you have done: set up the zone file and send us and E-mail. We can use our admin interface to clear up the delegation issues.
"

Regards,


See if this order of operations helps:
1)  Add he.net servers to zone.  Reload zone.
2)  Tell he.net servers to serve the zone.
3)  Tell the registrar to add the he.net servers.
Verify that it works.
4)  Remove other servers at registrar (if applicable).
5)  Remove other servers from zone.  Reload zone.

When reloading the zone, don't forget to bump the SOA serial first.