{
  "id": 20651761,
  "title": "DNS Change Audit Logs: 5 Custody Checks for Gaming Company Mail",
  "url": "https://urgent.news/2026/11/18/dns-change-audit-logs-5-custody-checks-for-gaming-company-mail",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-18T20:29:23.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/magnusnilsson2124/dns-change-audit-logs-5-custody-checks-for-gaming-company-mail-1i1c"
  },
  "original_language": "en",
  "account": "The article discusses the importance of auditing DNS changes for a gaming company migrating its mail system. It emphasizes the need to preserve the identity of the actor who requested the change and the zone it concerns, as this information alone does not reveal why the company switched mail providers or which approval allowed it. The audit event should bind the actor, zone, requested MX change, correlation identifier, approval reference, and timestamps as an application-owned event. Additionally, the article suggests keeping three kinds of evidence separate: application change events, scheduled zone listings, and cutover acceptance records. This separation allows for a more defensible acceptance decision. The article also highlights the importance of carrying the observed domain into the mail check, using DNS listings to extract the domain and then performing a mail-domain lookup. The Python code provided demonstrates how to perform these two reads using the same API key and base URL, without writing records or declaring propagation complete.",
  "summary": "A gaming company's mail migration needs DNS change auditing that preserves who changed each record in searchable logs. It also has two clocks: the moment an authorized engineer changes the MX records, and the point at which the team is ready to accept the cutover. A faster control-plane update doesn't, by itself, settle that second decision. TL;DR: Keep the record of who changed what in…",
  "key_points": [
    "Gaming company migrating mail system",
    "5 custody checks for DNS changes",
    "Separate evidence: application events, zone listings, cutover records"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}