From owner-freebsd-net@FreeBSD.ORG Sat Mar 17 18:14:14 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A2FD916A406 for ; Sat, 17 Mar 2007 18:14:14 +0000 (UTC) (envelope-from freebsd@southportcomputers.co.uk) Received: from ivy.southportcomputers.co.uk (ivy.southportcomputers.co.uk [82.195.155.161]) by mx1.freebsd.org (Postfix) with ESMTP id 2D69B13C465 for ; Sat, 17 Mar 2007 18:14:13 +0000 (UTC) (envelope-from freebsd@southportcomputers.co.uk) Received: from ivy.southportcomputers.co.uk (localhost [127.0.0.1]) by ivy.southportcomputers.co.uk (8.14.0/8.13.4) with ESMTP id l2HIECHc099068 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Sat, 17 Mar 2007 18:14:12 GMT (envelope-from freebsd@southportcomputers.co.uk) Received: (from www@localhost) by ivy.southportcomputers.co.uk (8.14.0/8.13.6/Submit) id l2HIE6De099067; Sat, 17 Mar 2007 18:14:06 GMT (envelope-from freebsd@southportcomputers.co.uk) X-Authentication-Warning: ivy.southportcomputers.co.uk: www set sender to freebsd@southportcomputers.co.uk using -f Received: from 84.92.113.93 (SquirrelMail authenticated user scomp) by mail.southportcomputers.co.uk with HTTP; Sat, 17 Mar 2007 18:14:06 -0000 (GMT) Message-ID: <49641.84.92.113.93.1174155246.squirrel@mail.southportcomputers.co.uk> In-Reply-To: References: Date: Sat, 17 Mar 2007 18:14:06 -0000 (GMT) From: "Colin Waring" To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: Troubleshooting aliases. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2007 18:14:14 -0000 Thanks to anyone who had a think about this one. It appears the cause is a bit simpler than thought. Quite simply, the hosting centre have apparantly allocated the IP addresses to someone else so whilst there is something responding, it isn't actually the right machine. Numpties. :) Regards, Colin.