Fwiw, you don’t really need to worry about your 192.168 address. It’s local to your network. I’m also on 192.168.1.x as it’s the most common internal address scheme for routers. But there are some that use 10.0.1.x or other variations.

We would need to know the external IP address that your ISP gives you to do anything with it. That should definitely be blocked out entirely if it appears in a screenshot or command output.

https://en.wikipedia.org/wiki/Private_network

…that’s the valid response, does ping www.google.com work and curl www.google.com return a bunch of text?

If ping www.google.com doesn’t work then your system isn’t using the correct dns server, though your local dns server works (as seen by the prior dig).

If curl works then…you have a working internet connection, maybe check the browser settings for proxy or something.

You only need one. Standard is to use your router IP as local nameserver.
If your internet provider has issues with name resolutions, which happens sometimes, you can instead set 8.8.8.8 (Google’s nameserver) or 1.1.1.1 (Cloudflare’s nameserver). But then you can’t ping other devices in your local network by name, and loading websites can be a tiny bit slower.

DNS turns a domain name into an IP which can then be used to send data through your router, a dns server is the server which is used to do this conversion (www.google.com turns into an IP 1.2.3.4 (that isn’t the actual IP of google)).

There are many dns servers, normally your local devices use your router as the dns server, which forwards it to your ISP which they further transfer it over global dns servers.

Alternatively you could use Google’s DNS server (8.8.8.8) or cloudflares DNS server (1.1.1.1) but if the one on your router works then just use it.

nameserver is the same as DNS server

Tldr: set the router IP as your dns server, you only need this one.