Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 13701 invoked by uid 6000); 7 Sep 1999 15:09:54 -0000 Received: (qmail 13442 invoked from network); 7 Sep 1999 15:09:48 -0000 Received: from va-165.skylink.it (HELO kim.ispra.webweaving.org) (194.185.55.165) by taz.hyperreal.org with SMTP; 7 Sep 1999 15:09:48 -0000 Received: from kim.ispra.webweaving.org (kim.ispra.webweaving.org [10.0.0.2]) by kim.ispra.webweaving.org (8.8.8/8.8.5) with ESMTP id PAA16836 for ; Tue, 7 Sep 1999 15:08:43 GMT X-Passed: MX on Ispra.WebWeaving.org Tue, 7 Sep 1999 15:08:43 GMT and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Tue, 7 Sep 1999 15:08:43 GMT Date: Tue, 7 Sep 1999 17:08:42 +0200 (CEST) From: Dirk-Willem van Gulik X-Sender: dirkx@kim.ispra.webweaving.org To: new-httpd@apache.org Subject: Re: (new/old) idea of resolving In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Tue, 7 Sep 1999, Rasmus Lerdorf wrote: > Why? DNS is not a transient thing. Though some idiots^H^H^H^Hclever people are starting to do things like using quick DNS updates to for example assign very short lived reverse mappings to constantly changing dhcp or ppp addresses. Dynamic DNS Update is a mixed blessing. I.e. while a customer is on line, or while a machine has been dhcp-ed in, its reverse address it is nicely called 'customername.we.trust.you.com' or somthing like that. After log-off the mapping is removed. I've had two US customers who wanted me to implement this for them, tied in with security and xs control based on the short lived fqhn. And looking at the next windows release, that is what some security seems to start rely on. Going be nice to see the battle over which IT staff gets to run the authoritative DNS servers; as for some things you might really want to keep it close/on your NT domain controller. So there is some argument for resolving relatively quickly; though of course some DNS implementations their caches are hopelessly broken when the TTL < 15 minutes. So it cannot be that quick. Yet. Dw.