Find the right place to edit your DNS records

Before you start

Edit records at the provider named by the parent delegation, after confirming that its assigned servers answer for the domain.

Have the domain, registrar access and intended record ready. Save the present value and TTL first. A hosting panel can show an unused zone when the parent delegates DNS elsewhere; edits there will not change public answers.

Confirm parent delegation and live authority

Confirm the parent-side delegation in the registrar account, or query the parent zone for the domain's NS set; for a .com example, dig @a.gtld-servers.net example.com NS +noall +authority shows the parent referral. Replace the illustrative domain and use an actual parent server for its TLD. Compare this with dig NS example.com +short, which can be a cached recursive or child-zone answer. Query each parent-delegated server for the zone's SOA and intended records before choosing a DNS panel.
Sign in to the DNS provider named by those servers. Check that its zone contains the existing public records.
For a website move, note the current A/AAAA or CNAME records. For an email move, note MX, SPF, DKIM and DMARC too; changing nameservers without carrying those records over can interrupt mail.
Edit only the record you intended. Do not paste a full hostname into a field that automatically appends the domain; inspect the provider's preview of the final name.

Verify what was published

Query an authoritative server directly, for example dig @ns1.example-dns.test www.example.com A, using your actual nameserver. Then query a public resolver with dig www.example.com A. Compare the answers and record types. If the authoritative answer is wrong, correct the live zone. If it is right but a resolver still shows the old value, read the propagation guide before changing anything again.

For an illustrative www.example.com A change, the delegated server should return the new assigned address and type; an old recursive answer after that points to caching rather than a second DNS panel.

When to ask for help

The domain owner controls registrar access and decides which provider hosts DNS. Novasean can advise on records for a Novasean service, but a third-party DNS provider's interface and propagation are outside our control. Contact support with the domain, intended record, current authoritative nameservers and the two lookup results; omit account passwords.

Map the records before a move

Use a small record inventory so a nameserver move does not silently remove mail or verification records. The values below illustrate record roles only; every address and hostname must be replaced with values supplied by the relevant service.

Record	Illustrative name	Purpose and check
A	example.com	IPv4 address for the website; confirm it is the assigned web target.
AAAA	example.com	IPv6 web target; remove an obsolete value only after checking IPv6 use.
CNAME	www.example.com	Alias to the intended site name; a CNAME cannot coexist with other records at the same name.
MX	example.com	Inbound mail destination; keep the provider's priority and target.
TXT	example.com	SPF or service verification; preserve unrelated TXT records.

Check both apex and www: a working apex does not prove www is configured. Changing only A while an old AAAA remains may send IPv6 visitors to the previous host.

If DirectAdmin and another DNS panel disagree

Compare the registrar or parent-zone delegation with dig NS example.com +short; a recursive or child-zone NS answer can differ from the parent's delegation. Query one delegated server with dig @ns1.provider.example www.example.com A +noall +answer. The answer section should name the requested host and show the record type, value and TTL. If the delegated server gives the expected record while DirectAdmin shows something else, DirectAdmin's copy is probably not the active zone. If the delegated servers disagree with each other, ask the DNS provider to check zone synchronisation before changing records in a second panel.

After a nameserver change, compare the full old and new zones. Mail may keep working briefly because of caches and then fail once resolvers use the new authority. Include MX and mail authentication records, not only the website address. DNSSEC also needs attention: a stale DS record at the registrar can make a correctly populated zone return validation errors.

Common questions

Does buying hosting move my DNS automatically? No. The domain remains delegated to the nameservers set at its registrar until they are changed.

Can I leave two providers authoritative? Only if the delegation and both providers are deliberately configured to serve consistent zones; accidental mixed nameservers produce intermittent answers.

Should I change NS to add one record? Usually no. Add the record at the existing authoritative provider unless you are intentionally moving the whole zone.

Can a child-zone NS answer settle the registrar delegation? No. Compare it with the parent delegation; disagreement requires the DNS operators to reconcile the two sets.

Sources and technical references

Prepared by Team Novasean from the references above. Menus and available features depend on your installed version and service permissions.

Related guides

Was this guide helpful?

If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .

Need help with your service?

Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.