DNS Sharing
Part of the MountDev Ops Workspace documentation. Updated November 19, 2026
MountDev Ops Workspace documentation | Updated November 19, 2026
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.
What DNS Sharing Is
When you add a domain, such as example.com, for a website, for sending email, or for a sign-in address, your provider needs access to that domain's DNS to set it up. You never copy or paste a DNS record, and you never share a password or an API token. You share access instead: one invite in Cloudflare, with the DNS role only. Your provider adds what is needed and checks it for you.
The Three Steps
- Put the domain on Cloudflare. The Free plan is enough. If the domain's DNS is somewhere else, the steps start here, with Cloudflare's own guide to adding a site. Cloudflare tells you the one change to make where you bought the domain.
- Invite your provider as a member. The address to invite is the address your provider shows you, with a Copy button. In Cloudflare, open Manage Account, then Members, choose Invite, paste the address, give it the DNS role only, and send it. You can limit it to this domain if your Cloudflare plan allows.
- We set it up. Your provider accepts the invite, adds what is needed, and checks it. The page updates by itself, so you can close it.
If your provider has not set up an address yet, the steps say to ask your provider for it. Nothing is guessed.
What You Can See and What You Cannot
You see where each domain stands: Move to Cloudflare, Waiting for invite, Setting up, or Done, with counts such as "2 of 3 found". You never see a DNS record's name or value, here or in any email, notice, or answer from the API or an AI agent. Staff of your provider see records only when troubleshooting.
Taking Access Away
You can remove the member in Cloudflare any time, under Manage Account, then Members. Nothing in your workspace depends on keeping the invite once the domain is set up.
For Owners and Admins
DNS Sharing (Operations, then Integrations, then My Connections, Cloudflare) holds the address your clients are told to invite: your own Cloudflare member address. Change it with Change (action core.dns.settings.save), and read it with action core.dns.settings.get. An empty value clears it, and clients are then told to ask you.
DNS Access lists every domain being set up, what it was added for (Website, Email, Sign-In, or Webhook), and where it stands. Add starts tracking a domain (action core.dns.access.add), Remove stops it and keeps the row (action core.dns.access.remove), and List shows each one (action core.dns.access.list).
Your workspace's AI agent can do all of these. None of them emails anyone, charges money, or shows a DNS record.
Checking by Itself
Once a domain is added for Email, we check it by ourselves, so you never need to press anything: every 2 minutes for the first hour, every 10 minutes for the next 24 hours, then every hour, until it is done or you remove it. The card updates the moment something changes, with no reload. If a check cannot run, it is tried again a little later, and one domain never holds up another. Check Now (action core.dns.access.check) asks for a check right away. It only queues it, the check runs within a minute, and each domain can be asked once a minute. Website, Sign-In, and Webhook domains are tracked and shown, and are checked by themselves as those parts arrive.
Notices
Telling a person when access arrives, and a reminder after 3 days, are planned and are off until MountDev finalizes its notification list. Nothing is sent for them today.
Connecting a Domain
Once your provider has accepted your invite, connect the domain so your provider can match it to your account. On Your Domains (Operations, then Integrations, then My Connections), choose Connect a Domain and enter two things:
- Cloudflare Account ID. The ID of the Cloudflare account that holds the domain: 32 letters and numbers, shown in the account overview in Cloudflare. It names the account. It is not a password.
- Domain. Like example.com.
Choose Connect (action core.dns.zone.claim). The entry shows Waiting for the Invite until your provider has accepted the invite, then Matched when Cloudflare shows that domain inside that account, or Not Found when it does not. Not Found never says which of the two is wrong: check the ID and the domain, and that your invite was sent. Your provider checks again by itself every 2 minutes at first, then less often, and you can close the page. Check Again asks right away.
A domain matches when three things are true, and your provider checks them again every time: your provider accepted the invite from that Cloudflare account, you entered that account ID and the domain, and Cloudflare shows the domain in that account. There is no first claim wins and no review step, so keep your Cloudflare account ID to people you trust: an account ID names an account, and anyone who knows it and a domain in it could enter both. What limits this is that the invite must have been accepted, that your provider can turn the feature off, and that everything is logged.
Release (action core.dns.zone.release) stops an entry at once. It is kept as released and comes back if you connect it again. List (action core.dns.zone.list) shows your entries. Connecting and releasing are for people with the permission Connect and release domains for DNS (core.dns.records.manage, owners and admins at first), and seeing the list needs See the domains your company connected for DNS (core.dns.records.view). An AI agent can list your entries. It cannot connect or release a domain.
Your provider sees each domain as a state and a count, such as "Matched, 8 records". It never sees your records, and your records are never kept in your provider's account. If your provider has not turned this on, Your Domains says "Your provider manages your DNS. Ask them for a change." and nothing is changed.
For Providers: Clients and DNS
Clients and DNS (Operations, then Integrations, then My Connections) has two switches, both off at first, and both for people only (action core.dns.settings.save, which an AI agent can use for the address but not for the switches):
- Let Clients Manage Their DNS (
dns_clients_manage). With it on, your clients can connect domains. Turning it off refuses every new request, says so to your clients, and removes nothing. - Accept DNS Invites Here. With it on, your Cloudflare connection accepts a pending invite when its role is DNS only (or DNS plus a read-only role), every few minutes. An invite with any other role stays pending in Cloudflare, and the card says how many wait. With it off, nothing is accepted here, so anything that accepts invites for you today keeps working until you choose.
Your Cloudflare token needs Zone Read and Memberships (read, and write to accept). Cloudflare calls the write level Edit in its dashboard and Write in its API. The card tells you when a permission is missing.
Matched Domains lists each client domain with the client's company name, its state, and a count. Only an accepted invite whose role is DNS only counts toward a match, so a wider membership of your own is never matched by a client. Your account holds the Cloudflare zone ID, the state, and counts, and never a record's name or value (action core.dns.settings.get).
Seeing and Changing Records Planned
The DNS Records page, where a client sees and changes the records of its own matched domains, with History, Undo, and Snapshots, is planned. It is described in the feature plan and is not built yet.
Planned
The same Share DNS Access card for Sign-In and Webhook addresses is planned (Part 4 of DNS Sharing Automation). It is described in the feature plan and is not built yet.
