DNS, again... or probably not...
Nov. 9th, 2016 10:28 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
alexpgpI've been experiencing what Windows diagnoses as DNS problems on and off for the past few days, to the point where it's become quite an annoyance.
DNS stands for Domain Name Service, and turns easy-to-remember domain names (like "livejournal.com") into the language of the Internet, which consists solely of numbers (in the case of LiveJournal, that'd be "208.93.0.150"). And if your computer is connected to the 'net, there's a reference in your computer's network configuration to another computer whose sole purpose is to "serve up" the appropriate numbers when provided a domain name, hence the name "server."
I tried to change the DNS servers in my computer's network configuration to Google's "Public DNS Servers" (with IP addresses 8.8.8.8 and 8.8.4.4), but strangely enough, I kept getting the DNS error.
When I left for the pen club meeting, there were three Comcast trucks parked at various points along my street. I suspect someone finally figured out what was wrong. What it may have been, I have no idea. But as this post suggests, the problem appears to have been fixed.
Cheers...
DNS stands for Domain Name Service, and turns easy-to-remember domain names (like "livejournal.com") into the language of the Internet, which consists solely of numbers (in the case of LiveJournal, that'd be "208.93.0.150"). And if your computer is connected to the 'net, there's a reference in your computer's network configuration to another computer whose sole purpose is to "serve up" the appropriate numbers when provided a domain name, hence the name "server."
I tried to change the DNS servers in my computer's network configuration to Google's "Public DNS Servers" (with IP addresses 8.8.8.8 and 8.8.4.4), but strangely enough, I kept getting the DNS error.
When I left for the pen club meeting, there were three Comcast trucks parked at various points along my street. I suspect someone finally figured out what was wrong. What it may have been, I have no idea. But as this post suggests, the problem appears to have been fixed.
Cheers...
