{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/",
        "slug": "validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence",
        "url": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/"
        },
        "title": "Validate DNS Servers may fail to resolve queries for some top-level domains with AD/DNS evidence",
        "summary": "Use DNS Servers may fail to resolve queries for some top-level domains to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "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": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "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-27T17:00:04+00:00",
        "modified_at": "2026-08-27T17:37:19+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 602,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of DNS Servers may fail to resolve queries for some top-level domains",
        "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": "DNS Servers may fail to resolve queries for some top-level domains",
            "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dns-server-not-resolve-queries-for-top-level-domain",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "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>Treat this document as a focused evidence review: Validate DNS Servers may fail to resolve queries for some top-level domains with AD/DNS evidence. 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://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dns-server-not-resolve-queries-for-top-level-domain\" target=\"_blank\" rel=\"noopener noreferrer\">DNS Servers may fail to resolve queries for some top-level domains</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “This article provides a solution to an issue where Domain Name System (DNS) Servers may fail to resolve queries for names in certain top-level domains when name resolution is provided by root hints.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Symptom, Microsoft states: “When name resolution is provided by root hints, Windows Server 2008 DNS and Windows Server 2008 R2 DNS Servers may fail to resolve queries for names in certain top-level domains.” The research record locates this support at <strong>Symptom</strong>.</li>\n</ul>\n<p>The source support ends with the statements listed above. Use them to examine Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution in the applicable environment, not to imply a wider guarantee.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators before translating the source into an operational decision.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Symptom</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution, including exceptions?</li>\n<li>What baseline for Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators must accompany the source-specific observation?</li>\n<li>Which success, stop, and escalation criteria are written before testing begins?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution, 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 Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators. Handle credentials, keys, recovery data, and personal information through approved secure channels.</p>\n<h2>Verification and evidence</h2>\n<p>Build a reproducible chain from <strong>Introduction below H1</strong>; <strong>Symptom</strong> to the observed environment. Useful domain evidence includes sanitized query transcripts, DNS and network configuration, packet captures, event data, directory locator tests, and rollback records; label every item with scope, timestamp, collector, and stable identifier.</p>\n<p>Label this evidence set <strong>DSE-20260827-442</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</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://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dns-server-not-resolve-queries-for-top-level-domain\" target=\"_blank\" rel=\"noopener noreferrer\">DNS Servers may fail to resolve queries for some top-level domains</a> — Microsoft</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: Validate DNS Servers may fail to resolve queries for some top-level domains with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official DNS Servers may fail to resolve queries for some top-level domains from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides a solution to an issue where Domain Name System (DNS) Servers may fail to resolve queries for names in certain top-level domains when name resolution is provided by root hints.” The research record locates this support at Introduction below H1.\nAt Symptom, Microsoft states: “When name resolution is provided by root hints, Windows Server 2008 DNS and Windows Server 2008 R2 DNS Servers may fail to resolve queries for names in certain top-level domains.” The research record locates this support at Symptom.\n\nThe source support ends with the statements listed above. Use them to examine Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Symptom, which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution, including exceptions?\nWhat baseline for Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution, 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 Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nBuild a reproducible chain from Introduction below H1; Symptom to the observed environment. Useful domain evidence includes sanitized query transcripts, DNS and network configuration, packet captures, event data, directory locator tests, and rollback records; label every item with scope, timestamp, collector, and stable identifier.\nLabel this evidence set DSE-20260827-442 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\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\nDNS Servers may fail to resolve queries for some top-level domains — Microsoft",
        "content_markdown": "Treat this document as a focused evidence review: Validate DNS Servers may fail to resolve queries for some top-level domains with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [DNS Servers may fail to resolve queries for some top-level domains](https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dns-server-not-resolve-queries-for-top-level-domain) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “This article provides a solution to an issue where Domain Name System (DNS) Servers may fail to resolve queries for names in certain top-level domains when name resolution is provided by root hints.” The research record locates this support at Introduction below H1.\n\n- At Symptom, Microsoft states: “When name resolution is provided by root hints, Windows Server 2008 DNS and Windows Server 2008 R2 DNS Servers may fail to resolve queries for names in certain top-level domains.” The research record locates this support at Symptom.\n\nThe source support ends with the statements listed above. Use them to examine Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution in the applicable environment, not to imply a wider guarantee.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Symptom, which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution, including exceptions?\n\n- What baseline for Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators must accompany the source-specific observation?\n\n- Which success, stop, and escalation criteria are written before testing begins?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution, 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 Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nBuild a reproducible chain from Introduction below H1; Symptom to the observed environment. Useful domain evidence includes sanitized query transcripts, DNS and network configuration, packet captures, event data, directory locator tests, and rollback records; label every item with scope, timestamp, collector, and stable identifier.\n\nLabel this evidence set DSE-20260827-442 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\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- [DNS Servers may fail to resolve queries for some top-level domains](https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dns-server-not-resolve-queries-for-top-level-domain) — Microsoft"
    },
    "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-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/",
                "url": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Validate DNS Servers may fail to resolve queries for some top-level domains with AD/DNS evidence",
                        "item": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/#article",
                "identifier": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/",
                "url": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/",
                "headline": "Validate DNS Servers may fail to resolve queries for some top-level domains with AD/DNS evidence",
                "description": "Use DNS Servers may fail to resolve queries for some top-level domains to review this narrow operational decision without extending the source beyond…",
                "abstract": "Use DNS Servers may fail to resolve queries for some top-level domains to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Treat this document as a focused evidence review: Validate DNS Servers may fail to resolve queries for some top-level domains with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official DNS Servers may fail to resolve queries for some top-level domains from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides a solution to an issue where Domain Name System (DNS) Servers may fail to resolve queries for names in certain top-level domains when name resolution is provided by root hints.” The research record locates this support at Introduction below H1.\nAt Symptom, Microsoft states: “When name resolution is provided by root hints, Windows Server 2008 DNS and Windows Server 2008 R2 DNS Servers may fail to resolve queries for names in certain top-level domains.” The research record locates this support at Symptom.\n\nThe source support ends with the statements listed above. Use them to examine Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Symptom, which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution, including exceptions?\nWhat baseline for Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Windows DNS servers, clients, zones, records, policies, network interfaces, routes, and the Active Directory services that consume name resolution, 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 Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nBuild a reproducible chain from Introduction below H1; Symptom to the observed environment. Useful domain evidence includes sanitized query transcripts, DNS and network configuration, packet captures, event data, directory locator tests, and rollback records; label every item with scope, timestamp, collector, and stable identifier.\nLabel this evidence set DSE-20260827-442 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\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\nDNS Servers may fail to resolve queries for some top-level domains — Microsoft",
                "datePublished": "2026-08-27T17:00:04+00:00",
                "dateModified": "2026-08-27T17:37:19+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/validate-dns-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/"
                },
                "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-servers-may-fail-to-resolve-queries-for-some-top-level-domains-with-ad-dns-evidence/#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 Servers may fail to resolve queries for some top-level domains with AD/DNS evidence"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 602,
                "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": "DNS Servers may fail to resolve queries for some top-level domains",
                    "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dns-server-not-resolve-queries-for-top-level-domain"
                }
            }
        ]
    }
}