Windows 10: Windows 10 ignores my DNS configuration and uses default DNS instead

I'm trying to setup Unotelly on my computer but Windows 10 ignores my DNS configuration and uses default DNS instead. I have reseted my network in PC settings and in CMD for second attempt, nothing works. Disabled IPv6 in all adapters, nothing works.
DNS still working on my old laptop running Windows 7 so it is not my router or ISP problem

I followed the guide at I'm getting the "UnoDNS Setup is incomplete. Please complete UnoDNS setup." message : UnoTelly Customer Service about nslookup. Here is my result

C:\Windows\System32>nslookup setupcheckapi.unotelly.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: quickstart3.unotelly.com
Address: 209.222.12.53
Aliases: setupcheckapi.unotelly.com

Ipleak.net result





DNS configuration





Programs i have installed that seems to affecting the network, but i never had that problem until Feb 2017
- AVG Internet Security
- Advanced IP Scanner
- Fiddler
- Virtualbox
- QNAP Qsync

Programs that are affecting network are NOT installed
- Dropbox
- Vmware

:)

 

Windows 10 - default DNS server on VPN adapter not used primarily when on Ethernet

Since the upgrade to Windows 10 on a couple of PC's in our company, we have noticed a difference in DNS lookup behaviour compared to Windows 8.1.

Previously, when we connected to a PPTP VPN connection configured in Windows, when we had a VPN connection established, the default DNS server that was used for resolving was the one configured on the VPN adapter.

With Windows 10, we now see that it keeps using the one configured on the Ethernet adapter as primary DNS server.

However, when connected via WiFi, it uses the default DNS server of the VPN adapter. We determined this by running NSLookup from a command prompt. The results are different when connected using ethernet or WiFi.

 

Windows 10 DNS fails for 1-2 minutes after wake from suspend

I have the same problem, and tentatively blame it on a bad interaction between the AT&T U-Verse 5031NV gateway and Windows 10. I have not duplicated the excellent troubleshooting of DavePatent (nice job with ping, and noting the heavy DNS traffic in the
Technet posting you linked in your reply).

I have worked around my problem by hard-coding my DNS servers to be Google's public ones (8.8.8.8, 8.8.4.4) instead of being automatically assigned by the gateway. (Network Connection, properties, IPv4, properties, "Use the following DNS server addresses".)
I still allow the IP address to be assigned automatically. I now get working DNS immediately upon waking the computer, instead of minutes later.

My problem machine is a no-name desktop with Windows 10 Home, purchased March 2016. Skylake chipset, ASUS Maximus VIII Gene motherboard, i5-6600, wired Ethernet with built-in network adapter Intel 1219-V, default automatic IP address and DNS configuration.
My other computers (Win7 desktop wired, Win8.1 laptop wireless, many Android devices wireless) have not had this issue.

I previously had one other issue with U-Verse and the 5031NV adapter when I set it up in late 2014: attempting to turn on the DMZ feature killed everything including my phone service. Known bug, apparently. I no longer try to turn on DMZ. Seems to be
unrelated to the current issue, except for the hint that the 5031NV gateway is ****.

To reiterate, I've resolved the problem to my satisfaction by configuring explicit non-AT&T DNS servers in the Windows 10 computer that was experiencing the DNS outage upon waking.

 

Dns Lock v1.3

 

After reboot, it doesn't work anymore. I checked ipleak.net again and i got different IP from Avast, so i found that AVG just added a new feature named Safe DNS. I uninstalled the feature and everything works now.