Which DNS hosts does nofeb recognise, and what does each form expect?
Detected from the domain's nameservers. "Name box" is what the host wants in its host or name field; "apex" is what to type for the domain itself.
| DNS host | Nameservers | Published by API | Name box | Apex | Quote TXT | Dot on targets | MX priority |
|---|---|---|---|---|---|---|---|
| Cloudflare | cloudflare.com, foundationdns.* | yes | label only | @ | no | no | own field |
| Amazon Route 53 | awsdns-* | no | full name + dot | — | yes | no | in value |
| GoDaddy | domaincontrol.com | no | label only | @ | no | no | own field |
| Namecheap | registrar-servers.com | no | label only | @ | no | no | own field |
| Google Cloud DNS | googledomains.com | no | label only | empty | yes | yes | own field |
| DigitalOcean | digitalocean.com | yes | label only | @ | no | no | own field |
| Hetzner DNS | hetzner.com, hetzner.de, first-ns.de, second-ns.de, second-ns.com | yes | label only | @ | no | yes | own field |
| Vercel | vercel-dns.com | yes | label only | empty | no | no | own field |
| Porkbun | porkbun.com | yes | label only | empty | no | no | own field |
| Gandi | gandi.net | yes | label only | @ | no | yes | own field |
| IONOS | ui-dns.* | no | label only | @ | no | no | own field |
| OVHcloud | ovh.net, anycast.me | no | label only | empty | no | yes | own field |
| DNSimple | dnsimple.*, dnsimple-edge.* | no | label only | empty | no | no | own field |
| Azure DNS | azure-dns.* | no | label only | @ | no | no | own field |
| Netlify | netlify.com | no | label only | @ | no | no | own field |
| Squarespace | squarespacedns.com, domains.squarespace.com | no | label only | @ | no | no | own field |
| Wix | wixdns.net | no | label only | empty | no | no | own field |
| NS1 (or Netlify DNS) | nsone.net | no | label only | @ | no | no | own field |
| Akamai Edge DNS | akam.net, akamaiedge.net | no | full name + dot | — | yes | yes | own field |
| UltraDNS | ultradns.com, ultradns.net, ultradns.org, ultradns.biz | no | full name + dot | — | yes | yes | own field |
| Name.com | name.com | no | label only | @ | no | no | own field |
| Any other host | — | no | label only | @ | no | no | own field |
What are the records, and what is each one for?
| Record | Type | Name (most hosts) | Why |
|---|---|---|---|
| DKIM key 1 | CNAME | token1._domainkey | Signs your mail; all three DKIM CNAMEs must exist. |
| DKIM key 2 | CNAME | token2._domainkey | Second DKIM key. |
| DKIM key 3 | CNAME | token3._domainkey | Third DKIM key. |
| MAIL FROM MX | MX | bounce | Receives bounces for the MAIL FROM domain, so SPF aligns. Mail to your own addresses is unaffected. |
| MAIL FROM SPF | TXT | bounce | Authorises the sending servers for the MAIL FROM domain. |
| DMARC | TXT | _dmarc | Publishes a DMARC policy. An existing DMARC record counts as satisfied; keep yours. |
| Inbound MX (optional) | MX | @ | Only if nofeb should receive mail for the domain. It changes where the domain's mail is delivered. |
How do I get the records for my own domain?
POST https://api.nofeb.com/v1/domains
{ "name": "example.com" }
GET https://api.nofeb.com/v1/domains/{domain_id}/dns-setup
{ "provider_label": "…", "api": { "supported": true, … },
"instructions": [ … ], "exports": { "zone_file": "…", "route53_change_batch": { … }, "terraform": "…" },
"records": [ … ] } Agents can do the same through the get_dns_setup MCP tool.
Frequently asked questions
Which DNS records does nofeb need?
Three DKIM CNAMEs, an MX and an SPF TXT on the MAIL FROM subdomain (bounce), and a DMARC TXT. An MX at the domain itself is optional and only needed when nofeb should receive the domain's mail.
Which DNS hosts can nofeb publish records to automatically?
Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun, Gandi. You hand nofeb an API token for one call; it is never stored, and nofeb never deletes a record.
What if my DNS host is not listed?
Every host gets the same records. Most forms append the domain to the name you type and quote TXT values for you; the generic row in the table below covers them, and the zone-file, Route 53 and Terraform exports work anywhere.
How do I know the records are right?
nofeb looks every record up live and reports, per record, whether it passes, what it found and the likely mistake, such as a name with the domain appended twice. It emits domain.verified when all required records pass.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Custom domains | Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. | Shipped |
| DNS setup made easy | nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. | Shipped |
| One-click DNS with Domain Connect | At DNS hosts that support Domain Connect, a signed link where you sign in to your DNS host, review the records and click Connect. The engine builds and signs the link; it appears for a host only once that host has adopted nofeb's published template. | Beta |