Implement DnsResolver for Windows - #129302

Closed
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver
Closed

Implement DnsResolver for Windows#129302
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver

Conversation

@rzikm

Copy link
Copy Markdown
Member

Implements the API approved in #19443:

  • New Dns.Resolve*[Async] static methods for A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
  • New DnsResolver / DnsResolverOptions for instance-based resolution with optional custom DNS servers.
  • Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord, PtrRecord, NsRecord.
  • DnsResponseCode enum and DnsResult envelope carrying ResponseCode, Records, and NegativeCacheTtl.

Windows implementation uses DnsQueryEx. Non-Windows platforms get PlatformNotSupportedException stubs pending follow-up implementations (splitting to multiple stacked PRs for easier review).

CopilotAI review requested due to automatic review settings June 11, 2026 16:57
@rzikm
rzikm requested a review from a teamJune 11, 2026 16:58
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new DNS query API surface area to System.Net.NameResolution (new Dns.Resolve* static entry points plus an instance-based DnsResolver), and implements the Windows PAL using DnsQueryEx. It also introduces functional tests, including deterministic loopback-server-driven tests for record parsing/handling.

Changes:

  • Adds new public APIs: Dns.Resolve* (A/AAAA/SRV/MX/TXT/CNAME/PTR/NS), DnsResolver, DnsResolverOptions, record structs, DnsResult<T>, and DnsResponseCode.
  • Implements Windows DNS querying/parsing via DnsQueryEx (sync + async paths), plus non-Windows PNSE stubs.
  • Adds functional tests (outer-loop network tests + loopback DNS server tests) and extends NameResolution telemetry to handle string[] answers.

Reviewed changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 18 comments.

Show a summary per file
FileDescription
src/libraries/System.Net.NameResolution/tests/FunctionalTests/System.Net.NameResolution.Functional.Tests.csprojAdds new functional test sources to the project
src/libraries/System.Net.NameResolution/tests/FunctionalTests/LoopbackDnsServer.csAdds an in-process UDP/TCP loopback DNS server for deterministic tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResponseBuilder.csAdds a fluent builder for DNS response bytes used by loopback tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverTest.csAdds outer-loop functional tests for the new APIs (real DNS)
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverLoopbackTest.csAdds deterministic loopback-server-driven tests for parsing/behavior/metrics
src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.csExtends telemetry answer handling to support string[]
src/libraries/System.Net.NameResolution/src/System/Net/DnsResult.csIntroduces DnsResult<T> envelope type
src/libraries/System.Net.NameResolution/src/System/Net/DnsResponseCode.csIntroduces DnsResponseCode enum
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Windows.csImplements Windows PAL via DnsQueryEx, record parsing, cancellation, glue, TTL extraction
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Unsupported.csAdds non-Windows PNSE PAL stubs
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverOptions.csAdds options type for custom server selection
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.csAdds instance-based resolver API + telemetry wrapping
src/libraries/System.Net.NameResolution/src/System/Net/DnsRecords.csAdds record structs (Address/Srv/Mx/Txt/CName/Ptr/Ns)
src/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.csAdds new static Dns.Resolve* APIs backed by a default resolver
src/libraries/System.Net.NameResolution/src/System/Net/Dns.csMakes Dns partial to host the new Dns.Resolve* partial
src/libraries/System.Net.NameResolution/src/System.Net.NameResolution.csprojWires new sources and Windows Dnsapi interop into the build
src/libraries/System.Net.NameResolution/src/Resources/Strings.resxAdds SR string for unsupported custom DNS ports
src/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.csAdds new public API contract entries
src/libraries/Common/src/Interop/Windows/Interop.Libraries.csAdds Libraries.Dnsapi constant
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.csAdds DnsQueryEx/DNS_RECORD-related structs/constants
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.csAdds LibraryImport declarations for DnsQueryEx/DnsCancelQuery/DnsFree

Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated
Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

@MihaZupanMihaZupan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass through.

Just curious, will there be a way to opt-in to using the managed implementation even on Windows, or would there be no reason to want to do that anyway?

