Re: OGR keyserver issues?

On Thu, 2010-12-09 at 08:18 -0800, Kevin G. McCoy wrote:

> All my affected clients are running under various Windows versions. It 
> will be a bit difficult to restart them all, since there are around 50 
> clients that have the problem right now. :-)

Actually, the problem could be anywhere in the DNS resolve path. The OS
is the first on the path, but there could be a "uplink" DNS server to
which OS sends requests to.

For example, I've just discovered that my own Acorp DSL/WAN router also
has a DNS problem causing my perproxy to stuck to malfunctioning
fullserver. This router could act as a "DNS proxy", forwarding DNS
requests from local computers to ISP (so local computers don't need to
know address of external DNS server), but it unconditionally caches
replies. Even worse, on following queries it always returns only one,
fixed IP address from own cache even for multiple-address hosts.

The simplest way to check for DNS problems is to run "nslookup" and type
query "us.v29.distributed.net" few times. If all DNS resolvers are
working correctly, many IP addresses (4 for current fullserver
configuration) must be printed, in different order for each query. One
address or fixed order means problems somewhere in your network. With
buggy router mentioned above it will print 4 addresses for first query
but one (same) for following. Unfortunately, it's impossible to say
where the problems is without detailed knowledge how your specific
network is built.


_______________________________________________
rc5 mailing list
rc5-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected]
http://lists.distributed.net/mailman/listinfo/rc5