From owner-freebsd-questions@FreeBSD.ORG Sun Mar 1 08:38:26 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9144F1065675 for ; Sun, 1 Mar 2009 08:38:26 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 63BAE8FC1B for ; Sun, 1 Mar 2009 08:38:26 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.lan.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 14041AFC1FE; Sat, 28 Feb 2009 23:38:26 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Sat, 28 Feb 2009 23:38:25 -0900 User-Agent: KMail/1.9.10 References: <49A95AF8.2060608@gmail.com> <49A969A1.90001@gmail.com> In-Reply-To: <49A969A1.90001@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902282338.25799.fbsd.questions@rachie.is-a-geek.net> Cc: Andrei Brezan Subject: Re: Odd problem with DNS and IP change. 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: Sun, 01 Mar 2009 08:38:26 -0000 On Saturday 28 February 2009 07:43:13 Andrei Brezan wrote: > Andrei Brezan wrote: > > "ping mail.domain.com" it tries to get to 10.1.1.1 the old ip and gets > > time to live exceeded fro an ip along the route. When i try to ping > > domain.com it gets all ok as it pings the new ip. > Disregard my noise. It was a file called hosts in /etc, changed there > the ip for mail.domain.com and now ping works ok. > Sorry about that. As a rule, only use /etc/hosts for hosts that cannot be resolved by DNS (i.e.: local network) or NFS hosts that provide critical filesystems (because the resolver might not be reachable at /etc/rc.d/mountcritremote time). -- Mel Problem with today's modular software: they start with the modules and never get to the software part.