{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/",
        "slug": "validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions",
        "url": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/"
        },
        "title": "Validate DNS UPDATE prerequisites before applying zone additions or deletions",
        "summary": "Use RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE) to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T12:17:13+00:00",
        "modified_at": "2026-08-27T12:36:15+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 601,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE)",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE)",
            "url": "https://www.rfc-editor.org/rfc/rfc2136.html",
            "published_on": null,
            "authority": "www.rfc-editor.org"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Frame this document as a source-led configuration and assurance check: Validate DNS UPDATE prerequisites before applying zone additions or deletions. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://www.rfc-editor.org/rfc/rfc2136.html\" target=\"_blank\" rel=\"noopener noreferrer\">RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE)</a> from RFC Editor / Internet Engineering Task Force supports the following bounded statements:</p>\n<ul>\n<li>A primary processes the UPDATE prerequisite section against the zone&#8217;s current state before it applies any additions or deletions. The research record locates this support at <strong>Section 3.2 (Process Prerequisite Section)</strong>.</li>\n<li>Prerequisites can assert that a name or RRset exists, does not exist, or exactly equals a supplied RRset, with a defined failure response for each condition. The research record locates this support at <strong>Sections 3.2.1 through 3.2.4 (Prerequisite processing)</strong>.</li>\n<li>If a system failure occurs while applying the update section, the server returns SERVFAIL and rolls back every change from that transaction. The research record locates this support at <strong>Section 3.4.2.1 (Update processing)</strong>.</li>\n</ul>\n<p>These statements are the factual basis for this document. Do not extend them into a broader assurance. Review authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers only where the source and recorded environment align.</p>\n<h2>What the source does not establish</h2>\n<p>This RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state before translating the source into an operational decision.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Section 3.2 (Process Prerequisite Section)</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Sections 3.2.1 through 3.2.4 (Prerequisite processing)</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 3 at <strong>Section 3.4.2.1 (Update processing)</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Within authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?</li>\n<li>Could Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?</li>\n<li>Who owns the decision, and which observation requires stopping, escalation, or rollback?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.</p>\n<p>Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state. Handle credentials, keys, recovery data, and personal information through approved secure channels.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>Section 3.2 (Process Prerequisite Section)</strong>; <strong>Sections 3.2.1 through 3.2.4 (Prerequisite processing)</strong>; <strong>Section 3.4.2.1 (Update processing)</strong>. Favor zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior, linked to stable identifiers, time, and operator.</p>\n<p>Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.rfc-editor.org/rfc/rfc2136.html\" target=\"_blank\" rel=\"noopener noreferrer\">RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE)</a> — RFC Editor / Internet Engineering Task Force</li>\n</ul>",
        "content_text": "Frame this document as a source-led configuration and assurance check: Validate DNS UPDATE prerequisites before applying zone additions or deletions. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nA primary processes the UPDATE prerequisite section against the zone’s current state before it applies any additions or deletions. The research record locates this support at Section 3.2 (Process Prerequisite Section).\nPrerequisites can assert that a name or RRset exists, does not exist, or exactly equals a supplied RRset, with a defined failure response for each condition. The research record locates this support at Sections 3.2.1 through 3.2.4 (Prerequisite processing).\nIf a system failure occurs while applying the update section, the server returns SERVFAIL and rolls back every change from that transaction. The research record locates this support at Section 3.4.2.1 (Update processing).\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers only where the source and recorded environment align.\nWhat the source does not establish\nThis RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Section 3.2 (Process Prerequisite Section), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Sections 3.2.1 through 3.2.4 (Prerequisite processing), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 3.4.2.1 (Update processing), which observable configuration, record, or test can confirm applicability here?\nWithin authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?\nCould Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section 3.2 (Process Prerequisite Section); Sections 3.2.1 through 3.2.4 (Prerequisite processing); Section 3.4.2.1 (Update processing). Favor zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior, linked to stable identifiers, time, and operator.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nRFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE) — RFC Editor / Internet Engineering Task Force",
        "content_markdown": "Frame this document as a source-led configuration and assurance check: Validate DNS UPDATE prerequisites before applying zone additions or deletions. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE)](https://www.rfc-editor.org/rfc/rfc2136.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\n- A primary processes the UPDATE prerequisite section against the zone’s current state before it applies any additions or deletions. The research record locates this support at Section 3.2 (Process Prerequisite Section).\n\n- Prerequisites can assert that a name or RRset exists, does not exist, or exactly equals a supplied RRset, with a defined failure response for each condition. The research record locates this support at Sections 3.2.1 through 3.2.4 (Prerequisite processing).\n\n- If a system failure occurs while applying the update section, the server returns SERVFAIL and rolls back every change from that transaction. The research record locates this support at Section 3.4.2.1 (Update processing).\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers only where the source and recorded environment align.\n\n## What the source does not establish\n\nThis RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at Section 3.2 (Process Prerequisite Section), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Sections 3.2.1 through 3.2.4 (Prerequisite processing), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 3 at Section 3.4.2.1 (Update processing), which observable configuration, record, or test can confirm applicability here?\n\n- Within authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?\n\n- Could Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?\n\n- Who owns the decision, and which observation requires stopping, escalation, or rollback?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.\n\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section 3.2 (Process Prerequisite Section); Sections 3.2.1 through 3.2.4 (Prerequisite processing); Section 3.4.2.1 (Update processing). Favor zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior, linked to stable identifiers, time, and operator.\n\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\n\n## Official references\n\n- [RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE)](https://www.rfc-editor.org/rfc/rfc2136.html) — RFC Editor / Internet Engineering Task Force"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/",
                "url": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Validate DNS UPDATE prerequisites before applying zone additions or deletions",
                        "item": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/#article",
                "identifier": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/",
                "url": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/",
                "headline": "Validate DNS UPDATE prerequisites before applying zone additions or deletions",
                "description": "Use RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE) to review this narrow operational decision without extending the source beyond…",
                "abstract": "Use RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE) to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Frame this document as a source-led configuration and assurance check: Validate DNS UPDATE prerequisites before applying zone additions or deletions. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nA primary processes the UPDATE prerequisite section against the zone’s current state before it applies any additions or deletions. The research record locates this support at Section 3.2 (Process Prerequisite Section).\nPrerequisites can assert that a name or RRset exists, does not exist, or exactly equals a supplied RRset, with a defined failure response for each condition. The research record locates this support at Sections 3.2.1 through 3.2.4 (Prerequisite processing).\nIf a system failure occurs while applying the update section, the server returns SERVFAIL and rolls back every change from that transaction. The research record locates this support at Section 3.4.2.1 (Update processing).\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers only where the source and recorded environment align.\nWhat the source does not establish\nThis RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Section 3.2 (Process Prerequisite Section), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Sections 3.2.1 through 3.2.4 (Prerequisite processing), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 3.4.2.1 (Update processing), which observable configuration, record, or test can confirm applicability here?\nWithin authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?\nCould Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section 3.2 (Process Prerequisite Section); Sections 3.2.1 through 3.2.4 (Prerequisite processing); Section 3.4.2.1 (Update processing). Favor zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior, linked to stable identifiers, time, and operator.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nRFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE) — RFC Editor / Internet Engineering Task Force",
                "datePublished": "2026-08-27T12:17:13+00:00",
                "dateModified": "2026-08-27T12:36:15+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/validate-dns-update-prerequisites-before-applying-zone-additions-or-deletions/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Validate DNS UPDATE prerequisites before applying zone additions or deletions"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Networks & Infrastructure",
                    "Explainer",
                    "Advisory priority"
                ],
                "genre": "Explainer",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 601,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "RFC 2136 — Dynamic Updates in the Domain Name System (DNS UPDATE)",
                    "url": "https://www.rfc-editor.org/rfc/rfc2136.html"
                }
            }
        ]
    }
}