[dns-operations] new public DNS service: 220.127.116.11
damian at google.com
Mon Nov 20 12:08:15 UTC 2017
On Mon, Nov 20, 2017 at 3:47 AM, Florian Weimer <fweimer at redhat.com> wrote:
> On 11/18/2017 09:11 AM, Damian Menscher wrote:
>> Your argument that you don't trust the ISPs between you and
>> Google/OpenDNS/Quad9, and therefore run your own local recursive resolver,
>> confuses me. After all, your local recursive needs to query third-party
>> authoritative servers anyway.
>> To convince yourself, answer these two questions:
>> - How many ISPs are between you and 18.104.22.168? I'm on Comcast, and they
>> have direct peering with Google, so the number is zero.
> 22.214.171.124 is increasingly seen as an anycast service address for DNS
> unrelated to Google, similar to how you download the SSH keys for root
> login from 169.254.169.254 or instance-data. I expect that many ISPs route
> 126.96.36.199 to their own servers.
Unlike 169.254/16 which is defined by RFC to be link-local, 188.8.131.52/24 has
been allocated to Google.
If you identify instances of BGP hijacking please report either privately
to the victim (Google in your example) or publicly to the nanog mailing
list, so corrective action can be taken.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dns-operations