techsupport

3211 readers

1 users here now

The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.

If something works or if you find a solution to your problem let us know it will be greatly apreciated.

Rules: instance rules + stay on topic

Partnered communities:

You Should Know

Software gore

Recommendations

founded 3 years ago

MODERATORS

GatoB@lemmy.world

[DNS] Cannot resolve domain names with router address 192.168.1.1 (piefed.blahaj.zone)

submitted 1 month ago* (last edited 1 month ago) by akunohana@piefed.blahaj.zone to c/techsupport@lemmy.world

2 comments fedilink hide all child comments

The router has a DNS configured and works with all other devices.

Public DNS, such as 9.9.9.9, do work.

I'm using OpenRC's netifrc (a script brings up my network interface) on Artix Linux (Arch based).

you are viewing a single comment's thread
view the rest of the comments

[–] tal@lemmy.today 0 points 1 month ago (1 children)

The router has a DNS configured and works with all other devices.

I'm not sure what this means. You mean that you have multiple devices, and you've set multiple of them up to use 192.168.1.1 as a DNS server, and some work and some don't? Or you just mean that the other devices work in that they can access the Internet, and aren't using 192.168.1.1 as a DNS server?

If you've got a Linux system, the basic tools I'd probably use as a first pass are dig, which is a utility that provides a fair bit of information about what's going on, bypasses your system resolver, and is often used for diagnosing DNS issues, and tcpdump, which will let you see what is going by at the network level. On Debian-family systems, dig is in the package bind9-dnsutils, and tcpdump is in the tcpdump package.

In one terminal:

$ sudo tcpdump udp port 53 and host 192.168.1.1

That'll start printing a summary of DNS traffic to and from the Linux box and the router.

In another:

$ dig www.google.com @192.168.1.1

That'll let you see if the query is timing out or what-all is going wrong, and it'll ensure that you don't have some client-side configuration issue, since you aren't using your system resolver.

[–] akunohana@piefed.blahaj.zone 1 points 1 month ago

I’m not sure what this means. You mean that you have multiple devices, and you’ve set multiple of them up to use 192.168.1.1 as a DNS server, and some work and some don’t? Or you just mean that the other devices work in that they can access the Internet, and aren’t using 192.168.1.1 as a DNS server? The former. All my devices use my router at 192.168.1.1 as a DNS server and resolution works on them (smartphone, another PC, yet another smartphone...). For some reason, it's only my Artix system that won't successfully ping domain names. Meanwhile, the package manager (pacman) resolves repo domain fine, so, MYSTERY. xD

Thank for all the advice! I haven't had the time to try any of them yet - having started on another (Commodore 64) project and whatnot - but I'll check them out when I can. :)