Great, I agree that it is because traffic from x.x.x.1 is taking a different path than x.x.x.2 likely because of a load balancing technique which has some dependency on source ip. I’ve posted the issue in Google’s issue tracker. Thanks for the help! On May 23, 2014, at 10:57 AM, Scott Berkman <scott@sberkman.net> wrote:
Check out this page and the link from there to the Google Public DNS User Group or the Issue Tracker for reporting issues:
https://developers.google.com/speed/public-dns/docs/using?csw=1#troubleshoot...
Hope that helps,
-Scott
On 05/23/2014 03:31 AM, Blake McKeeby wrote:
I have a /24 in an Internap colo and use Google Resolver 8.8.8.8 on all my machines. Google will not consistently respond to RDNS lookups from source IP X.X.X.1 but will respond consistently if I change the IP address of the machine to X.X.X.2. I have proven the DNS response is never returned using tcpdump. It's positively not a local networking issue as changing my resolver to 4.2.2.2 (Level 3) while the machine uses X.X.X.1, the RDNS responses arrive without fail.
Has anyone else seen this sort of selective response by Google? Do they maintain some sort of black list?
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages