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 Date: Tue, 4 Jan 2005 13:08:52 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: How to deal with DHCP and DNS(-tools)? Message-ID: <20050104180852.GA3169@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050103205224 DOT GA2696 AT sesa DOT net> <20050104170442 DOT GA470657 AT Worldnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050104170442.GA470657@Worldnet> User-Agent: Mutt/1.4.1i On Tue, Jan 04, 2005 at 12:04:42PM -0500, Pierre A. Humblet wrote: >On Mon, Jan 03, 2005 at 09:52:24PM +0100, Olaf F?llinger wrote: >>on my notebook with WinXP I'm using cygwin day by day. I receive the >>ip configuration by dhcp from windows. While most of the cygwins tools >>have no problem the dns tools(host, dig,...) seems to insist on a >>working /etc/resolv.conf. Does anyone have a automatic solution for >>updating this file with the current settings? > >You could write a program using minires. It should call res_init to >initialize the _res structure and then print the fields to >/etc/resolv.conf, as sketched below. > >Note that if /etc/resolv.conf exists, then minires will use it in >preference to the Windows values. Thus /etc/resolv must be renamed in >your program. > >Also /etc/resolv.conf will affect applications using minires. On >Win2000 and XP they will call the nameservers specified in >/etc/resolv.conf instead of using the native Windows resolver, except >if the "options" line in /etc/resolv.conf contains the "osquery" >keyword. I wonder if it would make sense to have a /proc/sys/resolv.conf that was autogenerated? Then we could just set up a symbolic link to that file. cgf -- 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/