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

[Rajesh Maskara]

Thanks Babak and Roy. We reached out to Google DNS directly and they have updated the published IP ranges. We are now in process of working with traffic managers to get their databases updated.

Thanks,
~Rajesh Maskara

From: Roy Arends [mailto:roy at dnss.ec]
Sent: Thursday, October 19, 2017 9:48 AM
To: Babak Farrokhi <babak at farrokhi.net>
Cc: Rajesh Maskara <rajmask at microsoft.com>; dns-operations at dns-oarc.net
Subject: Re: [dns-operations] Unpublished IP addresses for Google Public DNS

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<mailto: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<mailto:dns-operations at lists.dns-oarc.net>
https://lists.dns-oarc.net/mailman/listinfo/dns-operations<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.dns-oarc.net%2Fmailman%2Flistinfo%2Fdns-operations&data=02%7C01%7Crajmask%40microsoft.com%7C9f106de253334ca7d76808d517112eba%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636440284929451878&sdata=YkFDmxhWXz07bRrd1we6v4AOim6mQ17vg6wqZU5oscY%3D&reserved=0>
dns-operations mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-operations<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.dns-oarc.net%2Fmailman%2Flistinfo%2Fdns-operations&data=02%7C01%7Crajmask%40microsoft.com%7C9f106de253334ca7d76808d517112eba%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636440284929451878&sdata=YkFDmxhWXz07bRrd1we6v4AOim6mQ17vg6wqZU5oscY%3D&reserved=0>
_______________________________________________
dns-operations mailing list
dns-operations at lists.dns-oarc.net<mailto:dns-operations at lists.dns-oarc.net>
https://lists.dns-oarc.net/mailman/listinfo/dns-operations<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.dns-oarc.net%2Fmailman%2Flistinfo%2Fdns-operations&data=02%7C01%7Crajmask%40microsoft.com%7C9f106de253334ca7d76808d517112eba%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636440284929451878&sdata=YkFDmxhWXz07bRrd1we6v4AOim6mQ17vg6wqZU5oscY%3D&reserved=0>
dns-operations mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-operations<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.dns-oarc.net%2Fmailman%2Flistinfo%2Fdns-operations&data=02%7C01%7Crajmask%40microsoft.com%7C9f106de253334ca7d76808d517112eba%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636440284929451878&sdata=YkFDmxhWXz07bRrd1we6v4AOim6mQ17vg6wqZU5oscY%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20171019/9336d12f/attachment.html>