From owner-freebsd-questions Sat Nov 2 8:18:42 2002 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 4293137B401 for ; Sat, 2 Nov 2002 08:18:40 -0800 (PST) Received: from smtprelay6.dc2.adelphia.net (smtprelay6.dc2.adelphia.net [64.8.50.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 585AD43E42 for ; Sat, 2 Nov 2002 08:18:34 -0800 (PST) (envelope-from alex@battleface.com) Received: from prometheus.localdomain ([68.64.68.238]) by smtprelay6.dc2.adelphia.net (Netscape Messaging Server 4.15 smtprelay6 Dec 7 2001 09:58:59) with ESMTP id H4YIMS02.U1Q for ; Sat, 2 Nov 2002 11:18:28 -0500 Subject: Re: Resolving hostnames takes "forever" From: "Alex(ander Sendzimir)" To: freebsd-questions@FreeBSD.ORG In-Reply-To: <20021102144105.GA1116@happy-idiot-talk.infracaninophi> References: <200211021432.19756.freebsd.nospam@mekanix.dk> <20021102144105.GA1116@happy-idiot-talk.infracaninophi> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 02 Nov 2002 10:27:19 -0500 Message-Id: <1036250840.74419.67.camel@prometheus> Mime-Version: 1.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wow. This has been extremely useful to me, too. I have virtually the same setup and problem. If I'm understanding what you [Dr Seaman] are saying, if I analyze the dns packet data, I might be able to determine if my ISP's DNS software is broken? I would like to try this because I have a suspicion this is very likely. Finally, would it be worth while to run my own DNS server? Will setting it up be more trouble than it's worth? Thanks, Doc. Alex On Sat, 2002-11-02 at 09:41, Matthew Seaman wrote: On Sat, Nov 02, 2002 at 02:32:19PM +0100, Bjarne Wichmann Petersen wrote: The first thing you need to do to track down the problem is to trace the DNS queries your system makes while you attempt to browse the net. Supposing that your ethernet interface is fxp0, then you need to run commands like the following: # tcpdump -i fxp0 port 53 -w /tmp/dns-packets [ do some browsing in another window, then hit Ctrl-C ] This will record all the DNS traffic in the file in /tmp. You can view the transactions by: # tcpdump -r /tmp/dns-packets The reason for not just reading the DNS traffic directly is that tcpdump tends to generate and pick up it's own DNS traffic, which tends to lead to a massive feedback loop. a lot of good material -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message -- A L E X A N D E R S E N D Z I M I R Battleface Computing Custom Computing - Linux & Free BSD - C, Perl, Python, WWW info@battleface.com | 802 863 5502 | Colchester, VT 05446 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message