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

NCSI test won't resolve ipv4 #403

Open
CaptainFrosty opened this issue Nov 25, 2021 · 1 comment
Open

NCSI test won't resolve ipv4 #403

CaptainFrosty opened this issue Nov 25, 2021 · 1 comment

Comments

@CaptainFrosty
Copy link

Behaviour

I get the error Error getting the IPv4 address of dns.msftncsi.com when doing the NCSI test

Steps to reproduce this issue

  1. Open WindowsSpyBlocker and do NCSI test

Expected behaviour

The DNS should resolve the hostname

Actual behaviour

I get an error error messages for both ipv4 and ipv6 when testing NCSI. The Debian and Firefox servers test correctly. When I go to https://www.msftconnecttest.com/connecttest.txt in a browser I get:

Our services aren't available right now

We're working to restore all services as soon as possible. Please check back soon. 0RQSgYQAAAACY3eV/a0VeRZJMnDSQcqibQVNIRURHRTEyMTYARWRnZQ==_

When I go to http://www.msftncsi.com/ncsi.txt though I can successfully see the text file there.

Rules used

  1. data/firewall/spy.txt

Configuration

Country (ex. United-States) : United States

Operating system (ex. Windows 10 Pro 64 bits) : Windows 11

Winver screenshot :

image_2

@CaptainFrosty
Copy link
Author

I don't know if that message is just standard or if they are really are having problems on their end. Why do they have two NCSI servers now? When I turn my Adguard on it works, but I imagine that's just because the local DNS is accepting everything.

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

2 participants