Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNSSEC support for Windows #338

Open
foxcpp opened this issue Mar 7, 2021 · 2 comments
Open

DNSSEC support for Windows #338

foxcpp opened this issue Mar 7, 2021 · 2 comments
Labels
good first issue Easy to do, good for newcomers. help wanted We need your help with this one.

Comments

@foxcpp
Copy link
Owner

foxcpp commented Mar 7, 2021

The problem is obtaining system DNS configuration for use in resolver code. The relevant function is NewExtResolver in framework/dns/dnssec.go.

According to https://stackoverflow.com/a/13417318 comments it can be read from registry (DhcpNameServer or NameServer for each interface). Need to figure out which value should be preferred if there are multiple interfaces (or just use them all?).

@foxcpp foxcpp added help wanted We need your help with this one. good first issue Easy to do, good for newcomers. labels Mar 7, 2021
@foxcpp
Copy link
Owner Author

foxcpp commented Jul 5, 2021

I did some reason and it seems like Windows's DNS API does not expose information about DNSSEC status even for Windows versions that have the security-aware client implementation.

@foxcpp
Copy link
Owner Author

foxcpp commented Jul 5, 2021

Therefore extracting DNS configuration from registry and querying servers directly seems to be the only way to obtain security information necessary for maddy security policies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Easy to do, good for newcomers. help wanted We need your help with this one.
Projects
None yet
Development

No branches or pull requests

1 participant