prameshj

> > any other changes needed to disable default DNSSEC? > > No, that should be it. The commit [373ebff](https://github.com/kubernetes/dns/commit/373ebff7354b7c264c934313f933f6a4cb2aa879) is titled "_Manually_ revert DNSSEC by default in coreDNS". The...

> Perhaps try reverting the entire cache plugin directory to 1.7.0, and see if the 4X cache miss rate is still seen in tests. This would narrow down the cause...

I don't see any obvious changes in forward plugin either. Taking a step back, even if the default dnssec change is the trigger, I don't see any workaround other than...

> > I think the 4x cache misses might be a cascading effect - DO bit somehow causes upstream to slow down, this fails other queries(that could have been successful...

> There are some names in there that would normally be sent to the upstream name servers. e.g. google.com How do the test instances of node-cache handles those queries? Does...

For IPVS mode, the HA solution is to run 2 replicas as described in the KEP: ``` Running 2 daemonsets of node-local-dns using the same listenIP - 169.254.20.10 via SO_REUSEPORT...

> Pavithra -- can you send a PR to add back to the KEP? Yes, already created - https://github.com/kubernetes/enhancements/pull/2592 > Also -- it probably needs to have documentation if this...

> @prameshj: Regarding your comment: > > > requires managing conflicts - only one replica should handle interface/iptables management > > Are there known issues where the two replicas will...

> I have been implementing the above workarounds, but there are still users reporting that they receive the "Unable to process request due to missing initial state. This may happen...

Hi @KishiTheMechanic, are users accessing the web app `https://alpha.epics.dev/` directly from the android browser and seeing the session storage error?