[dns-operations] new public DNS service: 220.127.116.11
damian at google.com
Mon Nov 20 17:21:53 UTC 2017
On Mon, Nov 20, 2017 at 7:58 AM, A. Schulze <sca at andreasschulze.de> wrote:
> Am 20.11.2017 um 13:08 schrieb Damian Menscher:
> > 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.
> is there an easy way to identify an answer from a resolver (aka 18.104.22.168)
> as an answer from Google?
> "dig @22.214.171.124 hostname.bind. txt chaos" would be a weak indicator for
> but unfortunately, Google don't respond to such queries.
Given the intent is to detect malicious hijacking, I'm not sure posting a
query that can be imitated by others is useful. Instead, I recommend
running a traceroute and confirming the path enters Google's network before
reaching the final host.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dns-operations