Message-ID: <008301bef945$1cb07aa0$0a1aa8c0@jetnet.co.uk>
From: "David Reid" <abb37@dial.pipex.com>
To: <new-httpd@apache.org>
References: <Pine.BSF.4.05.9909071701420.9027-100000@kim.ispra.webweaving.org>
Subject: Re: (new/old) idea of resolving
Date: Tue, 7 Sep 1999 16:24:37 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Where I sometimes work they have a problem with using dynamic IP allocation
and a desire to review what users have accessed from the internet via their
proxy.  Having the proxy lookup every IP slows the thing to a crawl so they
can't have it on, but without it they can't track who downloaded what!

Might be nice if Apache did offer the functionality, whether as a module or
as a support program using the piped logs?

Just my 2p worth.

david
----- Original Message -----
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
To: <new-httpd@apache.org>
Sent: 07 September 1999 16:08
Subject: Re: (new/old) idea of resolving


>
> 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.
>