[ntpwg] [dhcwg] NTP option: IP address and/or FQDN

[anthony.flavin at bt.com]

Except the name server will only get the request once (assuming it
resolves to something), Whereas the Hard-coded IP address would be
getting a request every 64 seconds or so. Much less traffic.

All of this misses the point though. If a manufacturer does something
really dumb, as they have in the past, then their are problems for all.
However, I don't think that this is solvable within the NTP
specification itself. The best answer is education as a carrot and the
threat of a whole load of bad press as a stick.

Tony Flavin


-----Original Message-----
From: ntpwg-bounces+anthony.flavin=bt.com at lists.ntp.org
[mailto:ntpwg-bounces+anthony.flavin=bt.com at lists.ntp.org] On Behalf Of
Ted Lemon
Sent: 13 December 2007 02:38
To: Danny Mayer
Cc: DHC WG; Ralph Droms (rdroms); NTP Working Group
Subject: Re: [ntpwg] [dhcwg] NTP option: IP address and/or FQDN


On Dec 12, 2007, at 7:28 PM, Danny Mayer wrote:
> There is an even simpler solution to this. Have the DNS name remain
> but
> have it point to 127.0.0.1 or ::1. That way only itself is impacted.

That doesn't stop the traffic to the name server.


_______________________________________________
ntpwg mailing list
ntpwg at lists.ntp.org https://lists.ntp.org/mailman/listinfo/ntpwg