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

Evaluate the necessity of Microsoft-specific NCSI DNS record #34

Open
sebschrader opened this issue May 25, 2016 · 0 comments
Open

Evaluate the necessity of Microsoft-specific NCSI DNS record #34

sebschrader opened this issue May 25, 2016 · 0 comments
Milestone

Comments

@sebschrader
Copy link
Member

We should verify if the following DNS record in unauth-dnsmasq.conf for the Microsoft Windows Network Connection Status Indicator (NCSI) is really necessary.

This was added to let Windows detect the presence of the captive portal. But it seems that some machines still try to obtain Windows updates, although the captive portal is present.

For more background information see this superuser blog entry and this technet blog entry

@sebschrader sebschrader added this to the 0.4 milestone May 25, 2016
@sebschrader sebschrader modified the milestones: 0.4, 0.5 Jun 27, 2020
@sebschrader sebschrader modified the milestones: 0.5, 0.6 Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant