[188627] in North American Network Operators' Group
Re: Stop IPv6 Google traffic
daemon@ATHENA.MIT.EDU (Brielle)
Sun Apr 10 11:51:06 2016
X-Original-To: nanog@nanog.org
From: Brielle <bruns@2mbit.com>
In-Reply-To: <20160410153100.GA17394@lboro.ac.uk>
Date: Sun, 10 Apr 2016 09:50:58 -0600
To: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
(Sorry about formatting - posting on my phone)
Other things might need to make sure of is reverse DNS to differentiate betw=
een customers if at all possible, accurate Whois and separate Whois records f=
or static assigned blocks, etc.
No guarantees of a fix, but general good practices when this stuff comes up.=
Sent from my iPhone
> On Apr 10, 2016, at 9:31 AM, A.L.M.Buxey@lboro.ac.uk wrote:
>=20
> Hi,
>> The problem is IPv6-enabled customers complaints see captcha, and Google
>> NOC refuses to help solve it saying like find out some of your customer
>> violating some of our policy. As you can imagine, this is not possible.
>=20
> your customers are getting AAAA addresses when looking up google addresses=
...so their
> clients are trying to use IPv6 to talk to google..... so doing anything to=
that traffic - blackholing
> or just denying it, WILL affect the clients.=20
>=20
> give clients their own bigger blocks - or identify the clients violating p=
olicy (what the policy
> they are violating?) - you'll probably find the ones getting the captchas a=
re the ones violating! ;-)
>=20
> alan
