Re: NAT IP and Google
They take out our campus, both IPv4 and IPv6. All hailing attempts fail. Good luck. On Tue, May 20, 2014 at 8:21 AM, Pui Edylie <email@edylie.net> wrote:
Hi Everyone,
May I know what is the best approach so that Google would not ban our Natted IP from time to time as it suspect it as a bot.
Is there any official channel from Google which we could work with them for resolution?
Thanks much!
Best, Edy
-- Copyright 2014 Derek Andrew (excluding quotations) +1 306 966 4808 Information and Communications Technology University of Saskatchewan Peterson 120; 54 Innovation Boulevard Saskatoon,Saskatchewan,Canada. S7N 2V3 Timezone GMT-6 Typed but not read.
Their determination is based on the type of search traffic more than the volume. I had some success using squid to proxy through to them and reduce the overall number of complex queries. On May 20, 2014, at 10:10 AM, Derek Andrew <Derek.Andrew@usask.ca> wrote:
They take out our campus, both IPv4 and IPv6.
All hailing attempts fail.
Good luck.
On Tue, May 20, 2014 at 8:21 AM, Pui Edylie <email@edylie.net> wrote:
Hi Everyone,
May I know what is the best approach so that Google would not ban our Natted IP from time to time as it suspect it as a bot.
Is there any official channel from Google which we could work with them for resolution?
Thanks much!
Best, Edy
-- Copyright 2014 Derek Andrew (excluding quotations)
+1 306 966 4808 Information and Communications Technology University of Saskatchewan Peterson 120; 54 Innovation Boulevard Saskatoon,Saskatchewan,Canada. S7N 2V3 Timezone GMT-6
Typed but not read.
If at all possible, consider using a NAT pool instead of translating all outbound web traffic to a single IP address. When I ran Tribune's network (with about 15K internal client IPs), we were blacklisted by Google several times due to high query volumes. In the end I built a pair of /24 NAT pools, so for example all internal 10.x.y.124 addresses are translated to "kevin.nat.trb.com". In my experience, Google does temporary blacklisting based both on rate and also for certain types of queries; you can reduce your chance of a ban by using a smart proxy to rate-limit or deny certain types of query, or to choose the source address based on the URL requested, basically have a "low risk" and a "high risk" source address.
This works out especially well if you are using VOIP behind said NAT. ;-) Owen On May 20, 2014, at 10:27 AM, Kevin Kadow <kkadow@gmail.com> wrote:
If at all possible, consider using a NAT pool instead of translating all outbound web traffic to a single IP address. When I ran Tribune's network (with about 15K internal client IPs), we were blacklisted by Google several times due to high query volumes. In the end I built a pair of /24 NAT pools, so for example all internal 10.x.y.124 addresses are translated to "kevin.nat.trb.com".
In my experience, Google does temporary blacklisting based both on rate and also for certain types of queries; you can reduce your chance of a ban by using a smart proxy to rate-limit or deny certain types of query, or to choose the source address based on the URL requested, basically have a "low risk" and a "high risk" source address.
participants (4)
-
Chris Garrett -
Derek Andrew -
Kevin Kadow -
Owen DeLong