Use PD BIND 9 DNS notifications to keep customers informed about host-made DNS changes and alert your team when background work needs attention. Notification settings do not repair a failed DNS action or prove that public answers changed.

Choose the customer events

1. Open BIND 9 DNS → Settings → Notifications.
2. Review Zone created, Zone records changed and Zone removed.
3. Enable only the notices your support process needs.
4. Confirm the intended zone owner and the platform’s configured mail transport.
5. Inspect the actual DNS action and its result separately from the email setting.

The documented customer notifications are off by default. Record-change notices describe host/team changes; edits customers make themselves do not trigger that same notification. A zone-removal notice does not by itself establish whether only management was removed or provider DNS was deleted.

Enable the appropriate team alert

Review Email your team when a background DNS task needs attention in Notifications. The documented workflow suppresses clean-run alerts and limits attention alerts per job per calendar day. Do not treat a lack of repeated mail as proof the original problem has been resolved.

Check Maintenance and Activity for the relevant last result and action time. A configured email option is separate from successful delivery through the billing platform’s mail transport.

Keep useful diagnostic evidence

For a missing notice, check whether the relevant event occurred, which actor made the change, the setting and intended owner. Retain a redacted event/mail result while your hosting team checks the event and delivery; do not enable unrelated email campaigns or export customer records for diagnosis. See the job troubleshooting guide for the underlying DNS action.

Check the notification settings and result

Your hosting team should compare the original event, actor, intended zone owner, saved notice setting and actual event/mail result. Check normal mail transport separately from the DNS action. For a team alert, review the task severity and whether a successful alert for that job has already been sent that calendar day; no repeated email is not proof of recovery. Do not enable unrelated mail or repeat DNS changes merely to trigger another notice.

See the PD BIND 9 DNS WHMCS guide for related tasks, or explore the module.