Are you still seeing any issues with queries via 8.8.8.8 or 8.8.4.4? If so, can you post some example failures seen via "dig"? The issues seen via DNSViz were:
* Known broken support for empty non-terminals (ENTs) at AWS. This does not affect Google Public DNS, which for now (along with many other resolvers) tolerates the AWS misbehaviour. You could switch to a DNS operator that implements ENTs correctly, if you wish.
* An spurious report of an MTU issue between DNSViz and G-ROOT when resolving the DS records for .BR. This was likely transient packet loss. The actual reply "BR. IN DS ?" from the G-ROOT is only ~400 bytes.
* Mostly harmless glue AAAA records for one of the nameservers of "
vtech.com"
Refreshing the
DNSViz data eliminates the spurious MTU issue. None of the issues are related to Google Public DNS. What actual problem are you trying to solve? Please show some queries to Google Public DNS and corresponding responses, that occur with some regularity and produce unwanted results.