R
Rick T
I'm installing AnalogX's FastCache; it requires DNS to be set to
127.0.0.1, but when I do that I get an error message.
Rick
127.0.0.1, but when I do that I get an error message.
Rick
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.
You should upgrade or use an alternative browser.
H
Herb Martin
Rick T said:I'm installing AnalogX's FastCache; it requires DNS to be set to
127.0.0.1, but when I do that I get an error message.
What is the error message?
Chances are it's innocuous if you really have a working
caching DNS server on the same machine.
BTW, why are you doing this?
(All Win2000 class machines have a built-in, on by default
DNS cache for themselves. Are you going to be a caching-only
DNS server for other machines in your network?)
What's the real goal?
R
Rick T
Herb said:What is the error message?
Chances are it's innocuous if you really have a working
caching DNS server on the same machine.
BTW, why are you doing this?
(All Win2000 class machines have a built-in, on by default
DNS cache for themselves. Are you going to be a caching-only
DNS server for other machines in your network?)
What's the real goal?
So many questions, lol...
"IP addresses starting with 127 are not valid because they are reserved
for loopback addresses"
I'm just trying to avoid hitting up my ISP's DNS servers repeatedly for
the same addys.
FastCache increases the hold time for DNS lookups (if that's the correct
terminology); I'm tired of getting Not Founds using my ISP's DNS servers
about 10% of the time (then when I immediately retry it usually works).
Rick
J
Jim Byrd
Hi Rick - Much better solution: http://ntcanuck.com/
R
Rick T
Jim said:Hi Rick - Much better solution: http://ntcanuck.com/
I had that installed at some point in time... then I noticed on my
firewall tons of 1026/1027 inbound from china so I uninstalled it...
they're still coming in so it was(/is) probably the kids' msn spam; I
disrecall how well Treewalk worked.
Rick
D
David D
Maybe a bit overkill but I use the "defacto standard" BIND from http://www.isc.org
Configure it as a caching only DNS
/David
Configure it as a caching only DNS
/David
H
Herb Martin
What's the real goal?
This is perfectly fine on the SAME machine as the one where the cache
DNS runs -- you may also just use the IP address (of that same machine.)
I take it you are running this on a Workstation (non-Server) and so cannot
just run the Microsoft DNS server.
10%? -- unless you are a spammer with very dirty mailing lists (lots of
invalid
domains) then this is totally unacceptable and indicates you should just
avoid the ISP DNS completely.
If you use an internal DNS (for AD etc.) then you should configure your
internal clients to use STRICTLY that internal DNS and let it worry about
external resolution. ( I am assuming that is not your case however.)
So many questions, lol...
"IP addresses starting with 127 are not valid because they are reserved
for loopback addresses"
This is perfectly fine on the SAME machine as the one where the cache
DNS runs -- you may also just use the IP address (of that same machine.)
I'm just trying to avoid hitting up my ISP's DNS servers repeatedly for
the same addys.
I take it you are running this on a Workstation (non-Server) and so cannot
just run the Microsoft DNS server.
FastCache increases the hold time for DNS lookups (if that's the correct
terminology); I'm tired of getting Not Founds using my ISP's DNS servers
about 10% of the time (then when I immediately retry it usually works).
10%? -- unless you are a spammer with very dirty mailing lists (lots of
invalid
domains) then this is totally unacceptable and indicates you should just
avoid the ISP DNS completely.
If you use an internal DNS (for AD etc.) then you should configure your
internal clients to use STRICTLY that internal DNS and let it worry about
external resolution. ( I am assuming that is not your case however.)
J
Jim Byrd
Hi Rick - I'm extremely please with the performance of the latest version
(using the ICANN slave root add-on in my case - there are other
alternatives). I set things up with 127.0.0.1 as the primary (which is the
way Treewalk Hawk will install things) and then have added a couple of
"fallback" DNS sites as secondaries to be available when I have TW disabled
for some reason. Highly Recommended!
(using the ICANN slave root add-on in my case - there are other
alternatives). I set things up with 127.0.0.1 as the primary (which is the
way Treewalk Hawk will install things) and then have added a couple of
"fallback" DNS sites as secondaries to be available when I have TW disabled
for some reason. Highly Recommended!
R
Rick T
nope, not a spammer; happens with such mundane sites as google; second
or third try often gets it though (Without knowing much/anything about
how such things work I'm gonna guess a too-low timeout setting and/or
too-high traffic on their DNS servers).
Just a home broadband system and everybody can figure their own settings
(my machine isn't on all the time so it'd be useless as a server for
other machines)
Using the IP of this machine may be feasible though as long as nobody
changes the plugs around on the router (192....); I'll give that a shot.
Thanks
Rick
or third try often gets it though (Without knowing much/anything about
how such things work I'm gonna guess a too-low timeout setting and/or
too-high traffic on their DNS servers).
Just a home broadband system and everybody can figure their own settings
(my machine isn't on all the time so it'd be useless as a server for
other machines)
Using the IP of this machine may be feasible though as long as nobody
changes the plugs around on the router (192....); I'll give that a shot.
Thanks
Rick
H
Herb Martin
Rick T said:nope, not a spammer;
I didn't really mean for you to take that part seriously....
happens with such mundane sites as google; second
or third try often gets it though (Without knowing much/anything about
how such things work I'm gonna guess a too-low timeout setting and/or
too-high traffic on their DNS servers).
In that case you either have a problem on the network or (more likely)
an unreliable and unusable ISP DNS.
I would determine the source of the problem and likely just STOP
using the ISP-DNS is that is the culprit.
Or maybe stop using the ISP even.
Just a home broadband system and everybody can figure their own settings
(my machine isn't on all the time so it'd be useless as a server for
other machines)
Right. What about your Broadband router? Do you have a separate
(little) router or some such?
Most of those are quite capable of serving as cache DNS (or you
can buy one cheaply that does it.)
Using the IP of this machine may be feasible though as long as nobody
changes the plugs around on the router (192....); I'll give that a shot.
You really should be fine with 127.0.0.1 though.
Does it work? (Other than the possibly cosmetic error.)
R
Rick T
Herb said:I didn't really mean for you to take that part seriously....
In that case you either have a problem on the network or (more likely)
an unreliable and unusable ISP DNS.
I would determine the source of the problem and likely just STOP
using the ISP-DNS is that is the culprit.
Or maybe stop using the ISP even.
Right. What about your Broadband router? Do you have a separate
(little) router or some such?
Most of those are quite capable of serving as cache DNS (or you
can buy one cheaply that does it.)
Linksys in from the modem; doesn't have cacheing though I just found out
I can set it to different DNS's.
You really should be fine with 127.0.0.1 though.
Does it work? (Other than the possibly cosmetic error.)
the 192... worked for one lookup then failed the rest :/
W2K won't let me enter a 127... through network properties (it truncates
it to 1... which is more than annoying). Edited the registry to read
127... bypassing the warning message; looks like it's working currently
but FastCache doesn't appear to be doing anything.
Rick
H
Herb Martin
W2K won't let me enter a 127... through network properties (it truncates
Go to the command line and try nslookup:
nslookup SomeRecord 127.0.0.1
Or use the IP of the machine as the final (DNS server) parameter.
You may not have FastCache configured and running correctly.
it to 1... which is more than annoying). Edited the registry to read
127... bypassing the warning message; looks like it's working currently
but FastCache doesn't appear to be doing anything.
Go to the command line and try nslookup:
nslookup SomeRecord 127.0.0.1
Or use the IP of the machine as the final (DNS server) parameter.
You may not have FastCache configured and running correctly.
R
Rick T
Herb said:Go to the command line and try nslookup:
nslookup SomeRecord 127.0.0.1
Or use the IP of the machine as the final (DNS server) parameter.
You may not have FastCache configured and running correctly.
Got it; not sure what the problem was; seems to be working fine now.
Thanks
Rick