Gnupg-users Digest, Vol 16, Issue 34

John Clizbe JPClizbe at comcast.net
Tue Jan 25 00:15:43 CET 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

lord grinny wrote:

>> 
>> I don't think GPG is at fault here.  Please type the
> following
>> in a command prompt:
>> 
>> nslookup keyserver.kjsl.com
> 
> I tried this, but my DNS is definitly set up okee.
> 
> C:\Documents and
> Settings\Administrator.GRINNY>nslookup
> keyserver.kjsl.com
> *** Can't find server name for address 192.168.0.1:
> Non-existent domain
> *** Default servers are not available
> Server:  UnKnown
> Address:  192.168.0.1
> 
> Non-authoritative answer:
> Name:    keyserver.kjsl.com
> Address:  69.36.241.130
> 
> 192.168.0.1 is my gateway (A windows 98 box serving as
> a router)
> 

That response to nslookup tells me your DNS setup is NOT ok. You could be
getting a DNS resolver timeout causing the lookup to fail.

The D-Link 604-e is wonderfully dodgy at doing DNS forwarding - at least
that my experience with ours.

Try this to see if it's DNS that's the problem: list keyserver.kjsl.com in
your hosts file (%winDir%\system32\drivers\etc\hosts on Win2k, /etc/hosts
on *nix):

69.36.241.130	keyserver.kjsl.com

See if your problem 'resolves' itself. You'll need to flush the name cache
on Windows after changing the hosts file (ipconfig /flushdns).

Check your router, see http://http://192.168.0.1/st_devic.html, and setup
your Windows box(es) to use the DNS servers your broadband provider
supplies to the router in the DHCP setup.  I'd suggest some, but I don't
know who's your ISP. Just setup your Windows box to use a static address
on 192.168.0/24, netmask 255.255.255.0, gateway 192.168.0.1, and whatever
DNS servers your ISP says to use.

>> 
> Do you think I have a better chance on FreeBSD? (I do
> have a dualboot FreeBSD 
> 5.1 and Windows 2000, but I use windows for checking
> my email with thunderbird).
> 

I think FreeBSD would have the same problems. Your problem looks to be DNS
resolver related. If *BSD was configured with 'nameserver 192.168.0.1' in
resolv.conf, you'd probably get the same lookup failures.

- --
John P. Clizbe                   Inet:   JPClizbe(a)comcast DOT nyet
Golden Bear Networks             PGP/GPG KeyID: 0x608D2A10
"Be who you are and say what you feel because those who mind don't matter
and those who matter don't mind." - Dr Seuss, "Oh the Places You'll Go"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1-cvs-2005-01-21 (Windows 2000 Pro SP4)
Comment: When cryptography is outlawed, b25seSBvdXRsYXdzIHdpbGwgdXNlIG
Comment: Annoy John Asscraft -- Use Strong Encryption.
Comment: It's YOUR right - for the time being.
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFB9YGdHQSsSmCNKhARAsc6AKDqY9+T3ipIZ0i2VPoBEy3JqVwlSACgojlq
UII6ZzPmymC01LV1DGY0QPY=
=QuXj
-----END PGP SIGNATURE-----



More information about the Gnupg-users mailing list