From owner-freebsd-questions Fri Oct 26 12:31: 6 2001 Delivered-To: freebsd-questions@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 119C837B401 for ; Fri, 26 Oct 2001 12:31:00 -0700 (PDT) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id f9QJSFU59307; Fri, 26 Oct 2001 12:28:15 -0700 (PDT) (envelope-from dg) Date: Fri, 26 Oct 2001 12:28:15 -0700 From: David Greenman To: Tomek Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Weird ns.freebsd.org DNS problem Message-ID: <20011026122815.E58218@nexus.root.com> References: <3BD99DFF.119A1163@calcon.net> <003901c15e4a$06c2b8e0$f6f073d1@mpionline.com> <012001c15e54$28a2b460$f6f073d1@mpionline.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <012001c15e54$28a2b460$f6f073d1@mpionline.com>; from tomek@mpionline.com on Fri, Oct 26, 2001 at 01:26:45PM -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >I'm sorry, I misposted that last one, here it is correctly: > >Hello there, >The domain movierate.com is supposed to point to 209.115.240.249, and my >FreeBSD run DNS (builtin namedb) shows it as such BUT ns.freebsd.org >shows a non-authoritative answer as 209.115.240.247. Other servers (such >as ns1.earthlink.net, ns2, ns3, but not ns4.earthlink.net) show the same >247 address. > >(our DNS server is ns.mpionline.com or ns.movierate.com) > >It has been like this a LONG time, making movierate.com basically >unreachable to half the world, and I have tried everything from changing >serial numbers of domain info to cname aliasing, and even changing >registrars. > >PLEASE HELP, I'm at a complete loss with this one. Why is it pointing to >the wrong place? How can I force a name server to update itself from the >authoritative answer? The problem is caused by Network Solutions/Verisign having a HOST record for movierate.com. You need to delete the HOST record in their database in order to fix the problem. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message