From ArchWiki
Jump to: navigation, search

UncensoredDNS port numbers

I am wondering whether the information on port 53 & 5353 is relevant or of any interest. Isn't it multicast that uses UDP on 5353? Some reference would be welcome. I would happily rewrite the paragraph if there is no objection. Kewl (talk) 20:45, 29 September 2017 (UTC)

I have found an announcement from ‏ @censurfridns 8 Dec 2013 on Twitter "Due to popular request ns1 and ns2 now listen on port 5353 as well as the standard 53, for those of you with ISPs hijacking port 53 traffic!" and have checked it is still the case with the new servers and will therefore update accordingly Kewl (talk) 08:57, 30 September 2017 (UTC)


I think this page deserves an overhaul. I am thinking of renaming the article to DNS configuration, moving Network configuration#Resolving domain names here, rewriting and moving systemd-resolved up as it's the DNS client Arch Linux systems use and outsourcing the NetworkManager and dhcpcd specific sections to their respective articles. As I have stated in Help talk:Template#Creation of Template:Out of scope I don't think a list of DNS servers belongs on the ArchWiki, but I won't touch the section till we reach a consensus.--Larivact (talk) 18:08, 20 May 2018 (UTC)

I introduced systemd-resolved here and I agree it deserves more room. Then I am not clear about "DNS configuration", is it the configuration to build a DNS server or is it using it as a client or both. I am not sure this is the most understandable title about what you want to move in there but to be discussed. Then about dropping the list of DNS servers I disagree, it has been growing and has attracted interest, it is I think becoming a reference of concise list of alternative DNS servers. That it can be arranged differently I am sure but I don't see what dogma would prevent us from maintaining such a useful reference in the Arch wiki. This is an external service the Arch system relies on, having an unsecured or slow resolution is something that is affecting the system directly and that should be well addressed. -- Kewl (talk) 19:05, 20 May 2018 (UTC)
Good point, DNS resolver would be better. I guess the dogma would be preventing scope creep. Yes Arch systems use DNS servers but so do any other operating systems.--Larivact (talk) 19:22, 20 May 2018 (UTC)
The systemd-resolved.service is not active unless you enable it, so it is not "the DNS client Arch Linux systems use" and does not deserve any more space than other tools. As for "outsourcing" NetworkManager and dhcpcd sections, they deserve as much space as systemd-resolved on this page - it doesn't make sense to keep only some DNS configuration on this page. -- Lahwaacz (talk) 19:58, 20 May 2018 (UTC)
Thanks for clearing that up. systemd-resolved however is a DNS resolver while NetworkManager and dhcpcd just change /etc/resolv.conf.--Larivact (talk) 20:04, 20 May 2018 (UTC)
And systemd-resolved is arguably part of systemd-networkd which is just another network manager. -- Lahwaacz (talk) 20:36, 20 May 2018 (UTC)
The point is that systemd-resolved does resolving while NetworkManager and dhcpcd don't.--Larivact (talk) 20:42, 20 May 2018 (UTC)
They use the resolv.conf config file which is still the central topic of this page even if you rename it. Moving the sections to different pages would either be totally out of place or you would have to move (and duplicate) a considerable part of this page. -- Lahwaacz (talk) 21:22, 20 May 2018 (UTC)
I was thinking of moving and linking the sections. NetworkManager configuration belongs to the NetworkManager article and dhcpcd configuration belongs to the dhcpcd article.--Larivact (talk) 04:02, 21 May 2018 (UTC)
What I meant is that the current information on systemd-resolved is pretty light and it deserves more elaborated comments given the different configuration possibilities. We have to see where we develop it, not here if we want to keep the balance with the other network tools and keep the focus on resolv.conf, probably in systemd-networkd then. -- Kewl (talk) 03:55, 21 May 2018 (UTC)
Moving systemd-resolved to systemd-networkd doesn't make sense as systemd-resolved can be used without systemd-networkd.--Larivact (talk) 07:29, 21 May 2018 (UTC)

Kewl said that they are "not clear about DNS configuration, is it the configuration to build a DNS server or is it using it as a client or both." I thought about renaming the article to DNS resolver but that's actually ambiguous as any DNS server is also a DNS resolver. I still consider DNS configuration the best title as it's about configuring the DNS of an Arch Linux system, just like Network configuration is about configuring the network of the host.

So I propose to move resolv.conf to DNS configuration and make the article describe NSS hosts, /etc/hosts, resolv.conf, and DNS lookup utilities like dig & drill.

Sections I want to move to DNS configuration:

Sections I want to move from resolv.conf (but still link from DNS configuration):

--Larivact (talk) 12:30, 21 May 2018 (UTC)