Fresh Install Win10 "Name resolution for the name wpad timed out" DNS

Hi!

I just did a fresh install of windows 10 x 64. I remained in Build 1709. I did not format the HD, just fresh install. I have a brand new Router/Modem - AT&T Arris. I installed this myself, I installed similar hardware 5-10 times over my life, hooking up cables, I am good at it :) My download is 50Mbps and UP 6-7. I think I did ok installing.

I am getting this problem in Event Viewer, "Name resolution for the name wpad timed out after none of the configured DNS servers responded." This is a home PC, not connected to anything but the internet. It is hardwired. I am not a network admin - just a guy and his PC.

I did the normal things SFC/Scan & Trouble shooter - no luck.... Do I just ignore it? I have a "Latency" issue with a game, could this be the cause?
(Should I identify that PID/Process ID? How do I do that?)
- System

- Provider

[ Name] Microsoft-Windows-DNS-Client
[ Guid] {1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}

EventID 1014

Version 0

Level 3

Task 1014

Opcode 0

Keywords 0x4000000010000000

- TimeCreated

[ SystemTime] 2017-11-25T21:02:00.535593000Z

EventRecordID 884

Correlation

- Execution

[ ProcessID] 2580
[ ThreadID] 4052

Channel System

Computer DESKTOP-9DVSDJF

- Security

[ UserID] S-1-5-20


- EventData

QueryName wpad
AddressLength 128
Address 170000000000000026020304CC87357000000000000000010000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000

By default your router will be set as DNS set pcs to the fast 208.67.220.220. & 208.67.222.222

So I should switch from auto to manual using the opendns you gave?

Samuria said:

By default your router will be set as DNS set pcs to the fast 208.67.220.220. & 208.67.222.222

I never intentionally mean to be dumb. But should I make these changes in my router setup? I found instructions for changing this in router.

I've made changes of this nature once in the last 10 yrs when I tried google DNS. I do not really understand it. Should I concern myself with this error? Or follow your advice and if it works better just move on.