|
BIND as a replacement for Windows Hosts file for the purpose of Ad Blocking
Posted by Alec§taar Originally posted by dosfreak: "Was re-reading APK's Host file + dialup problems" I fixed that my man, it was simple once I got the fix too! All it was, was leaving the DHCP service set to 'automatic' & setting DNS service to 'manual'... & the problems I had with the HOSTS file on Windows 2000 went away! (Never had a problem w/ it on Windows XP though, ever!) * Must be one of the 'subtle differences' between 2000 & XP, as there are some in the way of networking (such as 2000 having all networking/IP functions turn on during bootup, which makes its bootup slower for instance whereas XP's IP services start only ON DEMAND (much like Apple Mac OS/X-Panther do it)). Originally posted by dosfreak: " That's EXACTLY what fixed it for me on Windows 2000: Again, stopping the DNS client service! (Never had to on XP though, HOSTS never gave me a hassle there on Dialup from any ISP OR on Cablemodems from any BSP) Originally posted by dosfreak: "Some benefits of using this method over Hosts, is that you no longer have to worry about huge hosts lists that seem to make dial-up flaky, (probably due to Hosts file not being designed for such long lists!) and you can easily carry the file over to any Linux system." Well, usings HOSTS here on 56k dialup works now, & bear in mind the solution: FIX STEPS FOR HOSTS FILE AND Windows 2000 dialup users: ------------------------------------------------------------------------ 1.) Stop DNS client service (set to manual startup type) 2.) Startup DHCP as automatic startup type 3.) Reboot Works! 56k dialup fix for HOSTS file users on Windows 2000 (once more, this never is a problem on Windows XP though, dialup or cable) & on Win2k on cablemodem this was never a problem I can recall either... just on dialup on Win2k. * BUT, the fix above? Works! APK |