Host and manage DNS for a domain

DNS is coming soon. Website administrators can preview it.

The preview lists domains in the selected Personal or team context. DNS hosting is included. Team access still applies: viewing a team's domains requires access to that team, and changing its DNS requires a team admin role.

DNS and Mail share each domain. Adding a domain that already belongs to Mail opens its existing setup. Adding it in DNS does not enable Mail or require a Mail plan.

Add a domain

Choose Add domain, enter a domain such as example.com, and add it to the selected team. On its page, choose Host DNS with Magpie or Keep my current DNS provider.

With external DNS, the zone stays at the current provider. Add the verification TXT record there and choose Check verification. The value is shown once; Make a new verification record replaces a lost value. Mail's required records remain available in Mail settings.

Move DNS to Magpie

Magpie imports records before showing the nameservers to use. A complete zone transfer is tried first. When the provider does not allow that, Magpie looks up common names, names found in public certificate logs, and names referenced by other records.

DNS discovery cannot find every record. Compare the imported records with the complete list at your current provider, including uncommon and private names. Review any records the report says could not be copied. Add missing records or remove unwanted ones, then choose Confirm the records.

Copy the records again replaces imported records while keeping records you added or edited in Magpie. Review and confirm the new copy.

Only then change nameservers at your registrar to the exact pair shown on the domain's page. Remove the old nameservers. After this change, records missing from Magpie can stop your website, email, or subdomains working.

If DNSSEC is enabled, remove its DS configuration at the registrar before switching. Magpie does not yet sign hosted zones.

The zone remains waiting until the domain's registry delegates it to the assigned Magpie pair. Check again checks immediately. Creating a zone in Magpie does not mean its nameservers are active.

Add or change records

Choose Add record on the domain page. Select a type, enter its name and values, and save. Supported types are A, AAAA, CNAME, MX, TXT, CAA, SRV, and NS for delegated subdomains.

• @ means the domain itself. www means www.example.com, and * is a wildcard.
• A and AAAA need an IPv4 or IPv6 address.
• CNAME needs a target hostname. It cannot share a name with other records or be used for the domain itself.
• MX needs a priority and mail-server hostname. Multiple MX records are allowed.
• TXT accepts the text itself. Paste SPF or verification text without adding zone-file quotes. Spaces, quotes, and long strings are handled automatically.
• CAA has separate flags, tag, and value fields.
• SRV has separate priority, weight, port, and target fields. Use a service name such as _sip._tcp.
• NS hands a subdomain to other nameservers. Magpie manages the domain's own nameservers.

TTL is the time resolvers may cache the record. Automatic is 1 hour. Presets range from 5 minutes to 1 day; custom values range from 60 to 86400 seconds. Records with the same name and type share their shortest TTL.

Click a displayed manual name, value, or TTL to edit it in place; it saves immediately. Record details changes the type or several values together. Remove asks for confirmation. Search records by name or value, or filter by type and management.

Records managed by Magpie

Mail's required records are marked Managed by Mail. They cannot be edited or removed individually. Open Mail settings to change the service. An existing SPF record keeps its other entries while Mail adds its include. You can edit the original SPF text; Mail's include is added when it is published.

Enable Mail connects the same domain and needs the usual paid Mail plan. Magpie creates the required DNS records automatically. If the domain already receives mail elsewhere, its existing MX records remain until you create the mailboxes and choose Move mail to Magpie. Messages stored at the previous provider are not transferred.

Records created by another Magpie service show the service's name. Take manual control stops automatic management of that record and warns that the connected service may stop working. A service cannot replace a conflicting manual record without confirmation.

Check publication and history

Publication shows whether the latest zone has been accepted by Magpie's DNS backend. A failed or pending publication stays visible; Magpie retries automatically, and Check again retries now.

Check record compares its configured values with each assigned nameserver and a public resolver. These results are separate: a public resolver may still have an older cached answer after Magpie's nameservers have changed. The check does not prove that a website or mail server is working, or that every resolver has refreshed.

Change history lists record changes, their previous and new values, who changed them, imports, and hosting events.

Move away or remove a domain

Choose Download zone file before moving. It exports the configured records, including Mail's generated records. The destination provider creates its own SOA record.

Copy the records to the new provider and change nameservers at the registrar. Stop hosting DNS succeeds only after the registry lists no Magpie nameservers. The zone stays stored for export and recovery; Resume Magpie DNS reuses it and waits for delegation again.

Moving nameservers does not remove a domain from the team. Remove domain also removes its saved zone and history. A domain connected to Mail must be removed from Mail settings after its addresses are removed. Disconnect other Magpie services before removing their domain.

DNS does not buy or renew domains, redirect web addresses, or manage website certificates.

For help with nameservers, records, or publication, Contact support.