The Failure
I cannot access google.com. “Everything” else works (haven’t checked the whole internet and web).
I figured it is a DNS failure, because on one page there is a DNS failure message, where a Google calendar supposed to be.
I can access gmail.com though.
Everything is fine on Safe Zone.
My Attempts
I run the Avast Virus Scan.
With no avail.
I run Spybot Search&Destroy.
Registry entries from Coupon Bar and tracking cookies.
I run Malwarebytes.
On quick scan nothing.
One file found on complete scan: Globe7.exe (Affiliate.Downloader).
My TCP/IP DNS settings are all on automatic still.
HOSTS file redirect/block a common malware tactic to block AV sites making it difficult to remove malware - 127.0.0.1 check your HOSTS file using notepad or a text editor of your choice, C:\WINDOWS\system32\drivers\etc\hosts or do a search for HOSTS to find it if not there.
All that was necessary was that there is no entry for google as that was one possibility that google might have been being blocked. Entries placed there by Spybot S&D are to prevent access to bad sites.
Whilst your other supposition on it being a DNS issue, I wouldn’t have expected that to be only for google.
The safe zone uses its own secure DNS server.
How to Flush DNS in Windows Using the Command Prompt
Step 1 – Close all open web browsers and applications on your computer.
Step 2 – Open the Windows command prompt by selecting the “Start” menu and entering “cmd” in the search text field box followed by clicking the “enter” key.
Step 3 – At the command prompt, enter “ipconfig /flushdns” followed by pressing the “enter” key. After a moment, Windows will display a message similar to: “Successfully flushed the DNS Resolver Cache.” Once the message is displayed, the DNS will be flushed removing all incorrect entries.
As I said “The safe zone uses its own secure DNS server” so that it is isolated from your desktop it is using a secure DNS service which avast has arranged. This also helps against DNS poisoning and using your DNS Cache, which may have bad entries in it.
That is why the suggestion to flush the DNS was given in case the problem was a bad DNS entry.