Ask your connected AI assistant to check a domain's DNS records or nameservers with a plain-language question, for example "what are the DNS records for example.com?" or "what nameservers is example.com using?" and it reads your zone directly (once you've connected an AI assistant to your account). It can also look up domain and WHOIS details. Nothing changes until you say so.
What you can ask
The assistant has separate tools for DNS records and for domain/WHOIS lookups, so phrase your question around what you actually want to know:
- DNS records: "Show me the DNS records for example.com" or "Is there a TXT record for SPF on example.com?" This reads the zone the same way the portal's Services → your hosting → DNS Zone Editor would show it.
- Nameservers: "What nameservers is example.com pointed to?" Nameservers are a domain-level setting, separate from the records inside the zone, so this is a different question even though it sounds similar.
- WHOIS / registration details: "When does example.com expire?" or "Who's the registrar of record for example.com?" pulls public registration data, useful when you're troubleshooting a domain you don't fully remember the history of.
Because the assistant can see your actual account, it can also flag something like a missing MX record or a nameserver that doesn't match what you expect, without you having to open the portal first.
Records vs. nameservers: why the distinction matters
DNS records (A, CNAME, MX, TXT, and so on) live inside a zone and control where mail and traffic for a domain go. Nameservers are what tells the internet which zone to ask in the first place. In the Flashcloud portal, these are edited in two different places: DNS Zone Editor under your hosting service changes records, while the DNS section on the domain itself changes nameservers (up to five). Your AI assistant respects that same split. If you ask it to "fix the DNS," be specific about whether you mean a record inside the zone or the nameservers pointing at that zone, since the fix looks different depending on which one is wrong.
If you want the assistant to make a change
Editing records or nameservers requires action permissions for that assistant. If they're enabled, here's what happens when you ask for a change, for example "add a TXT record for domain verification" or "point example.com's nameservers back to Flashcloud":
- The assistant proposes the exact change before making it.
- It shows you that proposal and waits. Nothing is written yet.
- You confirm explicitly. Only then does the change go through.
This confirmation step happens every time, not just the first time. There's no setting that lets an assistant skip the review and apply DNS changes silently.
Checking what an assistant is allowed to do
If you're not sure whether a connected assistant currently has DNS edit permission, open your portal's Goodies → AI Agents page. It lists every connected assistant, exactly what it's allowed to read and change, and its status and connection dates. You can disconnect an assistant from there.
When to open a ticket instead
For most DNS lookups and simple record changes, asking your assistant is faster than logging into the portal. But if a domain's DNS is failing to resolve after a change, or nameservers were switched away from Flashcloud by a previous host, propagation delays can make it hard to tell what's actually live versus cached. If your assistant's read of the records doesn't match what you're seeing from outside, or you suspect a deeper issue than a single wrong record, open a support ticket from the portal (Support). Tickets go to real people, not a queue bot, and they can dig into propagation and server-side resolution in ways a DNS read can't.