Marc Schneiders writes:
> 
> I suppose you are right. There *is* something wrong with my DNS,
> though similar resolv.conf work fine on FreeBSD and Linux machines
> here. I've tried to find out what it is, but couldn't. Running named
> on the NetBSD machines makes no difference. If I understand man pages
> correctly I should not need a resolv.conf when running named. Well I
> do. I have to get rid of the resolv.conf to be able to telnet to the
> NetBSD machines and get it back when I want the NetBSD boxes to
> connect to the internet.  I am quite stupid, and gave in after
> spending a night finding out how to fix this. I now simply copy
> resolv.conf to RESOLV.CONF and back when needed through "scripts", one
> included in rc.local.shutdown.

This is normally a problem when the ip addresses you are using are not
in the DNS tables.  Typically this happens when you are running private
ip addresses internally with a NAT box or other proxy.  If, for example,
you are using '192.168.1.0' as an internal Class C subnet, you need
to create a reverse entry for 1.168.192.in-addr.arpa. in your DNS tables.

Whenever I see this problem it is always because of the reverse lookup.
It takes several minutes for the PTR query to timeout, but after that the
telnet or whatever should connect/work.

-Andrew
-- 
-----------------------------------------------------------------
Andrew Gillham                            | NetBSD ist Affengeil.
gillham@whirlpool.com                     | Nachts ist es kaelter
I speak for myself, not for my employer.  | als draussen.