In theory… the number of layers of resolvers shouldn’t increase TTL. Any
resolver that gets an answer from an authoritative servers gets the full
TTL. A downstream resolver that asks for the records from that server’s
cache gets the answers with the TTL appropriately decremented. Any
additional lay
Yawn.
Been there, done that. Why do you think the other public mail services have
switched over so quickly ? :)
This is exclusively a gmail problem.
On Saturday, 10 August 2024 at 15:28, Suresh Ramasubramanian
wrote:
> Look at it this way, anywhere that has resolvers forwarding to other
>
Look at it this way, anywhere that has resolvers forwarding to other resolvers
that forward to yet another set of resolvers before the query gets to the root
servers (anywhere with a complex network and multiple layers of firewalling)
will have a succession of caches that need to clear .. so mig
In typical "Google knows best" style they appear to be ignoring SOA and TTL and
doing their own thing.
Changed DNS severs and MX records, other public mail services have picked it up
no problem.
Gmail however appear to be insisting on continuing to deliver to the old mail
servers for god knows
4 matches
Mail list logo
