Should we be afraid of Google Public DNS? - TechRepublic
184.108.40.206 | Google LLC | AbuseIPDB IP Abuse Reports for 220.127.116.11: . This IP address has been reported a total of 4 times from 4 distinct sources. 18.104.22.168 was first reported on July 9th 2020, and the most recent report was 2 days ago.. Recent Reports: We have received reports of abusive activity from this IP address within the last week. It is potentially still actively engaged in abusive activities. [SOLVED] Can ping 22.214.171.124 but no google.com - DNS - Spiceworks Jan 06, 2015 domain name system - How did Google acquire 126.96.36.199 The IP addressed 188.8.131.52 (in addition to 184.108.40.206) is now used for Google's DNS server. How did they obtain this IP? Specifically, what has to happen for an IP to be routed to a different location.
DNS forwarders that only point to 220.127.116.11 are using your ISP connection to hop to 18.104.22.168 when resolving DNS. You have a local DNS resolution solution much closer that will speed up requests if used instead. Additionally, if your DNS is set to 22.214.171.124, DNS failures may seem to be an ISP outage when your ISP connection is fine.
See all details about IP 126.96.36.199. | PTR record is dns.google. This IP is hosted by Google LLC (AS15169) and located in the country United States. Should we be afraid of Google Public DNS? - TechRepublic
See all details about IP 188.8.131.52. | PTR record is dns.google. This IP is hosted by Google LLC (AS15169) and located in the country United States.
or provide Google's DNS server IP (any one of them): 184.108.40.206 or 220.127.116.11. nameserver 18.104.22.168** P.S You can understand better how DNS works here. share | improve this answer | follow | edited Dec 28 '18 at 3:58. Pablo Bianchi. 6,022 3 3 gold badges 34 34 silver badges 63 63 bronze badges.