Just guessing but could it be that some bots on Verizon are doing mass queries to quad9 and Verizon has something in the path temporarily null routing it on one

Just guessing but could it be that some bots on Verizon are doing mass queries to quad9 and Verizon has something in the path temporarily null routing it on one network segment as to not be blamed for DDoS? Perhaps just on one network egress point and this person was lucky enough to share it with botters? Most bots that reach my devices are on mobile access points or modded cell phones based on their IP characteristics. The null routing could be happening either from Verizon's egress in that segment or from Quad9 blocking that particular SNAT. If they are on their home network this issue can be worked around transparently by using Unbound DNS [1a][1b] and defining multiple upstream providers or just talking to the root servers, whichever makes the most sense in their situation. Unbound can silently retry down servers in the background and prefer {n} percentage of the fastest ones as defined by the admin. [1a] - https://unbound.docs.nlnetlabs.nl/en/latest/ https://unbound.docs.nlnetlabs.nl/en/latest/ [1b] - https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound.conf.html https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound...