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.

Sign up for GitHub

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

Jump to bottom

ConnectionSpecificDomains still not handled properly #123

Closed
dovholuknf opened this issue Oct 7, 2020 · 0 comments
Closed

ConnectionSpecificDomains still not handled properly #123

dovholuknf opened this issue Oct 7, 2020 · 0 comments

Comments

@dovholuknf
Copy link
Member

Some applications in windows (for example Chrome) will append the "ConnectionSpecificDomain" to the DNS request before it is made. This means if the adapter has a ConnectionSpecificDomain of "potato.potato" and a request is made for mydemonstration this request will land at the DNS server as "mydemonstration.potato.potato".

This causes the DNS resolution to fail because the service was mapped to mydemonstration only. Account for ConnectionSpecificDomains.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dovholuknf