From owner-freebsd-questions@FreeBSD.ORG Tue Oct 25 13:38:19 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66C4E16A41F for ; Tue, 25 Oct 2005 13:38:19 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from speechpro.com (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03A9F43D45 for ; Tue, 25 Oct 2005 13:38:18 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from sysadm.stc ([192.168.2.26]) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1EUP0K-000JjT-97; Tue, 25 Oct 2005 17:38:16 +0400 Message-ID: <435E353B.4070609@speechpro.com> Date: Tue, 25 Oct 2005 17:38:03 +0400 From: Igor Robul User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mohan Singh , freebsd-questions@freebsd.org References: <48d803190510250633k93e3934n7f1dd2bca493e21e@mail.gmail.com> In-Reply-To: <48d803190510250633k93e3934n7f1dd2bca493e21e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archived: Yes Cc: Subject: Re: telnetting/netcatting into a DNS server? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2005 13:38:19 -0000 Mohan Singh wrote: >Whenever I need to test a mail/ssh/web server, I usually just telnet or nc >into the appropriate port, i.e.: > > $ echo "GET / " |nc -v yahoo.com 80 > > $ nc -v localhost 22 > Connection to localhost 22 port [tcp/ssh] succeeded! > SSH-1.99-OpenSSH_4.2 > >How would I connect to a nameserver and talk to it so I can know it is >working? I get as far as connecting to the port, but I don't know how to >make it send back anything meaningful. > > if you wish "know" your nameserver works, then nslookup - your.server.ip then try resolve some hostname/ip or host _name_to_resolve_ your.server.ip