On Mar 12, 2013, at 10:48 PM, Markku Miettinen su...@surfa.name wrote:
This is absolutely the way that a client SHOULD NOT work and this is what
many OS and application developers with IETF have been trying to shoot down
for years. It is not how IPv6 works as stated one of latter e-mails.
Am 12.03.13 22:48, schrieb Markku Miettinen:
This is absolutely the way that a client SHOULD NOT work and this is
what many OS and application developers with IETF have been trying to
shoot down for years. It is not how IPv6 works as stated one of latter
e-mails.
No no no. It works exactly as
Mouse wrote:
There is NOTHING in the DNS protocol for a client to signal that it prefers $
Isn't that what the QTYPE is for?
As far as I can tell, the only way to ever get both A and in the
answer section to a single query is to query for type ANY, which isn't
usually done because of
Fabian Wenk kirjoitti:
I am not sure if the traffic pattern change I see on two of my NTP
server have something to do with this DNS update or not.
Please have a look at the graphs at [1]. Since March 1st (Friday) I see
a higher base level of requests on ntp1 + ntp3.home4u.ch and also lower
As far as I can tell, the only way to ever get both A and in
the answer section to a single query is to query for type ANY [...]
According to the original RFC1035 DNS protocol specification, the
question section of the DNS request packet can contain any number of
queries, usually 1 it
On Tue, Mar 12, 2013 at 07:49:33PM -0700, Ask Bjørn Hansen wrote:
On my TODO are adding some new features to the vendor zones
(*.fedora.pool.ntp.org, etc) so the vendor can choose if their clients are
SNTP or NTP clients, if they want IPv6, if they use the pool or server
configuration for
