Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Software Troubleshooting
Should DNS Client Service Be Disabled When Using MVPS Host File?
Message
<blockquote data-quote="ForgottenSeer 58943" data-source="post: 709007"><p>Just use Netstat -a to see connections. Open command prompt, type netstat -a</p><p></p><p>Remember, without DNSClient your resolution will not be cached unless you have another program or piece of hardware caching resolutions. Your browser is ALREADY caching resolutions, so DNSClient is redundant and even slows down browsing in some cases added a secondary and unnecessary call. Chrome for example has a DNS Preresolver so once the DNS resolution is established from primary forwarder, you are much better off than using DNSClient.</p><p></p><p>For non-browsers, DNS resolution without a cache/resolver will be imperceptibly slower. Ping your DNS and find your non-browser cache speed, usually sub-20ms, something you likely won't perceive. For example if you launch a game it's resolving already during the launch period so a >20ms resolution poll won't be perceptible AT ALL..</p><p></p><p>If you have a local DNS (Pi-Hole, strongly recommended), DNSClient WILL slow everything down because it's adding a second or third layer, totally unnecessary cache to your system. If you use Heimdal, it's adding ANOTHER dns cache because Heimdal itself has a small caching agent from your primary resolver so DNSClient once again gets in your way.</p><p></p><p>We know over the years, that things like DNSClient are junk and should be disabled..</p><p></p><p><a href="https://www.scmagazineuk.com/flaw-in-windows-dns-client-exposed-millions-of-users-to-hacking/article/699416/" target="_blank">Flaw in Windows DNS client exposed millions of users to hacking</a></p><p></p><p><a href="https://tools.cisco.com/security/center/viewAlert.x?alertId=11487" target="_blank">https://tools.cisco.com/security/center/viewAlert.x?alertId=11487</a></p><p></p><p><a href="https://us.norton.com/online-threats/microsoftwindowsdnsclientserviceresponsespoofingvulnera-28553-vulnerability.html" target="_blank">https://us.norton.com/online-threats/microsoftwindowsdnsclientserviceresponsespoofingvulnera-28553-vulnerability.html</a></p><p></p><p><a href="https://support.microsoft.com/en-us/help/945553/ms08-020-vulnerability-in-dns-client-could-allow-spoofing" target="_blank">https://support.microsoft.com/en-us/help/945553/ms08-020-vulnerability-in-dns-client-could-allow-spoofing</a></p></blockquote><p></p>
[QUOTE="ForgottenSeer 58943, post: 709007"] Just use Netstat -a to see connections. Open command prompt, type netstat -a Remember, without DNSClient your resolution will not be cached unless you have another program or piece of hardware caching resolutions. Your browser is ALREADY caching resolutions, so DNSClient is redundant and even slows down browsing in some cases added a secondary and unnecessary call. Chrome for example has a DNS Preresolver so once the DNS resolution is established from primary forwarder, you are much better off than using DNSClient. For non-browsers, DNS resolution without a cache/resolver will be imperceptibly slower. Ping your DNS and find your non-browser cache speed, usually sub-20ms, something you likely won't perceive. For example if you launch a game it's resolving already during the launch period so a >20ms resolution poll won't be perceptible AT ALL.. If you have a local DNS (Pi-Hole, strongly recommended), DNSClient WILL slow everything down because it's adding a second or third layer, totally unnecessary cache to your system. If you use Heimdal, it's adding ANOTHER dns cache because Heimdal itself has a small caching agent from your primary resolver so DNSClient once again gets in your way. We know over the years, that things like DNSClient are junk and should be disabled.. [URL="https://www.scmagazineuk.com/flaw-in-windows-dns-client-exposed-millions-of-users-to-hacking/article/699416/"]Flaw in Windows DNS client exposed millions of users to hacking[/URL] [URL]https://tools.cisco.com/security/center/viewAlert.x?alertId=11487[/URL] [URL]https://us.norton.com/online-threats/microsoftwindowsdnsclientserviceresponsespoofingvulnera-28553-vulnerability.html[/URL] [URL]https://support.microsoft.com/en-us/help/945553/ms08-020-vulnerability-in-dns-client-could-allow-spoofing[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top
