Yes, a connected AI assistant can change your DNS records, but it can never do it silently. You ask in plain language ("point mail.mydomain.com to this IP" or "add a TXT record for domain verification"), the assistant shows you the exact record it's about to add, edit, or delete, and it only makes the change after you approve it. Nothing happens on the first message. This works the same whether you're using Claude, ChatGPT, Gemini, Perplexity, or Cursor, since they all connect through the same DNS tool.
What the assistant can actually touch
The DNS tool in the connector operates on the same records you'd manage yourself in Services → your hosting → DNS Zone Editor. That means A, CNAME, MX, TXT, and similar zone records for domains hosted with us. It does not touch nameservers: those are edited separately under Domains → your domain → DNS, and the connector's DNS tool is scoped to zone records, not nameserver changes.
If you haven't connected an assistant yet, start with Connect an AI assistant to your Flashcloud account, which covers the shared setup and what reading versus action permissions mean. Assistant-specific steps exist for Gemini and Cursor; Claude, ChatGPT, and Perplexity follow the same pattern with their own settings screens.
Walking through a real change
Say you ask your assistant to add a TXT record so a third-party service can verify domain ownership. Here's what happens:
- You describe the record in plain language: the host, the type, and the value you were given.
- The assistant calls its DNS tool in a read-only way first if it needs to check what's already there, then proposes the specific change: record type, name, value, and TTL if relevant.
- You review the proposal. This is the point to catch a typo in the value or a wrong hostname, since the assistant is only as accurate as what you told it or what it read from the existing zone.
- You approve, and only then does the assistant apply the change.
- DNS changes still propagate on normal DNS timelines. The assistant applying the record doesn't skip propagation; it skips the manual trip through the portal.
The same flow applies to edits and deletions. Asking your assistant to "delete the old A record for staging.mydomain.com" produces a proposal showing which record it found and what it's about to remove, not an instant deletion.
Other things it can do in the same session
DNS is one of several tools available once you've connected an assistant and granted action permissions. The same connector can look up WHOIS details, list invoices, manage WordPress sites, create or reset a mailbox, and open a support ticket. For a broader tour of what's manageable outside the assistant too, see Getting around cPanel: the tools that matter. Each of these follows the same propose-then-confirm pattern as DNS: the assistant never acts without showing you the change first.
Checking or revoking access
Go to Goodies → AI Agents in the portal to see what each connected assistant is allowed to do, plus its connected and last-used dates. If you want to pull the plug on an assistant, disconnecting it there revokes its access.
Account-identity and billing actions like passwords, two-factor settings, and payments stay inside the portal no matter which assistant you've connected.
When to contact support
If a DNS record you added through an assistant isn't resolving the way you expect after normal propagation time, or you're not sure which record is causing a problem, open a ticket from Support in the portal. A real person will look at your zone directly.