| From: | "WELTY, RICHARD" <richard(dot)welty(at)bankofamerica(dot)com> |
|---|---|
| To: | Richard_D_Levine(at)raytheon(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: DNS vs /etc/hosts |
| Date: | 2005-08-04 20:46:06 |
| Message-ID: | 5428D633F4014E4EBB589EE17A86BAEC086DC70F@usalbwmxmp23.ny.fbf1.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org]On Behalf Of
Richard_D_Levine(at)raytheon(dot)com
Sent: Thursday, August 04, 2005 4:29 PM
To: pgsql-general(at)postgresql(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lowell.Hought | 2005-08-04 21:39:02 | Re: DNS vs /etc/hosts |
| Previous Message | Richard_D_Levine | 2005-08-04 20:28:44 | Re: DNS vs /etc/hosts |