We're moving shortly!!! - Actually we're there now!!

Cracked it......Couldn't wait for my ISP to get it's finger out.......so I did the 'host' thing.........a quick 'Lick and Stick' in Notepad, battled my way through the darkness and smoke and here I'am, my Captain, safe and sound......


Cochise, Breathing easy in Bratislava....

 

No cracking needed with Treewalk DNS . And its faster than any dumb ol' isp

Alphalutra1

 

Thanks LWM
Prob solved
Looks like I'm not the only person with misconceptions about hosts file functions

https://www.wilderssecurity.com/showthread.php?t=124660

Learning backwards as well as forwards.

Regards.

 

We have arrived! Thank you Captain LWM!
The grass really is greener on the other side.

 

I just wanted to let everyone know that was concerned about my ability to access the forum that my ISP has updated its DNS, thus I have arrived.

For those of you that were not worried and actually placed phone calls to my ISP offerring them money not to update the DNS, I'm sorry.

For Wilders and everyone involved in the migration, I commend thee for such a smooth transition.

 

I did the HOSTS file thing, didn't notice any interruption. I was busy wiping free space on my HDs

 

Hay so will mine here shortly. Oops your talking that puter stuff, I'm talking my residential address. In any case it is still my good ole Wilders no mater in what location it resides. Ditto the remarks about a good job!

Thanks
Wildman

 

~a small voice is heard coming from the back seat~ Daddy, are we there yet?

 

Hello all,
Interesting how my emachine never missed a beat with the change over no host file change needed.

Yet my Compaq. No way, took me to the notice site everytime.

I hate tapering with the internals of the machine system files.

Anyway I followed LWM instructions bore down into the system files and pasted.

Well I'm here by way of ye old Compaq, so it worked.

My question is why would one computer using the same ISP be different, why would one not need to add the lines to the host file and the other one need it. I will give you the only differences btween the two that I think could possibly make a difference and let the membership give me their thoughts.

Compaq is XP retail box not mass install version, (don't think that would make any difference) Emachine came with XP already installed no disk.

Emachine is wireless, Compaq is not, yet like I said no problem getting the instructions by coming to the forum by way of emachine. I am behind a FW router of course.

Outpost FW on Compaq, McAfee on Emachine.

to me...any suggestions....? Oh well I'm here on the Compaq now, looks like no harm done by pasting those two lines in the hosts file

 

Thanks for your quick reply LWM.

I rebooted yesterday evening thinking that would solve the problem, but yes I stay up and running all the time.

But you hit on something in your reply... what about Out Post DNS Caching plug in that is turned on?

 

Yes, I activated it because as a feature it said pages and sites would load faster. I just ran the help file in Out Post to investigate further, it has limits that you can use to set expirations... I checked mine out they are as follows:

Limit DNS cach to 100 records and DNS cach records expire in 7 days.

To me it is just a toy that can report stuff if needed out of the the log. I am sure someone else could give me a dozen reasons why I need it. Before this latest version I had it turned off.

Would have been interesting to see what would have happened after 7 days.

 

Outpost's DNS Cache does not respect TTL (Time-To-Live) attributes on DNS records but will instead keep the value for 14 days (the default - though you can change this) regardless so it certainly could cause problems with site address changes, as could other DNS caching software. It is however possible to clear entries if a problem is suspected (right-click on the plugin, select Properties/Miscellaneous/DNS Records/Edit/Remove All) and exceptions can be specified for dynamic domains that change often (e.g. dyndns.org).

 

This is good to know Paranoid. Had I known this I would have cleared the enteries. As I really do not like to bore down into the system files and make changes, and only do when a problem occurs.

"If it is not broke don't fix it or try to tweak something that is working", Is my way.

I am not sure how useful this plug in is, I have used it both on and off and can not really tell any difference, but I know only a little of such things. On my Compaq the less RAM useage the better since it is at 256 with no more slots left for me to slip another card in and I do not wish to invest anymore in this old system anyway.

 

DNS caching is also done by the DNS Client Service on Win2K/XP so Outpost's caching would likely make very little difference there. However there are security advantages to disabling the DNS Client Service since it then forces applications to make their own DNS requests (making it possible to detect/block the DNSTester leaktest and malware using similar techniques) in which case Outpost's DNS plugin becomes less redundant.

Aside from that, the main factor would be your Internet connection and your ISP's DNS server. Those on dialup and/or with problematic DNS servers should gain more benefit from DNS caching.