Yes, I tried tcpdump, and there are no packets sent out. Nothing. nslookup 
just returns with the "Can't find server name . . ." without even trying. I 
even looked up the name server names using whois and put them in /etc/hosts 
as it seems that it wants to reverse DNS their addresses.

One thing that did work, oddly enough, is if I used a caching nameserver on 
the same subnet (10.10.10.203). And it showed up on tcpdump. Then NetBSD 
would resolve names using that nameserver. It's only if the name servers are 
outside of the local network that name resolution doesn't work. I don't 
understand. I modified the networks line in nsswitch.conf to

networks:	files [notfound=continue] dns

and also removed the domain line from resolv.conf as someone else suggested. 
But this doesn't change anything.

It is true that the name servers are behind a firewall, but none of the other 
systems have trouble reaching/using them, as the firewall allows port 53 TCP 
and UDP.

On Thursday 28 June 2001 12:31, you wrote:
> On Thu, Jun 28, 2001 at 10:37:44AM -0500, Michael Owens wrote:
> > I modified the nsswitch.conf, but to no avail. But I can ping the name
> > servers fine. When I do nslookup, the exact error is
> >
> >
> > root@mike> nslookup yahoo.com.
> > nslookup yahoo.com.
> > *** Can't find server name for address 216.140.16.254: No response from
> > server *** Can't find server name for address 216.140.17.254: No response
> > from server *** Default servers are not available
>
> Hum, isn't there some kind of filtering router between the
> nameserevers and your host, which could block UDP packets ?
>
> Did you try running 'tcpdump -n' when running nslookup, to see what
> happens on the wire ?
>
> --
> Manuel Bouyer <bouyer@antioche.eu.org>
> --

-- 
           _ _        
 _ __ ___ (_) | _____ 
| '_ ` _ \| | |/ / _ \  | Where does Bill want you to go today?
| | | | | | |   <  __/  | Find out at the Micro$oft Boycott Campaign
|_| |_| |_|_|_|\_\___|  | http://www.msbc.simplenet.com