{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/",
        "slug": "stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks",
        "url": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/"
        },
        "title": "Stage Forwarded DNS name resolution fails for dual-stacked queries with AD/DNS rollback checks",
        "summary": "Use Forwarded DNS name resolution fails for dual-stacked queries 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": "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:03+00:00",
        "modified_at": "2026-08-27T17:37:19+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 561,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Forwarded DNS name resolution fails for dual-stacked queries",
        "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": "Forwarded DNS name resolution fails for dual-stacked queries",
            "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/forwarded-dns-name-resolution-fails-for-dual-stacked-queries",
            "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>Frame this document as a source-led configuration and assurance check: Stage Forwarded DNS name resolution fails for dual-stacked queries with AD/DNS rollback checks. 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/forwarded-dns-name-resolution-fails-for-dual-stacked-queries\" target=\"_blank\" rel=\"noopener noreferrer\">Forwarded DNS name resolution fails for dual-stacked queries</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Symptoms, Microsoft states: “You&#8217;re using a third-party DNS server solution, and you can&#8217;t consistently resolve names when you use conditional forwarding.” The research record locates this support at <strong>Symptoms</strong>.</li>\n<li>At Symptoms, Microsoft states: “The local DNS server (10.100.100.70) can connect to the DNS server that&#8217;s configured as a conditional forwarder (10.133.3.250).” The research record locates this support at <strong>Symptoms</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>Symptoms</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Symptoms</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>If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>Build a reproducible chain from <strong>Symptoms</strong>; <strong>Symptoms</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-443</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/forwarded-dns-name-resolution-fails-for-dual-stacked-queries\" target=\"_blank\" rel=\"noopener noreferrer\">Forwarded DNS name resolution fails for dual-stacked queries</a> — Microsoft</li>\n</ul>",
        "content_text": "Frame this document as a source-led configuration and assurance check: Stage Forwarded DNS name resolution fails for dual-stacked queries with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Forwarded DNS name resolution fails for dual-stacked queries from Microsoft supports the following bounded statements:\n\nAt Symptoms, Microsoft states: “You’re using a third-party DNS server solution, and you can’t consistently resolve names when you use conditional forwarding.” The research record locates this support at Symptoms.\nAt Symptoms, Microsoft states: “The local DNS server (10.100.100.70) can connect to the DNS server that’s configured as a conditional forwarder (10.133.3.250).” The research record locates this support at Symptoms.\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 Symptoms, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Symptoms, 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.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators and sanitize protected material before retention.\nVerification and evidence\nBuild a reproducible chain from Symptoms; Symptoms 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-443 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nForwarded DNS name resolution fails for dual-stacked queries — Microsoft",
        "content_markdown": "Frame this document as a source-led configuration and assurance check: Stage Forwarded DNS name resolution fails for dual-stacked queries with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Forwarded DNS name resolution fails for dual-stacked queries](https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/forwarded-dns-name-resolution-fails-for-dual-stacked-queries) from Microsoft supports the following bounded statements:\n\n- At Symptoms, Microsoft states: “You’re using a third-party DNS server solution, and you can’t consistently resolve names when you use conditional forwarding.” The research record locates this support at Symptoms.\n\n- At Symptoms, Microsoft states: “The local DNS server (10.100.100.70) can connect to the DNS server that’s configured as a conditional forwarder (10.133.3.250).” The research record locates this support at Symptoms.\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 Symptoms, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Symptoms, 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\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators and sanitize protected material before retention.\n\n## Verification and evidence\n\nBuild a reproducible chain from Symptoms; Symptoms 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-443 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\n\n## Official references\n\n- [Forwarded DNS name resolution fails for dual-stacked queries](https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/forwarded-dns-name-resolution-fails-for-dual-stacked-queries) — 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/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/",
                "url": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Stage Forwarded DNS name resolution fails for dual-stacked queries with AD/DNS rollback checks",
                        "item": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/#article",
                "identifier": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/",
                "url": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/",
                "headline": "Stage Forwarded DNS name resolution fails for dual-stacked queries with AD/DNS rollback checks",
                "description": "Use Forwarded DNS name resolution fails for dual-stacked queries to review this narrow operational decision without extending the source beyond its…",
                "abstract": "Use Forwarded DNS name resolution fails for dual-stacked queries 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: Stage Forwarded DNS name resolution fails for dual-stacked queries with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Forwarded DNS name resolution fails for dual-stacked queries from Microsoft supports the following bounded statements:\n\nAt Symptoms, Microsoft states: “You’re using a third-party DNS server solution, and you can’t consistently resolve names when you use conditional forwarding.” The research record locates this support at Symptoms.\nAt Symptoms, Microsoft states: “The local DNS server (10.100.100.70) can connect to the DNS server that’s configured as a conditional forwarder (10.133.3.250).” The research record locates this support at Symptoms.\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 Symptoms, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Symptoms, 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.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, domain-controller health, time, routing, firewalls, certificates, and authorized operators and sanitize protected material before retention.\nVerification and evidence\nBuild a reproducible chain from Symptoms; Symptoms 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-443 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nForwarded DNS name resolution fails for dual-stacked queries — Microsoft",
                "datePublished": "2026-08-27T17:00:03+00:00",
                "dateModified": "2026-08-27T17:37:19+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/"
                },
                "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/stage-forwarded-dns-name-resolution-fails-for-dual-stacked-queries-with-ad-dns-rollback-checks/#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": "Stage Forwarded DNS name resolution fails for dual-stacked queries with AD/DNS rollback checks"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Explainer",
                    "Advisory priority"
                ],
                "genre": "Explainer",
                "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": 561,
                "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": "Forwarded DNS name resolution fails for dual-stacked queries",
                    "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/forwarded-dns-name-resolution-fails-for-dual-stacked-queries"
                }
            }
        ]
    }
}