The Connection icon changed to showing a connection, but still no
internet.
So, there's nothing wrong between your device and the "LAN" side of cable-modem. If you use the IPCONFIG command, the output should be similar to:
Ethernet adapter Local Area Connection:
IPv4 Address. . . . . . . . . . . : 10.0.0.133
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . :
**64.59.160.13**
**64.59.161.68**
showing that the cable-modem is on your LAN, using "10.0.0.1", and a DHCP-server has assigned "10.0.0.133" to your device, and showing the DNS-servers your device will query.
Logging-in to the cable-modem, I see:
Internet:Active
WAN IP Address (IPv4):70.66.129.43
WAN Default Gateway Address (IPv4):70.66.128.1
Primary DNS Server (IPv4):64.59.160.13
Secondary DNS Server (IPv4):64.59.161.68
showing that the cable-modem has a "public" IP-address, and communicates with the ISP's router at "70.66.128.1", and uses the same DNS-servers as my device.
Have you tried a power-off/power-on of the cable-modem, to get it to completely "refresh" its connection to your ISP?
We are getting DHCP on both Ethernet and WiFi without issue.
That's perfect communication between your device and the cable-modem.
I am unable to get to anything through DNS
What IP-address(es) do show (as above) for your device, and for the "WAN" side of the cable-modem?
I can navigate via IP and ping 8.8.8.8 outside of the network.
$ ping -4 dns.google
Pinging dns.google [8.8.8.8] with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=14ms TTL=119
Reply from 8.8.8.8: bytes=32 time=11ms TTL=119
Reply from 8.8.8.8: bytes=32 time=11ms TTL=119
Reply from 8.8.8.8: bytes=32 time=10ms TTL=119
**Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)**
Note that my DNS-servers resolved the name "dns.google" to the 8.8.8.8 IP-address. Your output may be different, namely "unable to resolve ...", or something like:
Pinging 8.8.8.9 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
**Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)**
when I PING'd a "nearby" IP-address.
Whatever is happening appears to be DNS related,
Agree, but where is the issue? Maybe, wrong IP-addresses inside the cable-modem for the DNS-servers?
Setting a static IP also did not resolve the issue
nor changing the DNS manually.
That is to be expected, since the problem seems to be "elsewhere", because there is nothing wrong on your device.
Somehow, the responses from the DNS-servers are not reaching your device ("filtering" inside the cable-modem), or Windows on your device is "blocking" those DNS-responses.
Do you have any "Internet Security" packages that might be blocking the responses, such as "Norton 360" or "McAfee"?
Do either of those apps write "log-files" that record each "blocking" action?
Do you (or a friend) have another Windows computer, that you can connect to the cable-modem? If so, does that system function correctly?