On Mon, Nov 06, 2000 at 05:53:12PM +0000, Philip Blundell wrote:
> In message <20001106164350.E11207@???>, Marcin Owsiany write
> s:
> >Each took about 5 seconds. Now I don't know what to think :-\
>
> As Nigel said, it's likely that you have some local nsswitch.conf problem.
> Check that you aren't going to NIS or anything like that for name service.
> (The queries that nslookup does don't go through NSS.)
I didn't do anything weird (i guess :-) with my host configuration. Anyway,
here it is attached. The two remote nameservers i'm using are two main
nameservers of Poland's largest telecommunications company. My local
nameserver is almost out-of-the-box Debian's squid, with only one zone added
and forwarders equal to the ones in /etc/resolv.conf.
It seems that the problem is that out of the remote nameservers that are
queried (see tcpdump's output attached to my first post) only one responds
and there is some kind of error in that response anyway.
regards
Marcin
--
+--------------------------------+ The reason we come up with new versions
|Marcin Owsiany | is not to fix bugs. It's the stupidest
|porridge@???| reason to buy a new version
+--------------------------------+ I ever heard. - Bill Gates
order hosts,bind
multi on
nameserver 127.0.0.1
domain skynet.com.pl
nameserver 194.204.152.34
nameserver 194.204.159.1
127.0.0.1 localhost
213.25.173.230 skynet.skynet.com.pl skynet starnet
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat
group: compat
shadow: compat
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
