[dns-operations] Unpublished IP addresses for Google Public DNS

[Robert Edmonds]

The original poster's question was whether addresses in 172.217.42.0/24
are being used by Google Public DNS, because they weren't listed in
Google's documentation. That prefix does appear as of now on
https://developers.google.com/speed/public-dns/faq#locations (and the
TXT equivalent), but it looks like it was added recently.

Here's the most recent archive.org capture of that page, from August:

https://web.archive.org/web/20170801000000*/https://developers.google.com/speed/public-dns/faq

It looks like they've added the following prefixes since then:

    172.217.38.0/24
    172.217.39.0/24
    172.217.40.0/24
    172.217.41.0/24
    172.217.42.0/24
    172.217.43.0/24
    172.217.44.0/24
    172.217.45.0/24
    172.217.47.0/24
    2607:f8b0:4020::/48
    74.125.178.0/24
    74.125.185.0/24

and removed this prefix:

    74.125.93.0/24

It also looks like they've allocated prefixes for a new site, YUL. That
probably coincides with this:

https://canada.googleblog.com/2017/03/google-announces-canada-region-for.html

Roy Arends wrote:
> dig TXT locations.publicdns.goog.
> 
> This will give you all addresses of Google’s public dns unicast backend.
> 
> Warmly
> 
> Roy
> 
> > On 19 Oct 2017, at 16:44, Babak Farrokhi <babak at farrokhi.net> wrote:
> > 
> > Hi,
> > 
> > I have seen several addresses from 172.217.42.x as source address from Google resolvers. Here is a list of IPs I’ve seen recently:
> > 
> > 172.217.42.3
> > 172.217.42.4
> > 172.217.42.5
> > 172.217.42.6
> > 172.217.42.7
> > 172.217.42.8
> > 172.217.42.9
> > 172.217.42.10
> > 172.217.42.11
> > 172.217.42.14
> > 
> > 
> > Kind Regards,
> > 
> > -- 
> > Babak Farrokhi
> > 
> > 
> > On 12 Oct 2017, at 3:51, Rajesh Maskara wrote:
> > 
> > Are following two IP addresses used by Google Public DNS for DNS resolution?
> > 
> >                 172.217.42.2
> > 
> >                 172.217.42.4
> > 
> >  
> > 
> > These addresses are NOT included in published ranges:
> > 
> > C:\>nslookup -type=TXT locations.publicdns.goog. | findstr "172.217."
> > 
> > Non-authoritative answer:
> > 
> >         "172.217.32.0/26 lhr "
> > 
> >         "172.217.32.64/26 lhr "
> > 
> >         "172.217.32.128/26 sin "
> > 
> >         "172.217.33.0/26 syd "
> > 
> >         "172.217.33.64/26 syd "
> > 
> >         "172.217.33.128/26 fra "
> > 
> >         "172.217.33.192/26 fra "
> > 
> >         "172.217.34.0/26 fra "
> > 
> >         "172.217.34.64/26 bom "
> > 
> >         "172.217.34.192/26 bom "
> > 
> >         "172.217.35.0/24 gru "
> > 
> >         "172.217.36.0/24 atl "
> > 
> >         "172.217.37.0/24 gru "
> > 
> >  
> > 
> > This is resulting in Traffic Managers like DYN etc to map the end-users incorrectly to CA, USA.
> > 
> >  
> > 
> > Thanks,
> > Rajesh Maskara
> > 
> > Microsoft
> > 
> > _______________________________________________
> > dns-operations mailing list
> > dns-operations at lists.dns-oarc.net
> > https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> > dns-operations mailing list
> > https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> > 
> > _______________________________________________
> > dns-operations mailing list
> > dns-operations at lists.dns-oarc.net
> > https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> > dns-operations mailing list
> > https://lists.dns-oarc.net/mailman/listinfo/dns-operations

> _______________________________________________
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> dns-operations mailing list
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations


-- 
Robert Edmonds