halcyon
November 24th, 2004, 03:22 AM
Ok, I'm now running L'n'S 2.5p2 d1 pretty ok with Phantom v6 ruleset, thanks to the help of many in this forum.
However, I still have some trouble, which I can't seem to be able to nail down or figure out for myself.
I have the situation as follows:
0. Windows XP own DNS service turned off.
1. Windows XP, ethernet -> ADSL connection (DNS server in ADSL modem turned off)
2. XP Network connection / TCP-IP setting has 127.0.0.1 (localhost) as primary dns server. xx.yy.zz.pp as a secondary (this is my isp's primary dns).
3. AnalogX FastCache running as a DNS relay/cache at 127.0.0.1.
4. L'n'S has authorized access for FastCache
5. "DNS-Allowed-1" rule from Phantom v6 is active and modified as follows:
Destination: Equal or = 127.0.0.1 / xx.yy.zz.pp
Destination port: Equals = 53 domain
6. The above rule is active, high on my list (after Invalid UDP blocking rules) and configured to allow traffic in both directions.
Now my problem:
When doing "nslookup www.yahoo.com" from XP command line I sometimes get:
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 127.0.0.1: Timed out
Server: my.isp.dns.com
Address: xx.yy.zz.pp
So, the nslookup cannot access fastcache dns at 127.0.0.1 (the primary dns of my network connection) and switches to the secondary dns (xx.yy.zz.pp).
Of course, this defeats the purpose, as I want fast, configurable and local DNS caching via FastCache.
Also, DNS lookups via Firefox seem REALLY slow and the likelihood of failed dns queries is very high (i.e. I get a "no such host").
The problem I have defies simple explanation to me.
Sometimes DNS at 127.0.0.1 works both from browsers AND from command line "nslookup" query.
This is confirmed by FastCache logs.
Also, when the network app -> Fastcache query works, there is NO entry in the L'n'S LOG (regardless of what logging I have configured on).
Only when my system reverts to using secondary dns (which is NOT localhost), does L'n'S log DNS queries.
I have not been able to find out, why my system switches over from using primary (127.0.0.1) dns to secondary (xx.yy.zz.pp) dns or when it does that.
I'm at loss to explain this.
Can anybody suggest things to try out or to discover.
I acknoledge the fact that this could be completely L'n'S unrelated issue.
However, I've only come acrosss this since I installed L'n'S on my machine.
I'm sure it's just a stupid user error, but I can't figure out where or how :)
Thanks!
best regards,
halcyon
However, I still have some trouble, which I can't seem to be able to nail down or figure out for myself.
I have the situation as follows:
0. Windows XP own DNS service turned off.
1. Windows XP, ethernet -> ADSL connection (DNS server in ADSL modem turned off)
2. XP Network connection / TCP-IP setting has 127.0.0.1 (localhost) as primary dns server. xx.yy.zz.pp as a secondary (this is my isp's primary dns).
3. AnalogX FastCache running as a DNS relay/cache at 127.0.0.1.
4. L'n'S has authorized access for FastCache
5. "DNS-Allowed-1" rule from Phantom v6 is active and modified as follows:
Destination: Equal or = 127.0.0.1 / xx.yy.zz.pp
Destination port: Equals = 53 domain
6. The above rule is active, high on my list (after Invalid UDP blocking rules) and configured to allow traffic in both directions.
Now my problem:
When doing "nslookup www.yahoo.com" from XP command line I sometimes get:
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 127.0.0.1: Timed out
Server: my.isp.dns.com
Address: xx.yy.zz.pp
So, the nslookup cannot access fastcache dns at 127.0.0.1 (the primary dns of my network connection) and switches to the secondary dns (xx.yy.zz.pp).
Of course, this defeats the purpose, as I want fast, configurable and local DNS caching via FastCache.
Also, DNS lookups via Firefox seem REALLY slow and the likelihood of failed dns queries is very high (i.e. I get a "no such host").
The problem I have defies simple explanation to me.
Sometimes DNS at 127.0.0.1 works both from browsers AND from command line "nslookup" query.
This is confirmed by FastCache logs.
Also, when the network app -> Fastcache query works, there is NO entry in the L'n'S LOG (regardless of what logging I have configured on).
Only when my system reverts to using secondary dns (which is NOT localhost), does L'n'S log DNS queries.
I have not been able to find out, why my system switches over from using primary (127.0.0.1) dns to secondary (xx.yy.zz.pp) dns or when it does that.
I'm at loss to explain this.
Can anybody suggest things to try out or to discover.
I acknoledge the fact that this could be completely L'n'S unrelated issue.
However, I've only come acrosss this since I installed L'n'S on my machine.
I'm sure it's just a stupid user error, but I can't figure out where or how :)
Thanks!
best regards,
halcyon