DNS Registry Hack

[Roderunner]

What, if any, benefits would their be in performing the following. It was found at MVPS.ORG and recommended if using their hosts file with DNS Client in manual or disabled.
----
# Flush the existing DNS cache

# Start > Run (type) regedit
# Navigate to the following location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters

# Click Edit > New > DWORD Value (type) MaxCacheTtl

# Click Edit > New > DWORD Value (type) MaxNegativeCacheTtl

# Next right-click on the MaxCacheTtl entry (right pane) and select: Modify and change the value to 1

# The MaxNegativeCacheTtl entry should already have a value of 0 (leave it that way - see screenshot)

# Close Regedit and reboot ..
--
P.S. forgot to say it is for a laptop. I have tried it and my boot time trebled.
What effect, as above, would using the hack with DNS on auto and not using the hosts file.

 

[DeVandal]

What is your goal?

 

[EzioAuditore]

# Click Edit > New > DWORD Value (type) MaxCacheTtl

This may have something to do with increasing the DNS cache amount so that the pages may load faster and the browser doesn't have to query the DNS for each website reducing the overall time.

I don't know about the other.

 

[Roderunner]

I was hoping it would speed up page loading. This is what I found about it Here

 

[DeVandal]

I was hoping it would speed up page loading. This is what I found about it Here

The hosts file really won't help with that. The settings that you refer to won't really help with that. Both of these are more related to finding a site, not loading it.

And, each website will load at a speed dependent on the content at that site. This is part of why browsers use a cache.

A faster hard drive, a browser cache set to a RAM drive, a cache set to a separate hard drive, a faster CPU, more RAM in some cases, a faster browser - these are how you speed up page loading independently of website design.

 

[Roderunner]

I was hoping it would speed up page loading. This is what I found about it Here

The hosts file really won't help with that. The settings that you refer to won't really help with that. Both of these are more related to finding a site, not loading it.

And, each website will load at a speed dependent on the content at that site. This is part of why browsers use a cache.

A faster hard drive, a browser cache set to a RAM drive, a cache set to a separate hard drive, a faster CPU, more RAM in some cases, a faster browser - these are how you speed up page loading independently of website design.

I'm using hack & host file on my desktop without any bother, its the laptop thats upsetting things.

 

[Roderunner]

Info re topic update
-
DNS Setting
-
Tuning DNS Caching under Microsoft Windows

You can modify the behavior of the Microsoft Windows DNS caching algorithm by setting two registry entries in the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesDnscacheParameters registry key.

The MaxCacheTtl represents the maximum time that the results of a DNS lookup will be cached. The default value is 86,400 seconds. If you set this value to 1, DNS entries will only be cashed for a single second.

MaxNegativeCacheTtl represents the maximim time that the results of a failed DNS lookup will be cached. The default value is 900 seconds. If you set this value to 0, failed DNS lookups will not be cached.

 

[pparks1]

The MaxCacheTtl represents the maximum time that the results of a DNS lookup will be cached. The default value is 86,400 seconds. If you set this value to 1, DNS entries will only be cashed for a single second.

I'm unsure how this would improve performance. Essentially you are saying to only cache a name for 1 second. All subsequent requests would then re-perform a new DNS lookup to determine the name again. All of these DNS Lookups will require time...not speed things up.

 

[Roderunner]

The MaxCacheTtl represents the maximum time that the results of a DNS lookup will be cached. The default value is 86,400 seconds. If you set this value to 1, DNS entries will only be cashed for a single second.

I'm unsure how this would improve performance. Essentially you are saying to only cache a name for 1 second. All subsequent requests would then re-perform a new DNS lookup to determine the name again. All of these DNS Lookups will require time...not speed things up.

As stated in an earlier post, I use the hacks with mvps.org's hosts file and DNS Service on auto on my slightly faster desktop and it does speed up page loading. If used on a laptop 'boot' time trebles.

 

[pparks1]

And as I stated, I don't see from a technical standpoint how expiring the DNS cache every 1 second on your local host could possibly lead to faster page loading... If anything, you would want to cache a DNS lookup even longer, so it only has to look it up once and then just keep referring to the cache rather than doing subsequent lookups.

 

[EzioAuditore]

And as I stated, I don't see from a technical standpoint how expiring the DNS cache every 1 second on your local host could possibly lead to faster page loading... If anything, you would want to cache a DNS lookup even longer, so it only has to look it up once and then just keep referring to the cache rather than doing subsequent lookups.

