From owner-freebsd-hackers  Sun Apr  7 07:52:19 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA15200
          for hackers-outgoing; Sun, 7 Apr 1996 07:52:19 -0700 (PDT)
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA15194
          for <hackers@freebsd.org>; Sun, 7 Apr 1996 07:52:16 -0700 (PDT)
Received: (from imb@localhost)
          by asstdc.scgt.oz.au (8.7.5/BSD4.4) id AAA05233
          Mon, 8 Apr 1996 00:51:20 +1000 (EST)
From: michael butler <imb@scgt.oz.au>
Message-Id: <199604071451.AAA05233@asstdc.scgt.oz.au>
Subject: xntpd .. which addresses to listen on
To: louie@TransSys.COM (Louis A. Mamakos)
Date: Mon, 8 Apr 1996 00:51:19 +1000 (EST)
Cc: hackers@freebsd.org
In-Reply-To: <199604071359.JAA01073@whizzo.transsys.com> from "Louis A. Mamakos" at Apr 7, 96 09:59:54 am
X-Mailer: ELM [version 2.4 PL24beta]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Louis A. Mamakos writes:

> What has this to do with ttys?  It's conceivable that you might have an
> external reference clock (GPS, WWVB, etc) which is sending you timestamps
> periodically.  It would be nice to be able to handle these in the same
> sort of way.

Speaking of xntpd, it would be nice if this adopted a similar mechanism as
named to determine the addresses of all the interfaces in a machine.
Specifically, to include alias addresses. 

At the moment, you may have an alias IP number under the same domain name
but in another subnet from the primary. ntp clients will fail (approx) half
the time depending entirely on how quickly the DNS rotates between 'A'
records. This is not useful for an intended accurate time reference,

	michael