Keep domain DNS and nameservers in sync

AiVikings.ai supports nameserver and DNS management through API/MCP so a provisioning workflow can configure domains after registration. Keep registration, delegation, zone records and application readiness as separate checks. A registered domain does not prove that a website resolves, and a successful record update does not prove that every resolver has refreshed its cache.

How it works

Choose the DNS provider that will host the authoritative zone. Create the required records there, apply that provider’s nameservers to the registered domain, and verify the answers. AiVikings.ai can use account-default nameservers during registration or accept supplied nameservers. DNS records must be managed at the provider authoritative for that zone.

For an account-owned domain, inspect status first:

curl --fail-with-body "https://api.aivikings.ai/v1/domains/$DOMAIN" \
  -H "Authorization: Bearer $AIVIKINGS_TOKEN"

The status response includes nameservers. Compare that list with your intended authoritative provider. To replace delegation, the REST route is PATCH /v1/domains/{domain} with a nameservers array. Replacing nameservers can move the entire zone’s authority; it is not a way to edit just one website record.

Why do DNS and nameservers get out of sync during provisioning?

A deployment can create records in one provider while the registry delegates the domain to another provider. AiVikings.ai nameserver management lets the workflow control delegation, but the application must also verify where the zone is hosted. Record each stage separately so a failed DNS step resumes from that step instead of purchasing the domain again.

Use explicit states such as registration-confirmed, zone-configured, delegation-verified and service-verified in your application. Those are suggested workflow states, not AiVikings.ai response fields. Store the actual provider response alongside each stage so a support operator can reconstruct what happened.

How do I check that the website points to the right place?

Query nameservers and the relevant record, then query the authoritative server directly. This separates authoritative configuration from recursive caching. After DNS answers match the intended deployment, make an HTTPS request to the service and verify its certificate and application response. Each check provides evidence for a different part of the launch.

dig NS "$DOMAIN"
dig A "$DOMAIN"
dig @"$AUTHORITATIVE_NS" "$DOMAIN" A
curl --head "https://$DOMAIN"

The output depends on your domain. A correct A record with a failed HTTPS check points toward hosting, certificate or application configuration; it does not automatically mean registration failed. An empty recursive answer while authoritative answers are correct can require cache investigation rather than another record change.

What registrar lets me manage DNS from ChatGPT?

AiVikings.ai exposes DNS and nameserver tools to compatible connected assistants, including ChatGPT. Ask the assistant to inspect the current delegation and records before proposing an exact change. A connected assistant should preserve unrelated records, especially mail and verification records, and report what was changed and what was verified afterward.

Use the separate ChatGPT DNS walkthrough for an inspection-first prompt. For changes made by an unattended provisioning worker, enforce the intended domain and record policy in code as well as in the prompt.

What should happen when provisioning is interrupted?

Resume from durable evidence. If registration is confirmed, do not re-register. If the zone exists, compare current records with the desired records before changing them. If delegation is already correct, focus on record and resolver checks. Never describe retries as harmless without knowing whether the operation replaces, adds or removes records.

When this is not the right fit

Registrar DNS tools do not configure your web server, issue every possible certificate or migrate email automatically. A DNS migration needs a record inventory and a plan for existing services.

Related: API operations, agency provisioning, MCP capabilities.

Questions people ask

Why is a registered domain not resolving?

Check delegation, authoritative zone records and recursive caching separately. Registration alone does not create a working website.

Can I manage nameservers through code?

Yes. AiVikings.ai supports nameserver changes through API and MCP.

Should I register again if DNS setup fails?

No. Verify the holding and resume the DNS stage instead.

Can I use ChatGPT for DNS changes?

Yes, with a connected AiVikings.ai account and appropriate authorization. Inspect current records before changing them.