Hello again, "If it ain't broke, don't fix it" never was a favorite of mine. I like to make things better all the time, disaster notwithstanding. Note that Lockergnome's advice below seems to be for I.E. and I use Netscape.
Before a Web page (webpage?) can fully load, your browser must first resolve the domain name to its corresponding IP address(es). Since Internet Explorer 4.0, the DNS cache has been resetting itself every thirty minutes. If this time-out setting is way too short for your tastes, then you'll need to fire up the Registry editor and navigate to HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Internet Settings key. In the right-hand pane, right-click and add a new DWORD value. Rename the new entry: "DnsCacheTimeout" (sans quotes). Double-click to edit it's properties, changing the type to Decimal before proceeding. What should 'Value data' be set to? Well, whatever you pick, this is the number of seconds between cache flushings. The higher - the greater the chance of not having the freshest DNS entry. The lower - the more time it will take your system to resolve DNS entries. 1. Any opinions on this from our experienced users? 2. Is this appropriate for Netscape too? 3. Starting with 'Value date' ... what are they talking about and what changes should one make? 4. No cause for alarm ... I'm backing up the registry. Harold ... http://www.geocities.com/buddychai/Navigator.html ... in Brighton Beach, Brooklyn, NY ============= PCWorks Mailing List ================= Don't see your post? Check our posting guidelines & make sure you've followed proper posting procedures, http://pcworkers.com/rules.htm Contact list owner <[EMAIL PROTECTED]> Unsubscribing and other changes: http://pcworkers.com =====================================================
