On 2022 Feb 27, at 05:46, Bob McDonald wrote:
> I'm guessing that the zone files hosted on the new DNS servers still contain
> NS records pointing to the old DNS servers.
After propagation everything seems to have settled out properly, no errors on
dnsviz now.
Thanks though.
--
Advance and
I'm guessing that the zone files hosted on the new DNS servers still
contain NS records pointing to the old DNS servers.
Based on your post, that's my guess.
Bob
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software
Is this a result of the propagation of DNS still occurring and dnsviz still
seeing the old DNS servers? The DNS pointers have been changed with the
registrar, but dnsviz is throwing quite a few errors, including this one.
"DNSKEY: The Authoritative Answer (AA) flag was not set in the res
The answers will be cached regardless of the setting of the AA flag. I
would suspect that most -- or at least a large percentage -- of DNS
queries made by endpoint clients are to upstream resolvers which don't
happen to be authoritative for the zone(s) in question, so AA=0 is very
common
In message 4d2d0689.7010...@chrysler.com, Kevin Darcy writes:
The answers will be cached regardless of the setting of the AA flag. I
would suspect that most -- or at least a large percentage -- of DNS
queries made by endpoint clients are to upstream resolvers which don't
happen
These triggered the release of 9.7.2-P1
when we were rejecting these after tightening the response processing
to treat glue to answer responses as referrals to address the issue
of named return glue records from the parent zones rather than the
actual answers in the child zones.
Sorry I'm not
Hello,
I'm not sure about, is it true that only the response which has included
the aa in flags can be cached by client DNS Cache?
For example, for my domain, there are two queries below, the result for the
first query won't be cached, but the second will be cached, am I right?
$ dig
7 matches
Mail list logo