nslookup isn't the easiest tool for use in diagnosing dns problems as it goes through the whole messy nsswitch process, and doesn't readily isolate much of anything.
the dig command focuses on dns only, skips nsswitch altogether, and lets you rule dns problems in or out in one swell foop. if dig is fast and nslookup is slow, then you need to examine /etc/nsswitch for foulups. richard -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Thursday, August 04, 2005 4:29 PM To: pgsql-general@postgresql.org Subject: Re: [GENERAL] DNS vs /etc/hosts Sorry to re-reply, but I had a much simpler idea. From the client machine that is slow to connect, type the command "nslookup hostname1". If it takes 15 seconds. If it does, DNS is the problem. ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
