I'm currently working on a project that has required some DNS troubleshooting, however. However I am fairly new to the wonderful world of networking and amI'm at a bit of a loss as to where to begin. My
My specific problem probably belongs on the RaspberryPi StackExchangeRaspberry Pi Stack Exchange, so I'll avoid crossposting. JustJust looking for information here.
Looking for information, I was lead to the resolv.conf(5) file, resolvconf(8), systemd-resolve(1), and the beast that avahi appears to be.
My RaspiRaspberry Pi with Raspbian Buster appears to have avahi-daemon running. My
My Ubuntu 18.04.4 LTS has systemd-resolved AND avahi-daemon. Does
Does resolvconf(8) (man page only on Ubuntu) coordinate the two? When
When is /etc/resolv.conf used/ignored?
On Ubuntu:
$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search telus On Raspbian:
$ cat /etc/resolv.conf # Generated by resolvconf nameserver 192.168.0.1 nameserver 8.8.8.8 nameserver fd51:42f8:caae:d92e::1 Which utilities are responsible for this? I
I don't really understand enough jargon to sift through the man pages and differentiate all these, and I'd love an explanation of how their roles are related.
