Windows 10: studio.youtube.com Err Name Not Resolved 105 Google DNS Resolver False Time 5:21 PM

Delete YouTube Channel Button is Gone in YouTube SettingsDelete your Google Account Button is Gone in Google AccountNo Internet Access Coming Time 4:21 PM iPhoneN iPhone Huawei P20 Pro

:)

 

dns resolve not existent names to strange ip

It has been a long time that my computer resolve names to strange ip when resolving not existent names.

For example today ping pippo.pluto.paperino resolves to ip
173.45.161.113 (see below).

Has anybody ever experienced this phenomenon, sometimes very annoying (ie test for unreachable host or in presence of DNS search list with multiple domain)?

Thank you in advance for every suggestion and help

Pietro

ping pippo.pluto.paperino

Pinging pippo.pluto.paperino [173.45.161.113] with 32 bytes of data:

Request timed out.

Ping statistics for 173.45.161.113:

Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),

Control-C

^C

 

DNS not resolved on material.angularjs.org

Okay, you got me with this, but since it doesn't open from google search either, this doesn't resolve my problem.

material.angularjs.org
----------------------------------------
Record Name . . . . . : material.angularjs.org
Record Type . . . . . : 5
Time To Live . . . . : 472
Data Length . . . . . : 8
Section . . . . . . . : Answer
CNAME Record . . . . : angular-material.firebaseapp.com




Record Name . . . . . : angular-material.firebaseapp.com
Record Type . . . . . : 5
Time To Live . . . . : 472
Data Length . . . . . : 8
Section . . . . . . . : Answer
CNAME Record . . . . : s-cert-1.firebaseapp.com




Record Name . . . . . : s-cert-1.firebaseapp.com
Record Type . . . . . : 1
Time To Live . . . . : 472
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 23.235.33.171




Record Name . . . . . : s-cert-1.firebaseapp.com
Record Type . . . . . : 1
Time To Live . . . . : 472
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 23.235.37.171

C:\Windows\system32>ping material.angularjs.org


Pinging s-cert-1.firebaseapp.com [23.235.33.171] with 32 bytes of data:
Reply from 23.235.33.171: bytes=32 time=26ms TTL=51
Reply from 23.235.33.171: bytes=32 time=25ms TTL=51
Reply from 23.235.33.171: bytes=32 time=25ms TTL=51
Reply from 23.235.33.171: bytes=32 time=25ms TTL=51


Ping statistics for 23.235.33.171:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 26ms, Average = 25ms





So looks like DNS is resolved and I get the valid IP now. But still cannot access the site.

 

Windows 10 local DNS names intermittently not resolving

Ever since I upgraded my Windows 7 Pro machine to Windows 10 Pro, I have intermittent issues resolving local DNS names. I've checked my primary and secondary DNS servers and the logs don't show any issues that would point to a potential issue on the server
side. I can ping IP addresses with no problem and internet names are resolving normally, but the local DNS names won't resolve. I end up having to run 'ipconfig /flushdns' to get local DNS to resolve correctly. Is my local DNS cache resolver data becoming
corrupted? What could be causing this? Any ideas?