From owner-freebsd-questions Fri Nov 21 22:44:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17256 for questions-outgoing; Fri, 21 Nov 1997 22:44:42 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from mail.netbistro.com (vortex.netbistro.com [204.239.167.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA17251 for ; Fri, 21 Nov 1997 22:44:38 -0800 (PST) (envelope-from grimm@shell.pgonline.com) Received: (qmail 11992 invoked from network); 22 Nov 1997 06:44:26 -0000 Received: from shell.pgonline.com (grimm@204.239.167.36) by vortex.netbistro.com with SMTP; 22 Nov 1997 06:44:26 -0000 Date: Fri, 21 Nov 1997 22:44:25 -0800 (PST) From: Grimm To: Brian Somers cc: support@freebsd.org Subject: Re: Help with ppp needed... In-Reply-To: <199711220319.DAA08222@awfulhak.demon.co.uk> Message-ID: X-Geek: GCS d- s++:- a-- C++ UB++>++++ P+>++++ L- E? W+ N+(++) o? K- w+(!w---) !O M-- !V PS+ PE Y !PGP t+ ?5 X+ R tv b+ DI+@ D+++@ G e h- r y** MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 22 Nov 1997, Brian Somers wrote: > /etc/resolv.conf is the only thing required to get the DNS stuff > working - as you've already figured out. The only thing I'd suspect > is that you've mis-specified the IP number (or even mis-spelt > ``nameserver''). > > You could always use tcpdump (or "set log +tcp/ip" in ppp) to see if > you get requests going to your DNS on port 53. Tcpdump is better for > this sort of thing 'cos you can get it to just output stuff for a > given port. With this info, you can determine if you're actually > sending the request out (and if the DNS is actually replying). Interestingly enough, I checked all this, and made sure the format was right in my resolv.conf. Then I dialed out with ppp, and tried nslookup. It, uhm, works. And I don't know why, because I didn't change a _thing_ since when it was not working. Although, after it _was_ working, I _did_ change the timeout from its original 180 seconds to 2400. (because I like it that way. ;) ) So I'm thinking it might have timed out while I wasn't looking, or something like that. Anyway. It's fixed. Thanks guys. :) -- A "recovered" Tech Support Guy...