NAT IP and Google

Owen DeLong owen at
Wed May 21 18:26:50 UTC 2014

This works out especially well if you are using VOIP behind said NAT. ;-)


On May 20, 2014, at 10:27 AM, Kevin Kadow <kkadow at> 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 "".
> 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.

More information about the NANOG mailing list