Host Muting: Silencing Alerts for a Record Type Without Stopping Monitoring

Acknowledging an alert is a one-time action for a one-time change. It stops working as a strategy the moment a record starts changing on a schedule you already expect, since every recurrence means acknowledging the same kind of change again. Muting exists for that repeat case: a specific record type on a specific host that you've decided isn't worth an alert, until you decide otherwise.

What muting actually does

Muting a record type on a host stops it from raising an alert or sending a notification. It doesn't stop the host from being checked, and it doesn't stop the change from being written to your DNS change history. A muted change still shows up exactly where an unmuted one would, it just arrives pre-acknowledged instead of waiting for you to review it.

Muting is scoped to one host, one record type at a time

Muting A records on one host has no effect on its AAAA or MX records, and no effect on any other host on the domain. There's no domain-wide mute and no "mute everything on this host" shortcut beyond selecting every record type it currently has. That granularity is the point: the record type that's actually noisy gets silenced, and everything else on the same host keeps alerting normally.

Indefinite vs a timed window

A mute can run indefinitely or for a fixed window of 1 hour, 24 hours, or 7 days. A timed mute lifts itself automatically once the window passes, no one has to remember to turn it back on, and the record starts alerting normally again the moment the window closes. An indefinite mute stays in place until someone removes it, which is the right choice for a record type you've permanently decided doesn't need alerting, rather than one you're temporarily working around.

When muting is the right tool

A record you're mid-migration on. A record can get adjusted more than once before a migration is actually done, whether that's correcting a value that didn't take effect cleanly or shifting traffic gradually rather than all at once. A short timed mute covers that window without leaving the record silenced once the migration is finished.

A record managed by an automated process you already trust. Some records are updated by scripts, deployment tooling, or a provider's own automation rather than by a person making a deliberate change. If that process is already trusted and its changes are already expected, an indefinite mute matches how the record actually behaves.

A record that's already flapping and you know why. Not every noisy record is a CDN rotating IPs, the built-in CDN filtering only covers that specific case. A record changing for some other known, benign reason is exactly what a manual mute is for.

What it isn't for

Muting isn't a way to stop monitoring something you no longer care about. The host keeps being checked on the same schedule either way, and every change still lands in the history, so muting has no effect on how much monitoring costs or how complete your record stays. It's specifically about which changes interrupt you, not which changes get tracked.

Setting it up

Muting is set from a host's menu on the domain page: choose which record types to mute and how long the mute should last. A host with an active mute shows a badge next to its name, and the same menu item becomes an edit option so the mute can be adjusted or cleared once it's no longer needed. A mute that's outlived its reason, the migration finished, the flapping stopped, is worth removing rather than leaving in place quietly hiding whatever happens next.