From owner-freebsd-questions Wed Sep 23 08:28:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13689 for freebsd-questions-outgoing; Wed, 23 Sep 1998 08:28:22 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13677 for ; Wed, 23 Sep 1998 08:28:20 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id IAA05004; Wed, 23 Sep 1998 08:26:59 -0700 (PDT) (envelope-from dhw) Date: Wed, 23 Sep 1998 08:26:59 -0700 (PDT) From: David Wolfskill Message-Id: <199809231526.IAA05004@pau-amma.whistle.com> To: dhw@whistle.com, mirlok@acmail.ab.az Subject: Re: dns Cc: jacques@wired.ctech.ac.za, questions@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Wed, 23 Sep 1998 13:55:11 +0500 (AZST) >From: Mirlok >And after I change it, how much time should pass before the others will >see it? Standard answer number 0: It depends. In this case, it depends on when the others cached it, and the value you had in the TTL of the SOA record. Or, if you have influence with the right folks (sysadmins, typically, of the other systems in question), they might be willing to flush their nameservers caches manually, thus forcing their systems to fetch the information upon next request. However, they should do this only after you're certain that any secondary nameservers have already got the new information; from the perspective of J. Random System out there, "primary" and "secondary" nameservers for a given zone are equally authoritative. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message