Delegation and verification - Aptranet Developers

Delegation is controlled at the domain’s parent—usually through its registrar—not inside the Aptranet zone.

Before changing nameservers

Recreate every required record set in Aptranet.
Query both Aptranet nameservers directly.
Compare answers with the current authoritative provider.
Verify that CNAME targets and mail/service hostnames also resolve.
Confirm DNSSEC state with the registrar. Do not leave a stale DS record when moving to an unsigned or differently signed zone.

Verify authority

dig @APTRANET_PRIMARY_NS example.com SOA
dig @APTRANET_PRIMARY_NS example.com NS
dig @APTRANET_SECONDARY_NS www.example.com A

After delegation:

dig example.com NS +trace
dig @1.1.1.1 www.example.com A
dig @8.8.8.8 www.example.com A

Propagation

Resolvers cache NS and record answers according to their TTLs. During the transition, some users can reach the old provider while others reach Aptranet. Keep both zones consistent and active until the former delegation is no longer observed.

Lower high application-record TTLs before a planned address change. Nameserver delegation has its own caching behavior, so lowering only the new zone’s records does not make the parent delegation change immediate.