DNS 8.8.8.8 resolve timeout for dns.msftncsi.com
why is my router using google's DNS when my primary and secondary DNS are 212.159.6.9, 212.159.6.10?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
This domain (www.msftncsi.com) is used for Microsoft Network Connectivity Status Indicator (NCSI) - It is part of "network awareness" in Windows.
Some companies use it in their router FWs to check if there's an Internet connectivity on the device (network monitoring) - a similar question has been answered in this post and this post.
- Copy Link
- Report Inappropriate Content
I have the EXACT same thing
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi, have you checked what are the current WAN DNS as well as LAN DNS?
Can I have some pictures that the router is still using Google address for the DNS resolution?
By the way, what are the hardware as well as the firmware version of VR2100?
Thank you very much.
- Copy Link
- Report Inappropriate Content
Hi, I have the same problem on an Archer VR600v v2 (firmware version: 0.7.0 0.9.1 v0075.0 Build 200616 Rel.36749n).
In the router, the two DNS servers 185.95.218.42 and 185.95.218.43 are set in the WAN settings.
No DNS servers are set in the LAN settings.
The following messages appear in the system log at irregular intervals:
Uhrzeit | Typ | Ebene | Information |
---|---|---|---|
2021-06-02 09:46:53 | HTTPD | Information | DNS 8.8.8.8 resolve succeed for dns.msftncsi.com |
2021-06-02 09:46:53 | HTTPD | Information | DNS 185.95.218.43 resolve timeout for dns.msftncsi.com |
2021-05-31 10:13:27 | HTTPD | Information | DNS 8.8.8.8 resolve succeed for dns.msftncsi.com |
2021-05-31 10:13:27 | HTTPD | Information | DNS 185.95.218.43 resolve timeout for dns.msftncsi.com |
2021-05-31 09:27:59 | HTTPD | Information | DNS 8.8.8.8 resolve succeed for dns.msftncsi.com |
2021-05-31 09:27:59 | HTTPD | Information | DNS 185.95.218.43 resolve timeout for dns.msftncsi.com |
2021-05-31 09:22:24 | HTTPD | Information | DNS 8.8.8.8 resolve succeed for dns.msftncsi.com |
2021-05-31 09:22:24 | HTTPD | Information | DNS 185.95.218.43 resolve timeout for dns.msftncsi.com |
The two DNS servers are monitored via two different monitoring systems and are permanently accessible.
This behavior was noticed because websites did not load at times. This short failure is due to the change of DNS servers.
- Copy Link
- Report Inappropriate Content
Sorry to piggyback, I have the exact same issue with this, most of the time the system log shows:
2 | 2021-06-08 01:56:47 | HTTPD | Information | DNS 1.1.1.1 resolve succeed= for www.msftncsi.com |
3 | 2021-06-08 01:56:47 | HTTPD | Information | DNS 1.1.1.1 resolve succeed for dns.msftncsi.com |
But then occasionally it decides to just take a dump on itself and instead shows
2 | 2021-06-08 01:54:30 | HTTPD | Information | DNS 8.8.8.8 resolve timeout for www.msftncsi.com |
3 | 2021-06-08 01:54:30 | HTTPD | Information | DNS 1.0.0.1 resolve timeout for dns.msftncsi.com |
I've got a Pi-Hole server running as my local DNS, and the WAN DNS servers have been manually pointed to Cloudflare's 1.1.1.1 and 1.0.0.1
No matter what DNS settings I use it still somehow queries 8.8.8.8 and also somehow develops issues with connecting using 1.1.1.1 or 1.0.0.1
It's definitely due to this TP-Link Router as the original ISP router has none of the same issues apart from being just generally awful.
I did disable Bit swap in the Advanced>Network>DSL setttings, and for about 24 hours this solved the issue, but now it's back with avengence. If I can't get this sorted I'm going to have to get yet another modem/router. And for sure will never buy another TP-Link product.
@TP-Link Please help.
- Copy Link
- Report Inappropriate Content
Hi, I have now found a halfway good solution to my problem.
I now use the DNS servers from Quad9. In contrast to my previous ones, these are interestingly accepted by the router without any problems.
Unfortunately, I have not yet been able to find a way to delete the Google DNS servers from the system.
However, it is possible to block the IP address via static routing. This means that a connection is no longer possible.
ID | Zielnetz | Subnetzmaske | Gateway |
---|---|---|---|
1 | 8.8.8.8 | 255.255.255.255 | 192.168.1.1 |
2 | 8.8.4.4 | 255.255.255.255 | 192.168.1.1 |
These two steps have solved the problems for me.
- Copy Link
- Report Inappropriate Content
This domain (www.msftncsi.com) is used for Microsoft Network Connectivity Status Indicator (NCSI) - It is part of "network awareness" in Windows.
Some companies use it in their router FWs to check if there's an Internet connectivity on the device (network monitoring) - a similar question has been answered in this post and this post.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 9144
Replies: 7
Voters 0
No one has voted for it yet.