From owner-freebsd-questions@FreeBSD.ORG Wed Jul 11 15:15:03 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8FCA616A46B for ; Wed, 11 Jul 2007 15:15:03 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.freebsd.org (Postfix) with ESMTP id 5B42713C487 for ; Wed, 11 Jul 2007 15:15:03 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: (qmail 30022 invoked from network); 11 Jul 2007 10:15:02 -0500 Received: from 203-206-236-35.dyn.iinet.net.au (HELO localhost) (203.206.236.35) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 11 Jul 2007 10:15:02 -0500 Date: Thu, 12 Jul 2007 01:14:56 +1000 From: Norberto Meijome To: Eric F Crist Message-ID: <20070712011456.016882a2@localhost> In-Reply-To: References: X-Mailer: Claws Mail 2.10.0 (GTK+ 2.10.13; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: User Questions Subject: Re: Some hosting weirdness... 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: Wed, 11 Jul 2007 15:15:03 -0000 On Wed, 11 Jul 2007 07:19:09 -0500 Eric F Crist wrote: > What should I look for? Is there possibly some weird caching issues > at their ISPs? How can I fix this? Differences in DNS replies sounds about the problem . You can bypass DNS by using a hosts file pointing the hostnames to the right IP address. If you find no problem this way, then it's a DNS server issue (unless the machine u are testing has some other issues...but it would be unlikely) You can verify an ISPs own DNS by querying that server in particular (you can usually find their DNS servers in their support pages, or do dig ns [ISP_DOMAINNAME] the answers given may not be the NS used by end users, but should be close enough. If they have an old record in their cache, you should contact their DNS admin / NOC. good luck :) ( I know of one or 2 ISPs here in Oz that (used to?) fix the TTL of zones so they'd save in some traffic...of course, this made a mess of things). The problem may also be if the zones for the domains you are having problems with used to be hosted at those particular ISPs (eg, the ISP NS were the authoritative servers). If you then set other servers as the authoritative without asking the ISPs to clean up, their DNS servers will still be serving (wrongly) authoritative answers with old data. get in touch with them so they remove your zones from their servers. B _________________________ {Beto|Norberto|Numard} Meijome When you just want a system that works, you choose Linux; When you want a system that just works, you choose Microsoft. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.