Date: Sat, 4 Apr 1998 11:18:04 -0800 (PST) From: Tom <tom@uniserve.com> To: Wes Peters - Softweyr LLC <softweyr@xmission.com> Cc: robert+freebsd@cyrus.watson.org, stable@FreeBSD.ORG Subject: Re: Hesiod support on 2.2 Message-ID: <Pine.BSF.3.96.980404111339.17684C-100000@shell.uniserve.com> In-Reply-To: <199804032219.PAA17773@xmission.xmission.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 3 Apr 1998, Wes Peters - Softweyr LLC wrote: > DNS wasn't really designed with a highly volatile dataset in mind. If > it takes a day or two for the existence of a new workstation to trickle No. New records are available immediately. If someone has looked up the record before it was added, there may be some negative cache entries around which will expire in 10 minutes. > across the net, that's generally not too bad, but if it takes a day or > two for my new password to trickle across the net, I cannot reliably > predict if I can login or not. This would involve changing an existing entry, not adding a new entry. This is rather different, because previous version(s) of the record can be cached. > You can, of course, fix this problem by using short expirations on the > zone your login information is stored in, but that doesn't change the > basic design limitation. NOTIFY support in BIND 8.1 helps a lot. Secondaries update immediately now. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980404111339.17684C-100000>