Open Websites & Apps, click into the site, and select the DNS tab. You'll see the full DNS zone for that domain right there, with a callout above the record table pointing at the A record, since that's the one people come here to change (usually to point the domain at a different IP after a migration or a new server).
This is the same zone data as the classic Zone Editor, just scoped to one domain and surfaced inside the per-site view instead of a standalone tool. If you'd rather work in the full editor with every domain on the account in one place, that's still available too.
Finding the DNS tab
From the Meridian dashboard sidebar, click Websites & Apps. Each site on the account has its own row with tabs across the top: Overview, SSL, Email, DNS, Files, Backups, Alias, Settings. Click DNS to load that domain's zone.
The table lists every record with its type, name, and value, the same fields you'd see anywhere DNS is edited. Add a record, edit an existing value, or delete one directly from this table.
The A record hint
Above the record table, Meridian highlights the A record for the domain's root (@) with a short note explaining what it controls: the IP address your domain resolves to. This is the record most people are actually looking for when they land on this tab, whether they're pointing the domain at a new server after a migration or fixing a site that stopped resolving.
If you're changing hosts entirely and moving a domain's nameservers, that's a different control. Nameservers are set from the domain's page under Domains, not from this per-site DNS tab.
Editing other record types
The same tab handles CNAME, MX, TXT, and any other record type in the zone, not just the A record. A few things worth knowing before you touch anything other than the A record:
- MX records are already set correctly if you're using hosting email on this account. If you've moved mail to Google Workspace or another provider, you'll replace the MX records here with theirs.
- TXT records carry SPF, DKIM, DMARC, and domain-ownership verification strings. Editing or removing one by mistake is a common way mail delivery breaks silently.
For a full rundown of what each record type does and when you'd touch it, see DNS records and how to manage them. If you're troubleshooting mail specifically after a DNS change, checking SPF and DKIM with the Email Deliverability tool will tell you fast whether something drifted.
Propagation and what to expect after saving
Changes save on our nameservers once submitted. Visitors may still see the old value for a while if their ISP or browser cached the previous record under a longer TTL. If you're about to make a change you know is coming, lowering the TTL a day ahead of time shortens that window.
If a new site isn't resolving right after adding an A record, give it some time before assuming something's wrong. If it's still not working after a while, double check the value against what your host or app actually expects, and confirm the domain is really using our nameservers, not a third-party DNS provider.
Managing multiple sites on one account
If this hosting account runs more than one website, whether as separate addon domains, aliases, or subdomains, each one gets its own row in Websites & Apps and its own DNS tab. See addon domains, aliases, and subdomains if you're not sure which setup fits what you're trying to do, since the DNS you need to touch differs depending on which type you pick.
When to contact support
DNS mistakes are usually recoverable, but if you're not confident about a record you're about to change, especially MX or TXT records tied to email, open a ticket first. Support is available through the portal under Support, plus live chat, and it's real people on the other end, not a bot. That's the safer move before editing anything you can't easily reverse from memory.