On 15/04/15 16:05, Brian Rak wrote:
We noticed that we're no longer getting results back for google.com
when we do queries from a few of our recursive servers (other ones are
fine).
A bit of searching revealed that a few of our servers are listed here
We noticed that we're no longer getting results back for google.com
when we do queries from a few of our recursive servers (other ones are
fine).
A bit of searching revealed that a few of our servers are listed here
http://www.google.com/intl/en_ALL/ipv6/statistics/data/no_.txt
On 4/15/2015 11:28 AM, Phil Mayers wrote:
On 15/04/15 16:05, Brian Rak wrote:
We noticed that we're no longer getting results back for google.com
when we do queries from a few of our recursive servers (other ones are
fine).
A bit of searching revealed that a few of our servers are listed
I suggest checking if any of your affected users have broken 6to4 setups,
and that you are applying the relevant mitigations in RFC 6343.
MTU size issues and high latency have also both been mentioned as
possible reasons for the mysterious blacklist.
It has also been said that
And you are not alone... While my employer has deployed a lot of IPv6
internally (still not 100% though), some internal DNS servers are
blacklisted by Google. Probably because a lot of our internal labs (which
are also IPv6-enabled of course) are managed by the engineers using the
lab, so, ending