Yeah. You should increase the cache time so that your system doesn't have to query the DNS again and again for the same site you visited just 1 second ago and can use this cache to begin the page loading sequence faster and what do you mean by '' I use hacks" ?

 

[Roderunner]

And as I stated, I don't see from a technical standpoint how expiring the DNS cache every 1 second on your local host could possibly lead to faster page loading... If anything, you would want to cache a DNS lookup even longer, so it only has to look it up once and then just keep referring to the cache rather than doing subsequent lookups.

Yeah. You should increase the cache time so that your system doesn't have to query the DNS again and again for the same site you visited just 1 second ago and can use this cache to begin the page loading sequence faster and what do you mean by '' I use hacks" ?

Hi, I have read that a PC first checks the host's file, if successful it has no need to use DNS Service.
The 'hacks' are in my start thread, Maybe should have described them as 'edits'

 

[NoN]

The MaxCacheTtl represents the maximum time that the results of a DNS lookup will be cached. The default value is 86,400 seconds. If you set this value to 1, DNS entries will only be cashed for a single second.

I'm unsure how this would improve performance. Essentially you are saying to only cache a name for 1 second. All subsequent requests would then re-perform a new DNS lookup to determine the name again. All of these DNS Lookups will require time...not speed things up.

As stated in an earlier post, I use the hacks with mvps.org's hosts file and DNS Service on auto on my slightly faster desktop and it does speed up page loading. If used on a laptop 'boot' time trebles.

You can see on screenshot, some DNS Cache hack since XP (meant Windows 98)...maybe a look at speedguide.net can help you a litlle but there's a lot of discuss on MS Technet site, search for DNS.

 

[pparks1]

Hi, I have read that a PC first checks the host's file, if successful it has no need to use DNS Service.
The 'hacks' are in my start thread, Maybe should have described them as 'edits'

Yes, the PC always uses the Host file first. This gives you complete ability to override and set DNS entries to whatever you want. Of course, the downside is that if the site ever moves to a new IP, you have to update your hosts file accordingly...otherwise you will still be pointing at the old IP which may or may not resolve to anything.

 

[Fayla]

That's what I do with my computer. It should also help avoid MIM attacks. I have a few entries in my HOSTS file and they are for the SSL login pages of websites I frequent.

The MVPS has a point worth noting:

Editors Note: in most cases a large HOSTS file (over 135 kb) tends to slow down the machine.

Hi, I have read that a PC first checks the host's file, if successful it has no need to use DNS Service.
The 'hacks' are in my start thread, Maybe should have described them as 'edits'

Yes, the PC always uses the Host file first. This gives you complete ability to override and set DNS entries to whatever you want. Of course, the downside is that if the site ever moves to a new IP, you have to update your hosts file accordingly...otherwise you will still be pointing at the old IP which may or may not resolve to anything.

 

[NoN]

another DNS trick:

How to prevent DNS cache pollution

 

[Roderunner]

I'm unsure how this would improve performance. Essentially you are saying to only cache a name for 1 second. All subsequent requests would then re-perform a new DNS lookup to determine the name again. All of these DNS Lookups will require time...not speed things up.

As stated in an earlier post, I use the hacks with mvps.org's hosts file and DNS Service on auto on my slightly faster desktop and it does speed up page loading. If used on a laptop 'boot' time trebles.

You can see on screenshot, some DNS Cache hack since XP (meant Windows 98)...maybe a look at speedguide.net can help you a litlle but there's a lot of discuss on MS Technet site, search for DNS.

Sorry, I can't enlarge the image you posted

Hi, I have read that a PC first checks the host's file, if successful it has no need to use DNS Service.
The 'hacks' are in my start thread, Maybe should have described them as 'edits'

Yes, the PC always uses the Host file first. This gives you complete ability to override and set DNS entries to whatever you want. Of course, the downside is that if the site ever moves to a new IP, you have to update your hosts file accordingly...otherwise you will still be pointing at the old IP which may or may not resolve to anything.

I check MVPS site frequently for updates.

 

[Roderunner]

another DNS trick:

How to prevent DNS cache pollution

I use OpenDNS for my PC's with the updater application.

 

[NoN]

another DNS trick:

How to prevent DNS cache pollution

I use OpenDNS for my PC's with the updater application.

Could be the easier solution checking what's up!...