Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <424D2B43.6070508@endbracket.net> Date: Fri, 01 Apr 2005 21:06:43 +1000 From: Michael Wardle User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: ping, nslookup can't resolve names References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Rich McNeary wrote: > I started trying to ping the other servers in cygwin's bash terminal > but the host couldn't be found, nslookup had similar problems. I had a similar problem a few years ago. The problem was one of: - Windows not properly appending the domain name to a plain host name (i.e. a non-FQDN) - the Windows DNS cache (see ipconfig /flush or similar) - misunderstanding that ping is different from nslookup/host/dig (ping uses the entire name resolution service which may include %windir%/system32/drivers/etc/hosts and others whereas nslookup uses only strictly DNS) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/