Comment on lines +75 to +82
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name) { throw null; }
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name, System.Net.Sockets.AddressFamily addressFamily) { throw null; }
public System.Net.DnsResult<System.Net.SrvRecord> ResolveSrv(string name) { throw null; }
public System.Net.DnsResult<System.Net.MxRecord> ResolveMx(string name) { throw null; }
public System.Net.DnsResult<System.Net.TxtRecord> ResolveTxt(string name) { throw null; }
public System.Net.DnsResult<System.Net.CNameRecord> ResolveCName(string name) { throw null; }
public System.Net.DnsResult<System.Net.PtrRecord> ResolvePtr(string name) { throw null; }
public System.Net.DnsResult<System.Net.NsRecord> ResolveNs(string name) { throw null; }

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname,System.Net.Sockets.AddressFamilyaddressFamily){thrownull;}
publicSystem.Net.DnsResult<System.Net.SrvRecord>ResolveSrv(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.MxRecord>ResolveMx(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.TxtRecord>ResolveTxt(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.CNameRecord>ResolveCName(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.PtrRecord>ResolvePtr(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.NsRecord>ResolveNs(stringname){thrownull;}

I think we should talk about this with the team :)

My stance continues to be that exposing sync APIs here is a mistake, especially if we have real plans to eventually add support for resolution over HTTPS/QUIC.
The fact that e.g. Resolve silently has 2x the latency compared to the async variant makes the argument that we need sync APIs for perf wrong IMO.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am also not entirely happy with having synchronous versions as well, we can bring it in a team discussion and push back if more of us feel strongly about this :)

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 4 comments.

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
@MichalPetryka

MichalPetryka commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

I've worked with DNS apis here before so here's what I wanted to note:

  • This needs to account for this pre Windows 11 bug and fallback to DnsQueryW for affected cases (it's only when DnsQueryEx would return synchronously).
  • IIRC DnsQueryEx is also broken under impersonization, so this needs identical handling like the GetAddrInfoW handling today has.

CopilotAI review requested due to automatic review settings June 18, 2026 11:38

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 6 comments.

Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.cs Outdated
Comment on lines +48 to +54
[OuterLoop("Binds the loopback DNS port 53 and issues real DnsQueryEx calls.")]
[Collection(nameof(DisableParallelization))]
[PlatformSpecific(TestPlatforms.Windows)]
public class DnsResolverLoopbackTest : IClassFixture<WindowsLoopbackServer>
{
private static DnsResolver CreateResolver(LoopbackDnsServer server)
=> new DnsResolver(new DnsResolverOptions { Servers = { server.EndPoint } });
Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

rzikm added a commit that referenced this pull request Jul 8, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
eiriktsarpalis pushed a commit that referenced this pull request Jul 15, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@github-actionsgithub-actionsBot locked and limited conversation to collaborators Jul 26, 2026
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@rzikm@MichalPetryka@MihaZupan
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Implement DnsResolver for Windows - #129302

Closed
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver
Closed

Implement DnsResolver for Windows#129302
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver

Conversation

@rzikm

Copy link
Copy Markdown
Member

Implements the API approved in #19443:

  • New Dns.Resolve*[Async] static methods for A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
  • New DnsResolver / DnsResolverOptions for instance-based resolution with optional custom DNS servers.
  • Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord, PtrRecord, NsRecord.
  • DnsResponseCode enum and DnsResult envelope carrying ResponseCode, Records, and NegativeCacheTtl.

Windows implementation uses DnsQueryEx. Non-Windows platforms get PlatformNotSupportedException stubs pending follow-up implementations (splitting to multiple stacked PRs for easier review).

CopilotAI review requested due to automatic review settings June 11, 2026 16:57
@rzikm
rzikm requested a review from a teamJune 11, 2026 16:58
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new DNS query API surface area to System.Net.NameResolution (new Dns.Resolve* static entry points plus an instance-based DnsResolver), and implements the Windows PAL using DnsQueryEx. It also introduces functional tests, including deterministic loopback-server-driven tests for record parsing/handling.

Changes:

  • Adds new public APIs: Dns.Resolve* (A/AAAA/SRV/MX/TXT/CNAME/PTR/NS), DnsResolver, DnsResolverOptions, record structs, DnsResult<T>, and DnsResponseCode.
  • Implements Windows DNS querying/parsing via DnsQueryEx (sync + async paths), plus non-Windows PNSE stubs.
  • Adds functional tests (outer-loop network tests + loopback DNS server tests) and extends NameResolution telemetry to handle string[] answers.

Reviewed changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 18 comments.

Show a summary per file
FileDescription
src/libraries/System.Net.NameResolution/tests/FunctionalTests/System.Net.NameResolution.Functional.Tests.csprojAdds new functional test sources to the project
src/libraries/System.Net.NameResolution/tests/FunctionalTests/LoopbackDnsServer.csAdds an in-process UDP/TCP loopback DNS server for deterministic tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResponseBuilder.csAdds a fluent builder for DNS response bytes used by loopback tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverTest.csAdds outer-loop functional tests for the new APIs (real DNS)
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverLoopbackTest.csAdds deterministic loopback-server-driven tests for parsing/behavior/metrics
src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.csExtends telemetry answer handling to support string[]
src/libraries/System.Net.NameResolution/src/System/Net/DnsResult.csIntroduces DnsResult<T> envelope type
src/libraries/System.Net.NameResolution/src/System/Net/DnsResponseCode.csIntroduces DnsResponseCode enum
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Windows.csImplements Windows PAL via DnsQueryEx, record parsing, cancellation, glue, TTL extraction
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Unsupported.csAdds non-Windows PNSE PAL stubs
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverOptions.csAdds options type for custom server selection
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.csAdds instance-based resolver API + telemetry wrapping
src/libraries/System.Net.NameResolution/src/System/Net/DnsRecords.csAdds record structs (Address/Srv/Mx/Txt/CName/Ptr/Ns)
src/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.csAdds new static Dns.Resolve* APIs backed by a default resolver
src/libraries/System.Net.NameResolution/src/System/Net/Dns.csMakes Dns partial to host the new Dns.Resolve* partial
src/libraries/System.Net.NameResolution/src/System.Net.NameResolution.csprojWires new sources and Windows Dnsapi interop into the build
src/libraries/System.Net.NameResolution/src/Resources/Strings.resxAdds SR string for unsupported custom DNS ports
src/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.csAdds new public API contract entries
src/libraries/Common/src/Interop/Windows/Interop.Libraries.csAdds Libraries.Dnsapi constant
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.csAdds DnsQueryEx/DNS_RECORD-related structs/constants
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.csAdds LibraryImport declarations for DnsQueryEx/DnsCancelQuery/DnsFree

Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated
Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

@MihaZupanMihaZupan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass through.

Just curious, will there be a way to opt-in to using the managed implementation even on Windows, or would there be no reason to want to do that anyway?

Comment on lines +75 to +82
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name) { throw null; }
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name, System.Net.Sockets.AddressFamily addressFamily) { throw null; }
public System.Net.DnsResult<System.Net.SrvRecord> ResolveSrv(string name) { throw null; }
public System.Net.DnsResult<System.Net.MxRecord> ResolveMx(string name) { throw null; }
public System.Net.DnsResult<System.Net.TxtRecord> ResolveTxt(string name) { throw null; }
public System.Net.DnsResult<System.Net.CNameRecord> ResolveCName(string name) { throw null; }
public System.Net.DnsResult<System.Net.PtrRecord> ResolvePtr(string name) { throw null; }
public System.Net.DnsResult<System.Net.NsRecord> ResolveNs(string name) { throw null; }

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname,System.Net.Sockets.AddressFamilyaddressFamily){thrownull;}
publicSystem.Net.DnsResult<System.Net.SrvRecord>ResolveSrv(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.MxRecord>ResolveMx(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.TxtRecord>ResolveTxt(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.CNameRecord>ResolveCName(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.PtrRecord>ResolvePtr(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.NsRecord>ResolveNs(stringname){thrownull;}

I think we should talk about this with the team :)

My stance continues to be that exposing sync APIs here is a mistake, especially if we have real plans to eventually add support for resolution over HTTPS/QUIC.
The fact that e.g. Resolve silently has 2x the latency compared to the async variant makes the argument that we need sync APIs for perf wrong IMO.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am also not entirely happy with having synchronous versions as well, we can bring it in a team discussion and push back if more of us feel strongly about this :)

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 4 comments.

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
@MichalPetryka

MichalPetryka commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

I've worked with DNS apis here before so here's what I wanted to note:

  • This needs to account for this pre Windows 11 bug and fallback to DnsQueryW for affected cases (it's only when DnsQueryEx would return synchronously).
  • IIRC DnsQueryEx is also broken under impersonization, so this needs identical handling like the GetAddrInfoW handling today has.

CopilotAI review requested due to automatic review settings June 18, 2026 11:38

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 6 comments.

Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.cs Outdated
Comment on lines +48 to +54
[OuterLoop("Binds the loopback DNS port 53 and issues real DnsQueryEx calls.")]
[Collection(nameof(DisableParallelization))]
[PlatformSpecific(TestPlatforms.Windows)]
public class DnsResolverLoopbackTest : IClassFixture<WindowsLoopbackServer>
{
private static DnsResolver CreateResolver(LoopbackDnsServer server)
=> new DnsResolver(new DnsResolverOptions { Servers = { server.EndPoint } });
Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

rzikm added a commit that referenced this pull request Jul 8, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
eiriktsarpalis pushed a commit that referenced this pull request Jul 15, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@github-actionsgithub-actionsBot locked and limited conversation to collaborators Jul 26, 2026
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@rzikm@MichalPetryka@MihaZupan
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Implement DnsResolver for Windows - #129302

Closed
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver
Closed

Implement DnsResolver for Windows#129302
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver

Conversation

@rzikm

Copy link
Copy Markdown
Member

Implements the API approved in #19443:

  • New Dns.Resolve*[Async] static methods for A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
  • New DnsResolver / DnsResolverOptions for instance-based resolution with optional custom DNS servers.
  • Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord, PtrRecord, NsRecord.
  • DnsResponseCode enum and DnsResult envelope carrying ResponseCode, Records, and NegativeCacheTtl.

Windows implementation uses DnsQueryEx. Non-Windows platforms get PlatformNotSupportedException stubs pending follow-up implementations (splitting to multiple stacked PRs for easier review).

CopilotAI review requested due to automatic review settings June 11, 2026 16:57
@rzikm
rzikm requested a review from a teamJune 11, 2026 16:58
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new DNS query API surface area to System.Net.NameResolution (new Dns.Resolve* static entry points plus an instance-based DnsResolver), and implements the Windows PAL using DnsQueryEx. It also introduces functional tests, including deterministic loopback-server-driven tests for record parsing/handling.

Changes:

  • Adds new public APIs: Dns.Resolve* (A/AAAA/SRV/MX/TXT/CNAME/PTR/NS), DnsResolver, DnsResolverOptions, record structs, DnsResult<T>, and DnsResponseCode.
  • Implements Windows DNS querying/parsing via DnsQueryEx (sync + async paths), plus non-Windows PNSE stubs.
  • Adds functional tests (outer-loop network tests + loopback DNS server tests) and extends NameResolution telemetry to handle string[] answers.

Reviewed changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 18 comments.

Show a summary per file
FileDescription
src/libraries/System.Net.NameResolution/tests/FunctionalTests/System.Net.NameResolution.Functional.Tests.csprojAdds new functional test sources to the project
src/libraries/System.Net.NameResolution/tests/FunctionalTests/LoopbackDnsServer.csAdds an in-process UDP/TCP loopback DNS server for deterministic tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResponseBuilder.csAdds a fluent builder for DNS response bytes used by loopback tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverTest.csAdds outer-loop functional tests for the new APIs (real DNS)
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverLoopbackTest.csAdds deterministic loopback-server-driven tests for parsing/behavior/metrics
src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.csExtends telemetry answer handling to support string[]
src/libraries/System.Net.NameResolution/src/System/Net/DnsResult.csIntroduces DnsResult<T> envelope type
src/libraries/System.Net.NameResolution/src/System/Net/DnsResponseCode.csIntroduces DnsResponseCode enum
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Windows.csImplements Windows PAL via DnsQueryEx, record parsing, cancellation, glue, TTL extraction
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Unsupported.csAdds non-Windows PNSE PAL stubs
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverOptions.csAdds options type for custom server selection
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.csAdds instance-based resolver API + telemetry wrapping
src/libraries/System.Net.NameResolution/src/System/Net/DnsRecords.csAdds record structs (Address/Srv/Mx/Txt/CName/Ptr/Ns)
src/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.csAdds new static Dns.Resolve* APIs backed by a default resolver
src/libraries/System.Net.NameResolution/src/System/Net/Dns.csMakes Dns partial to host the new Dns.Resolve* partial
src/libraries/System.Net.NameResolution/src/System.Net.NameResolution.csprojWires new sources and Windows Dnsapi interop into the build
src/libraries/System.Net.NameResolution/src/Resources/Strings.resxAdds SR string for unsupported custom DNS ports
src/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.csAdds new public API contract entries
src/libraries/Common/src/Interop/Windows/Interop.Libraries.csAdds Libraries.Dnsapi constant
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.csAdds DnsQueryEx/DNS_RECORD-related structs/constants
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.csAdds LibraryImport declarations for DnsQueryEx/DnsCancelQuery/DnsFree

Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated
Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

@MihaZupanMihaZupan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass through.

Just curious, will there be a way to opt-in to using the managed implementation even on Windows, or would there be no reason to want to do that anyway?

Comment on lines +75 to +82
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name) { throw null; }
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name, System.Net.Sockets.AddressFamily addressFamily) { throw null; }
public System.Net.DnsResult<System.Net.SrvRecord> ResolveSrv(string name) { throw null; }
public System.Net.DnsResult<System.Net.MxRecord> ResolveMx(string name) { throw null; }
public System.Net.DnsResult<System.Net.TxtRecord> ResolveTxt(string name) { throw null; }
public System.Net.DnsResult<System.Net.CNameRecord> ResolveCName(string name) { throw null; }
public System.Net.DnsResult<System.Net.PtrRecord> ResolvePtr(string name) { throw null; }
public System.Net.DnsResult<System.Net.NsRecord> ResolveNs(string name) { throw null; }

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname,System.Net.Sockets.AddressFamilyaddressFamily){thrownull;}
publicSystem.Net.DnsResult<System.Net.SrvRecord>ResolveSrv(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.MxRecord>ResolveMx(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.TxtRecord>ResolveTxt(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.CNameRecord>ResolveCName(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.PtrRecord>ResolvePtr(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.NsRecord>ResolveNs(stringname){thrownull;}

I think we should talk about this with the team :)

My stance continues to be that exposing sync APIs here is a mistake, especially if we have real plans to eventually add support for resolution over HTTPS/QUIC.
The fact that e.g. Resolve silently has 2x the latency compared to the async variant makes the argument that we need sync APIs for perf wrong IMO.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am also not entirely happy with having synchronous versions as well, we can bring it in a team discussion and push back if more of us feel strongly about this :)

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 4 comments.

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
@MichalPetryka

MichalPetryka commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

I've worked with DNS apis here before so here's what I wanted to note:

  • This needs to account for this pre Windows 11 bug and fallback to DnsQueryW for affected cases (it's only when DnsQueryEx would return synchronously).
  • IIRC DnsQueryEx is also broken under impersonization, so this needs identical handling like the GetAddrInfoW handling today has.

CopilotAI review requested due to automatic review settings June 18, 2026 11:38

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 6 comments.

Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.cs Outdated
Comment on lines +48 to +54
[OuterLoop("Binds the loopback DNS port 53 and issues real DnsQueryEx calls.")]
[Collection(nameof(DisableParallelization))]
[PlatformSpecific(TestPlatforms.Windows)]
public class DnsResolverLoopbackTest : IClassFixture<WindowsLoopbackServer>
{
private static DnsResolver CreateResolver(LoopbackDnsServer server)
=> new DnsResolver(new DnsResolverOptions { Servers = { server.EndPoint } });
Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

rzikm added a commit that referenced this pull request Jul 8, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
eiriktsarpalis pushed a commit that referenced this pull request Jul 15, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@github-actionsgithub-actionsBot locked and limited conversation to collaborators Jul 26, 2026
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@rzikm@MichalPetryka@MihaZupan
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Implement DnsResolver for Windows - #129302

Closed
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver
Closed

Implement DnsResolver for Windows#129302
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver

Conversation

@rzikm

Copy link
Copy Markdown
Member

Implements the API approved in #19443:

  • New Dns.Resolve*[Async] static methods for A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
  • New DnsResolver / DnsResolverOptions for instance-based resolution with optional custom DNS servers.
  • Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord, PtrRecord, NsRecord.
  • DnsResponseCode enum and DnsResult envelope carrying ResponseCode, Records, and NegativeCacheTtl.

Windows implementation uses DnsQueryEx. Non-Windows platforms get PlatformNotSupportedException stubs pending follow-up implementations (splitting to multiple stacked PRs for easier review).

CopilotAI review requested due to automatic review settings June 11, 2026 16:57
@rzikm
rzikm requested a review from a teamJune 11, 2026 16:58
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new DNS query API surface area to System.Net.NameResolution (new Dns.Resolve* static entry points plus an instance-based DnsResolver), and implements the Windows PAL using DnsQueryEx. It also introduces functional tests, including deterministic loopback-server-driven tests for record parsing/handling.

Changes:

  • Adds new public APIs: Dns.Resolve* (A/AAAA/SRV/MX/TXT/CNAME/PTR/NS), DnsResolver, DnsResolverOptions, record structs, DnsResult<T>, and DnsResponseCode.
  • Implements Windows DNS querying/parsing via DnsQueryEx (sync + async paths), plus non-Windows PNSE stubs.
  • Adds functional tests (outer-loop network tests + loopback DNS server tests) and extends NameResolution telemetry to handle string[] answers.

Reviewed changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 18 comments.

Show a summary per file
FileDescription
src/libraries/System.Net.NameResolution/tests/FunctionalTests/System.Net.NameResolution.Functional.Tests.csprojAdds new functional test sources to the project
src/libraries/System.Net.NameResolution/tests/FunctionalTests/LoopbackDnsServer.csAdds an in-process UDP/TCP loopback DNS server for deterministic tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResponseBuilder.csAdds a fluent builder for DNS response bytes used by loopback tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverTest.csAdds outer-loop functional tests for the new APIs (real DNS)
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverLoopbackTest.csAdds deterministic loopback-server-driven tests for parsing/behavior/metrics
src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.csExtends telemetry answer handling to support string[]
src/libraries/System.Net.NameResolution/src/System/Net/DnsResult.csIntroduces DnsResult<T> envelope type
src/libraries/System.Net.NameResolution/src/System/Net/DnsResponseCode.csIntroduces DnsResponseCode enum
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Windows.csImplements Windows PAL via DnsQueryEx, record parsing, cancellation, glue, TTL extraction
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Unsupported.csAdds non-Windows PNSE PAL stubs
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverOptions.csAdds options type for custom server selection
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.csAdds instance-based resolver API + telemetry wrapping
src/libraries/System.Net.NameResolution/src/System/Net/DnsRecords.csAdds record structs (Address/Srv/Mx/Txt/CName/Ptr/Ns)
src/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.csAdds new static Dns.Resolve* APIs backed by a default resolver
src/libraries/System.Net.NameResolution/src/System/Net/Dns.csMakes Dns partial to host the new Dns.Resolve* partial
src/libraries/System.Net.NameResolution/src/System.Net.NameResolution.csprojWires new sources and Windows Dnsapi interop into the build
src/libraries/System.Net.NameResolution/src/Resources/Strings.resxAdds SR string for unsupported custom DNS ports
src/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.csAdds new public API contract entries
src/libraries/Common/src/Interop/Windows/Interop.Libraries.csAdds Libraries.Dnsapi constant
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.csAdds DnsQueryEx/DNS_RECORD-related structs/constants
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.csAdds LibraryImport declarations for DnsQueryEx/DnsCancelQuery/DnsFree

Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated
Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

@MihaZupanMihaZupan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass through.

Just curious, will there be a way to opt-in to using the managed implementation even on Windows, or would there be no reason to want to do that anyway?

Comment on lines +75 to +82
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name) { throw null; }
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name, System.Net.Sockets.AddressFamily addressFamily) { throw null; }
public System.Net.DnsResult<System.Net.SrvRecord> ResolveSrv(string name) { throw null; }
public System.Net.DnsResult<System.Net.MxRecord> ResolveMx(string name) { throw null; }
public System.Net.DnsResult<System.Net.TxtRecord> ResolveTxt(string name) { throw null; }
public System.Net.DnsResult<System.Net.CNameRecord> ResolveCName(string name) { throw null; }
public System.Net.DnsResult<System.Net.PtrRecord> ResolvePtr(string name) { throw null; }
public System.Net.DnsResult<System.Net.NsRecord> ResolveNs(string name) { throw null; }

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname,System.Net.Sockets.AddressFamilyaddressFamily){thrownull;}
publicSystem.Net.DnsResult<System.Net.SrvRecord>ResolveSrv(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.MxRecord>ResolveMx(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.TxtRecord>ResolveTxt(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.CNameRecord>ResolveCName(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.PtrRecord>ResolvePtr(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.NsRecord>ResolveNs(stringname){thrownull;}

I think we should talk about this with the team :)

My stance continues to be that exposing sync APIs here is a mistake, especially if we have real plans to eventually add support for resolution over HTTPS/QUIC.
The fact that e.g. Resolve silently has 2x the latency compared to the async variant makes the argument that we need sync APIs for perf wrong IMO.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am also not entirely happy with having synchronous versions as well, we can bring it in a team discussion and push back if more of us feel strongly about this :)

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 4 comments.

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
@MichalPetryka

MichalPetryka commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

I've worked with DNS apis here before so here's what I wanted to note:

  • This needs to account for this pre Windows 11 bug and fallback to DnsQueryW for affected cases (it's only when DnsQueryEx would return synchronously).
  • IIRC DnsQueryEx is also broken under impersonization, so this needs identical handling like the GetAddrInfoW handling today has.

CopilotAI review requested due to automatic review settings June 18, 2026 11:38

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 6 comments.

Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.cs Outdated
Comment on lines +48 to +54
[OuterLoop("Binds the loopback DNS port 53 and issues real DnsQueryEx calls.")]
[Collection(nameof(DisableParallelization))]
[PlatformSpecific(TestPlatforms.Windows)]
public class DnsResolverLoopbackTest : IClassFixture<WindowsLoopbackServer>
{
private static DnsResolver CreateResolver(LoopbackDnsServer server)
=> new DnsResolver(new DnsResolverOptions { Servers = { server.EndPoint } });
Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

rzikm added a commit that referenced this pull request Jul 8, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
eiriktsarpalis pushed a commit that referenced this pull request Jul 15, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@github-actionsgithub-actionsBot locked and limited conversation to collaborators Jul 26, 2026
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@rzikm@MichalPetryka@MihaZupan
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Implement DnsResolver for Windows - #129302

Closed
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver
Closed

Implement DnsResolver for Windows#129302
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver

Conversation

@rzikm

Copy link
Copy Markdown
Member

Implements the API approved in #19443:

  • New Dns.Resolve*[Async] static methods for A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
  • New DnsResolver / DnsResolverOptions for instance-based resolution with optional custom DNS servers.
  • Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord, PtrRecord, NsRecord.
  • DnsResponseCode enum and DnsResult envelope carrying ResponseCode, Records, and NegativeCacheTtl.

Windows implementation uses DnsQueryEx. Non-Windows platforms get PlatformNotSupportedException stubs pending follow-up implementations (splitting to multiple stacked PRs for easier review).

CopilotAI review requested due to automatic review settings June 11, 2026 16:57
@rzikm
rzikm requested a review from a teamJune 11, 2026 16:58
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new DNS query API surface area to System.Net.NameResolution (new Dns.Resolve* static entry points plus an instance-based DnsResolver), and implements the Windows PAL using DnsQueryEx. It also introduces functional tests, including deterministic loopback-server-driven tests for record parsing/handling.

Changes:

  • Adds new public APIs: Dns.Resolve* (A/AAAA/SRV/MX/TXT/CNAME/PTR/NS), DnsResolver, DnsResolverOptions, record structs, DnsResult<T>, and DnsResponseCode.
  • Implements Windows DNS querying/parsing via DnsQueryEx (sync + async paths), plus non-Windows PNSE stubs.
  • Adds functional tests (outer-loop network tests + loopback DNS server tests) and extends NameResolution telemetry to handle string[] answers.

Reviewed changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 18 comments.

Show a summary per file
FileDescription
src/libraries/System.Net.NameResolution/tests/FunctionalTests/System.Net.NameResolution.Functional.Tests.csprojAdds new functional test sources to the project
src/libraries/System.Net.NameResolution/tests/FunctionalTests/LoopbackDnsServer.csAdds an in-process UDP/TCP loopback DNS server for deterministic tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResponseBuilder.csAdds a fluent builder for DNS response bytes used by loopback tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverTest.csAdds outer-loop functional tests for the new APIs (real DNS)
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverLoopbackTest.csAdds deterministic loopback-server-driven tests for parsing/behavior/metrics
src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.csExtends telemetry answer handling to support string[]
src/libraries/System.Net.NameResolution/src/System/Net/DnsResult.csIntroduces DnsResult<T> envelope type
src/libraries/System.Net.NameResolution/src/System/Net/DnsResponseCode.csIntroduces DnsResponseCode enum
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Windows.csImplements Windows PAL via DnsQueryEx, record parsing, cancellation, glue, TTL extraction
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Unsupported.csAdds non-Windows PNSE PAL stubs
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverOptions.csAdds options type for custom server selection
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.csAdds instance-based resolver API + telemetry wrapping
src/libraries/System.Net.NameResolution/src/System/Net/DnsRecords.csAdds record structs (Address/Srv/Mx/Txt/CName/Ptr/Ns)
src/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.csAdds new static Dns.Resolve* APIs backed by a default resolver
src/libraries/System.Net.NameResolution/src/System/Net/Dns.csMakes Dns partial to host the new Dns.Resolve* partial
src/libraries/System.Net.NameResolution/src/System.Net.NameResolution.csprojWires new sources and Windows Dnsapi interop into the build
src/libraries/System.Net.NameResolution/src/Resources/Strings.resxAdds SR string for unsupported custom DNS ports
src/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.csAdds new public API contract entries
src/libraries/Common/src/Interop/Windows/Interop.Libraries.csAdds Libraries.Dnsapi constant
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.csAdds DnsQueryEx/DNS_RECORD-related structs/constants
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.csAdds LibraryImport declarations for DnsQueryEx/DnsCancelQuery/DnsFree

Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated
Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

@MihaZupanMihaZupan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass through.

Just curious, will there be a way to opt-in to using the managed implementation even on Windows, or would there be no reason to want to do that anyway?

Comment on lines +75 to +82
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name) { throw null; }
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name, System.Net.Sockets.AddressFamily addressFamily) { throw null; }
public System.Net.DnsResult<System.Net.SrvRecord> ResolveSrv(string name) { throw null; }
public System.Net.DnsResult<System.Net.MxRecord> ResolveMx(string name) { throw null; }
public System.Net.DnsResult<System.Net.TxtRecord> ResolveTxt(string name) { throw null; }
public System.Net.DnsResult<System.Net.CNameRecord> ResolveCName(string name) { throw null; }
public System.Net.DnsResult<System.Net.PtrRecord> ResolvePtr(string name) { throw null; }
public System.Net.DnsResult<System.Net.NsRecord> ResolveNs(string name) { throw null; }

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname,System.Net.Sockets.AddressFamilyaddressFamily){thrownull;}
publicSystem.Net.DnsResult<System.Net.SrvRecord>ResolveSrv(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.MxRecord>ResolveMx(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.TxtRecord>ResolveTxt(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.CNameRecord>ResolveCName(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.PtrRecord>ResolvePtr(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.NsRecord>ResolveNs(stringname){thrownull;}

I think we should talk about this with the team :)

My stance continues to be that exposing sync APIs here is a mistake, especially if we have real plans to eventually add support for resolution over HTTPS/QUIC.
The fact that e.g. Resolve silently has 2x the latency compared to the async variant makes the argument that we need sync APIs for perf wrong IMO.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am also not entirely happy with having synchronous versions as well, we can bring it in a team discussion and push back if more of us feel strongly about this :)

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 4 comments.

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
@MichalPetryka

MichalPetryka commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

I've worked with DNS apis here before so here's what I wanted to note:

  • This needs to account for this pre Windows 11 bug and fallback to DnsQueryW for affected cases (it's only when DnsQueryEx would return synchronously).
  • IIRC DnsQueryEx is also broken under impersonization, so this needs identical handling like the GetAddrInfoW handling today has.

CopilotAI review requested due to automatic review settings June 18, 2026 11:38

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 6 comments.

Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.cs Outdated
Comment on lines +48 to +54
[OuterLoop("Binds the loopback DNS port 53 and issues real DnsQueryEx calls.")]
[Collection(nameof(DisableParallelization))]
[PlatformSpecific(TestPlatforms.Windows)]
public class DnsResolverLoopbackTest : IClassFixture<WindowsLoopbackServer>
{
private static DnsResolver CreateResolver(LoopbackDnsServer server)
=> new DnsResolver(new DnsResolverOptions { Servers = { server.EndPoint } });
Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

rzikm added a commit that referenced this pull request Jul 8, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
eiriktsarpalis pushed a commit that referenced this pull request Jul 15, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@github-actionsgithub-actionsBot locked and limited conversation to collaborators Jul 26, 2026
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@rzikm@MichalPetryka@MihaZupan
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Implement DnsResolver for Windows - #129302

Closed
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver
Closed

Implement DnsResolver for Windows#129302
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver

Conversation

@rzikm

Copy link
Copy Markdown
Member

Implements the API approved in #19443:

  • New Dns.Resolve*[Async] static methods for A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
  • New DnsResolver / DnsResolverOptions for instance-based resolution with optional custom DNS servers.
  • Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord, PtrRecord, NsRecord.
  • DnsResponseCode enum and DnsResult envelope carrying ResponseCode, Records, and NegativeCacheTtl.

Windows implementation uses DnsQueryEx. Non-Windows platforms get PlatformNotSupportedException stubs pending follow-up implementations (splitting to multiple stacked PRs for easier review).

CopilotAI review requested due to automatic review settings June 11, 2026 16:57
@rzikm
rzikm requested a review from a teamJune 11, 2026 16:58
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new DNS query API surface area to System.Net.NameResolution (new Dns.Resolve* static entry points plus an instance-based DnsResolver), and implements the Windows PAL using DnsQueryEx. It also introduces functional tests, including deterministic loopback-server-driven tests for record parsing/handling.

Changes:

  • Adds new public APIs: Dns.Resolve* (A/AAAA/SRV/MX/TXT/CNAME/PTR/NS), DnsResolver, DnsResolverOptions, record structs, DnsResult<T>, and DnsResponseCode.
  • Implements Windows DNS querying/parsing via DnsQueryEx (sync + async paths), plus non-Windows PNSE stubs.
  • Adds functional tests (outer-loop network tests + loopback DNS server tests) and extends NameResolution telemetry to handle string[] answers.

Reviewed changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 18 comments.

Show a summary per file
FileDescription
src/libraries/System.Net.NameResolution/tests/FunctionalTests/System.Net.NameResolution.Functional.Tests.csprojAdds new functional test sources to the project
src/libraries/System.Net.NameResolution/tests/FunctionalTests/LoopbackDnsServer.csAdds an in-process UDP/TCP loopback DNS server for deterministic tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResponseBuilder.csAdds a fluent builder for DNS response bytes used by loopback tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverTest.csAdds outer-loop functional tests for the new APIs (real DNS)
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverLoopbackTest.csAdds deterministic loopback-server-driven tests for parsing/behavior/metrics
src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.csExtends telemetry answer handling to support string[]
src/libraries/System.Net.NameResolution/src/System/Net/DnsResult.csIntroduces DnsResult<T> envelope type
src/libraries/System.Net.NameResolution/src/System/Net/DnsResponseCode.csIntroduces DnsResponseCode enum
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Windows.csImplements Windows PAL via DnsQueryEx, record parsing, cancellation, glue, TTL extraction
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Unsupported.csAdds non-Windows PNSE PAL stubs
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverOptions.csAdds options type for custom server selection
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.csAdds instance-based resolver API + telemetry wrapping
src/libraries/System.Net.NameResolution/src/System/Net/DnsRecords.csAdds record structs (Address/Srv/Mx/Txt/CName/Ptr/Ns)
src/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.csAdds new static Dns.Resolve* APIs backed by a default resolver
src/libraries/System.Net.NameResolution/src/System/Net/Dns.csMakes Dns partial to host the new Dns.Resolve* partial
src/libraries/System.Net.NameResolution/src/System.Net.NameResolution.csprojWires new sources and Windows Dnsapi interop into the build
src/libraries/System.Net.NameResolution/src/Resources/Strings.resxAdds SR string for unsupported custom DNS ports
src/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.csAdds new public API contract entries
src/libraries/Common/src/Interop/Windows/Interop.Libraries.csAdds Libraries.Dnsapi constant
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.csAdds DnsQueryEx/DNS_RECORD-related structs/constants
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.csAdds LibraryImport declarations for DnsQueryEx/DnsCancelQuery/DnsFree

Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated
Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

@MihaZupanMihaZupan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass through.

Just curious, will there be a way to opt-in to using the managed implementation even on Windows, or would there be no reason to want to do that anyway?

Comment on lines +75 to +82
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name) { throw null; }
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name, System.Net.Sockets.AddressFamily addressFamily) { throw null; }
public System.Net.DnsResult<System.Net.SrvRecord> ResolveSrv(string name) { throw null; }
public System.Net.DnsResult<System.Net.MxRecord> ResolveMx(string name) { throw null; }
public System.Net.DnsResult<System.Net.TxtRecord> ResolveTxt(string name) { throw null; }
public System.Net.DnsResult<System.Net.CNameRecord> ResolveCName(string name) { throw null; }
public System.Net.DnsResult<System.Net.PtrRecord> ResolvePtr(string name) { throw null; }
public System.Net.DnsResult<System.Net.NsRecord> ResolveNs(string name) { throw null; }

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname,System.Net.Sockets.AddressFamilyaddressFamily){thrownull;}
publicSystem.Net.DnsResult<System.Net.SrvRecord>ResolveSrv(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.MxRecord>ResolveMx(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.TxtRecord>ResolveTxt(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.CNameRecord>ResolveCName(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.PtrRecord>ResolvePtr(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.NsRecord>ResolveNs(stringname){thrownull;}

I think we should talk about this with the team :)

My stance continues to be that exposing sync APIs here is a mistake, especially if we have real plans to eventually add support for resolution over HTTPS/QUIC.
The fact that e.g. Resolve silently has 2x the latency compared to the async variant makes the argument that we need sync APIs for perf wrong IMO.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am also not entirely happy with having synchronous versions as well, we can bring it in a team discussion and push back if more of us feel strongly about this :)

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 4 comments.

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
@MichalPetryka

MichalPetryka commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

I've worked with DNS apis here before so here's what I wanted to note:

  • This needs to account for this pre Windows 11 bug and fallback to DnsQueryW for affected cases (it's only when DnsQueryEx would return synchronously).
  • IIRC DnsQueryEx is also broken under impersonization, so this needs identical handling like the GetAddrInfoW handling today has.

CopilotAI review requested due to automatic review settings June 18, 2026 11:38

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 6 comments.

Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.cs Outdated
Comment on lines +48 to +54
[OuterLoop("Binds the loopback DNS port 53 and issues real DnsQueryEx calls.")]
[Collection(nameof(DisableParallelization))]
[PlatformSpecific(TestPlatforms.Windows)]
public class DnsResolverLoopbackTest : IClassFixture<WindowsLoopbackServer>
{
private static DnsResolver CreateResolver(LoopbackDnsServer server)
=> new DnsResolver(new DnsResolverOptions { Servers = { server.EndPoint } });
Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

rzikm added a commit that referenced this pull request Jul 8, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
eiriktsarpalis pushed a commit that referenced this pull request Jul 15, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@github-actionsgithub-actionsBot locked and limited conversation to collaborators Jul 26, 2026
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@rzikm@MichalPetryka@MihaZupan
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Implement DnsResolver for Windows - #129302

Closed
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver
Closed

Implement DnsResolver for Windows#129302
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver

Conversation

@rzikm

Copy link
Copy Markdown
Member

Implements the API approved in #19443:

  • New Dns.Resolve*[Async] static methods for A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
  • New DnsResolver / DnsResolverOptions for instance-based resolution with optional custom DNS servers.
  • Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord, PtrRecord, NsRecord.
  • DnsResponseCode enum and DnsResult envelope carrying ResponseCode, Records, and NegativeCacheTtl.

Windows implementation uses DnsQueryEx. Non-Windows platforms get PlatformNotSupportedException stubs pending follow-up implementations (splitting to multiple stacked PRs for easier review).

CopilotAI review requested due to automatic review settings June 11, 2026 16:57
@rzikm
rzikm requested a review from a teamJune 11, 2026 16:58
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new DNS query API surface area to System.Net.NameResolution (new Dns.Resolve* static entry points plus an instance-based DnsResolver), and implements the Windows PAL using DnsQueryEx. It also introduces functional tests, including deterministic loopback-server-driven tests for record parsing/handling.

Changes:

  • Adds new public APIs: Dns.Resolve* (A/AAAA/SRV/MX/TXT/CNAME/PTR/NS), DnsResolver, DnsResolverOptions, record structs, DnsResult<T>, and DnsResponseCode.
  • Implements Windows DNS querying/parsing via DnsQueryEx (sync + async paths), plus non-Windows PNSE stubs.
  • Adds functional tests (outer-loop network tests + loopback DNS server tests) and extends NameResolution telemetry to handle string[] answers.

Reviewed changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 18 comments.

Show a summary per file
FileDescription
src/libraries/System.Net.NameResolution/tests/FunctionalTests/System.Net.NameResolution.Functional.Tests.csprojAdds new functional test sources to the project
src/libraries/System.Net.NameResolution/tests/FunctionalTests/LoopbackDnsServer.csAdds an in-process UDP/TCP loopback DNS server for deterministic tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResponseBuilder.csAdds a fluent builder for DNS response bytes used by loopback tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverTest.csAdds outer-loop functional tests for the new APIs (real DNS)
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverLoopbackTest.csAdds deterministic loopback-server-driven tests for parsing/behavior/metrics
src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.csExtends telemetry answer handling to support string[]
src/libraries/System.Net.NameResolution/src/System/Net/DnsResult.csIntroduces DnsResult<T> envelope type
src/libraries/System.Net.NameResolution/src/System/Net/DnsResponseCode.csIntroduces DnsResponseCode enum
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Windows.csImplements Windows PAL via DnsQueryEx, record parsing, cancellation, glue, TTL extraction
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Unsupported.csAdds non-Windows PNSE PAL stubs
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverOptions.csAdds options type for custom server selection
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.csAdds instance-based resolver API + telemetry wrapping
src/libraries/System.Net.NameResolution/src/System/Net/DnsRecords.csAdds record structs (Address/Srv/Mx/Txt/CName/Ptr/Ns)
src/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.csAdds new static Dns.Resolve* APIs backed by a default resolver
src/libraries/System.Net.NameResolution/src/System/Net/Dns.csMakes Dns partial to host the new Dns.Resolve* partial
src/libraries/System.Net.NameResolution/src/System.Net.NameResolution.csprojWires new sources and Windows Dnsapi interop into the build
src/libraries/System.Net.NameResolution/src/Resources/Strings.resxAdds SR string for unsupported custom DNS ports
src/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.csAdds new public API contract entries
src/libraries/Common/src/Interop/Windows/Interop.Libraries.csAdds Libraries.Dnsapi constant
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.csAdds DnsQueryEx/DNS_RECORD-related structs/constants
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.csAdds LibraryImport declarations for DnsQueryEx/DnsCancelQuery/DnsFree

Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated
Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

@MihaZupanMihaZupan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass through.

Just curious, will there be a way to opt-in to using the managed implementation even on Windows, or would there be no reason to want to do that anyway?

Comment on lines +75 to +82
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name) { throw null; }
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name, System.Net.Sockets.AddressFamily addressFamily) { throw null; }
public System.Net.DnsResult<System.Net.SrvRecord> ResolveSrv(string name) { throw null; }
public System.Net.DnsResult<System.Net.MxRecord> ResolveMx(string name) { throw null; }
public System.Net.DnsResult<System.Net.TxtRecord> ResolveTxt(string name) { throw null; }
public System.Net.DnsResult<System.Net.CNameRecord> ResolveCName(string name) { throw null; }
public System.Net.DnsResult<System.Net.PtrRecord> ResolvePtr(string name) { throw null; }
public System.Net.DnsResult<System.Net.NsRecord> ResolveNs(string name) { throw null; }

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname,System.Net.Sockets.AddressFamilyaddressFamily){thrownull;}
publicSystem.Net.DnsResult<System.Net.SrvRecord>ResolveSrv(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.MxRecord>ResolveMx(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.TxtRecord>ResolveTxt(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.CNameRecord>ResolveCName(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.PtrRecord>ResolvePtr(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.NsRecord>ResolveNs(stringname){thrownull;}

I think we should talk about this with the team :)

My stance continues to be that exposing sync APIs here is a mistake, especially if we have real plans to eventually add support for resolution over HTTPS/QUIC.
The fact that e.g. Resolve silently has 2x the latency compared to the async variant makes the argument that we need sync APIs for perf wrong IMO.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am also not entirely happy with having synchronous versions as well, we can bring it in a team discussion and push back if more of us feel strongly about this :)

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 4 comments.

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
@MichalPetryka

MichalPetryka commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

I've worked with DNS apis here before so here's what I wanted to note:

  • This needs to account for this pre Windows 11 bug and fallback to DnsQueryW for affected cases (it's only when DnsQueryEx would return synchronously).
  • IIRC DnsQueryEx is also broken under impersonization, so this needs identical handling like the GetAddrInfoW handling today has.

CopilotAI review requested due to automatic review settings June 18, 2026 11:38

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 6 comments.

Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.cs Outdated
Comment on lines +48 to +54
[OuterLoop("Binds the loopback DNS port 53 and issues real DnsQueryEx calls.")]
[Collection(nameof(DisableParallelization))]
[PlatformSpecific(TestPlatforms.Windows)]
public class DnsResolverLoopbackTest : IClassFixture<WindowsLoopbackServer>
{
private static DnsResolver CreateResolver(LoopbackDnsServer server)
=> new DnsResolver(new DnsResolverOptions { Servers = { server.EndPoint } });
Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

rzikm added a commit that referenced this pull request Jul 8, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
eiriktsarpalis pushed a commit that referenced this pull request Jul 15, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@github-actionsgithub-actionsBot locked and limited conversation to collaborators Jul 26, 2026
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@rzikm@MichalPetryka@MihaZupan
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Implement DnsResolver for Windows - #129302

Closed
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver
Closed

Implement DnsResolver for Windows#129302
rzikm wants to merge 0 commit into
dotnet:mainfrom
rzikm:dns-resolver

Conversation

@rzikm

Copy link
Copy Markdown
Member

Implements the API approved in #19443:

  • New Dns.Resolve*[Async] static methods for A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
  • New DnsResolver / DnsResolverOptions for instance-based resolution with optional custom DNS servers.
  • Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord, PtrRecord, NsRecord.
  • DnsResponseCode enum and DnsResult envelope carrying ResponseCode, Records, and NegativeCacheTtl.

Windows implementation uses DnsQueryEx. Non-Windows platforms get PlatformNotSupportedException stubs pending follow-up implementations (splitting to multiple stacked PRs for easier review).

CopilotAI review requested due to automatic review settings June 11, 2026 16:57
@rzikm
rzikm requested a review from a teamJune 11, 2026 16:58
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new DNS query API surface area to System.Net.NameResolution (new Dns.Resolve* static entry points plus an instance-based DnsResolver), and implements the Windows PAL using DnsQueryEx. It also introduces functional tests, including deterministic loopback-server-driven tests for record parsing/handling.

Changes:

  • Adds new public APIs: Dns.Resolve* (A/AAAA/SRV/MX/TXT/CNAME/PTR/NS), DnsResolver, DnsResolverOptions, record structs, DnsResult<T>, and DnsResponseCode.
  • Implements Windows DNS querying/parsing via DnsQueryEx (sync + async paths), plus non-Windows PNSE stubs.
  • Adds functional tests (outer-loop network tests + loopback DNS server tests) and extends NameResolution telemetry to handle string[] answers.

Reviewed changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 18 comments.

Show a summary per file
FileDescription
src/libraries/System.Net.NameResolution/tests/FunctionalTests/System.Net.NameResolution.Functional.Tests.csprojAdds new functional test sources to the project
src/libraries/System.Net.NameResolution/tests/FunctionalTests/LoopbackDnsServer.csAdds an in-process UDP/TCP loopback DNS server for deterministic tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResponseBuilder.csAdds a fluent builder for DNS response bytes used by loopback tests
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverTest.csAdds outer-loop functional tests for the new APIs (real DNS)
src/libraries/System.Net.NameResolution/tests/FunctionalTests/DnsResolverLoopbackTest.csAdds deterministic loopback-server-driven tests for parsing/behavior/metrics
src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.csExtends telemetry answer handling to support string[]
src/libraries/System.Net.NameResolution/src/System/Net/DnsResult.csIntroduces DnsResult<T> envelope type
src/libraries/System.Net.NameResolution/src/System/Net/DnsResponseCode.csIntroduces DnsResponseCode enum
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Windows.csImplements Windows PAL via DnsQueryEx, record parsing, cancellation, glue, TTL extraction
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverPal.Unsupported.csAdds non-Windows PNSE PAL stubs
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolverOptions.csAdds options type for custom server selection
src/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.csAdds instance-based resolver API + telemetry wrapping
src/libraries/System.Net.NameResolution/src/System/Net/DnsRecords.csAdds record structs (Address/Srv/Mx/Txt/CName/Ptr/Ns)
src/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.csAdds new static Dns.Resolve* APIs backed by a default resolver
src/libraries/System.Net.NameResolution/src/System/Net/Dns.csMakes Dns partial to host the new Dns.Resolve* partial
src/libraries/System.Net.NameResolution/src/System.Net.NameResolution.csprojWires new sources and Windows Dnsapi interop into the build
src/libraries/System.Net.NameResolution/src/Resources/Strings.resxAdds SR string for unsupported custom DNS ports
src/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.csAdds new public API contract entries
src/libraries/Common/src/Interop/Windows/Interop.Libraries.csAdds Libraries.Dnsapi constant
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.csAdds DnsQueryEx/DNS_RECORD-related structs/constants
src/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.csAdds LibraryImport declarations for DnsQueryEx/DnsCancelQuery/DnsFree

Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated
Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsApi.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

@MihaZupanMihaZupan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass through.

Just curious, will there be a way to opt-in to using the managed implementation even on Windows, or would there be no reason to want to do that anyway?

Comment on lines +75 to +82
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name) { throw null; }
public System.Net.DnsResult<System.Net.AddressRecord> ResolveAddresses(string name, System.Net.Sockets.AddressFamily addressFamily) { throw null; }
public System.Net.DnsResult<System.Net.SrvRecord> ResolveSrv(string name) { throw null; }
public System.Net.DnsResult<System.Net.MxRecord> ResolveMx(string name) { throw null; }
public System.Net.DnsResult<System.Net.TxtRecord> ResolveTxt(string name) { throw null; }
public System.Net.DnsResult<System.Net.CNameRecord> ResolveCName(string name) { throw null; }
public System.Net.DnsResult<System.Net.PtrRecord> ResolvePtr(string name) { throw null; }
public System.Net.DnsResult<System.Net.NsRecord> ResolveNs(string name) { throw null; }

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.AddressRecord>ResolveAddresses(stringname,System.Net.Sockets.AddressFamilyaddressFamily){thrownull;}
publicSystem.Net.DnsResult<System.Net.SrvRecord>ResolveSrv(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.MxRecord>ResolveMx(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.TxtRecord>ResolveTxt(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.CNameRecord>ResolveCName(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.PtrRecord>ResolvePtr(stringname){thrownull;}
publicSystem.Net.DnsResult<System.Net.NsRecord>ResolveNs(stringname){thrownull;}

I think we should talk about this with the team :)

My stance continues to be that exposing sync APIs here is a mistake, especially if we have real plans to eventually add support for resolution over HTTPS/QUIC.
The fact that e.g. Resolve silently has 2x the latency compared to the async variant makes the argument that we need sync APIs for perf wrong IMO.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am also not entirely happy with having synchronous versions as well, we can bring it in a team discussion and push back if more of us feel strongly about this :)

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 4 comments.

Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/Dns.Resolve.cs Outdated
Comment threadsrc/libraries/System.Net.NameResolution/src/System/Net/DnsResolver.cs Outdated
@MichalPetryka

MichalPetryka commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

I've worked with DNS apis here before so here's what I wanted to note:

  • This needs to account for this pre Windows 11 bug and fallback to DnsQueryW for affected cases (it's only when DnsQueryEx would return synchronously).
  • IIRC DnsQueryEx is also broken under impersonization, so this needs identical handling like the GetAddrInfoW handling today has.

CopilotAI review requested due to automatic review settings June 18, 2026 11:38

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 21 out of 21 changed files in this pull request and generated 6 comments.

Comment threadsrc/libraries/Common/src/Interop/Windows/Dnsapi/Interop.DnsTypes.cs Outdated
Comment on lines +48 to +54
[OuterLoop("Binds the loopback DNS port 53 and issues real DnsQueryEx calls.")]
[Collection(nameof(DisableParallelization))]
[PlatformSpecific(TestPlatforms.Windows)]
public class DnsResolverLoopbackTest : IClassFixture<WindowsLoopbackServer>
{
private static DnsResolver CreateResolver(LoopbackDnsServer server)
=> new DnsResolver(new DnsResolverOptions { Servers = { server.EndPoint } });
Comment threadsrc/libraries/System.Net.NameResolution/ref/System.Net.NameResolution.cs Outdated

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

rzikm added a commit that referenced this pull request Jul 8, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
eiriktsarpalis pushed a commit that referenced this pull request Jul 15, 2026
Replacement for #129302 (thanks,
`gh stack submit` 😠)
Implements the API approved in
#19443:
New Dns.Resolve*[Async] static methods for
A/AAAA/SRV/MX/TXT/CNAME/PTR/NS records.
New DnsResolver / DnsResolverOptions for instance-based resolution with
optional custom DNS servers.
Record types AddressRecord, SrvRecord, MxRecord, TxtRecord, CNameRecord,
PtrRecord, NsRecord.
DnsResponseCode enum and DnsResult envelope carrying ResponseCode,
Records, and NegativeCacheTtl.
Windows implementation uses DnsQueryEx. Non-Windows platforms get
PlatformNotSupportedException stubs pending follow-up implementations
(splitting to multiple stacked PRs for easier review).
---------
Co-authored-by: rzikm <rzikm@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@github-actionsgithub-actionsBot locked and limited conversation to collaborators Jul 26, 2026
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@rzikm@MichalPetryka@MihaZupan