unbound does so also
Anything known-port which is potentially serviced by a daemon in the base
must be listed in /etc/services, so that it can be added to the
net.inet.{tcp,udp}.baddynamic lists at boot by /etc/rc.
Otherwise, the random port allocator (reserved, non-reserved, and high)
may allocate it for other uses before that service gets started, therefore
it will fail.
I need to add I worry for the future, the 512-1023 reserved space is
being gobbled at a rapid pace by new services, which not only decreases
the port# entropy but reduces the total number of reserved ports which
can be allocated. Fewer software services allocate reserved ports
today, but it isn't a dead concept either, and people are likely to run
more instances of software since machines got bigger. I wonder if any
old service entries can be can be purged.
> I know all the limitations with adding new stuff to services(5) but now
> that a base software (unwind) implements DoT, would it make sense to
> add it to services(5)?
>
> Regarding the comments, I went with the wording from the iana website.
>
>
> Cheers,
> Daniel
>
> Index: services
> ===================================================================
> RCS file: /cvs/src/etc/services,v
> retrieving revision 1.95
> diff -u -p -r1.95 services
> --- services 3 Jul 2018 23:52:27 -0000 1.95
> +++ services 27 Jan 2019 13:50:35 -0000
> @@ -179,6 +179,8 @@ silc 706/tcp #
> Secure Live Internet
> silc 706/udp
> kerberos-adm 749/tcp # Kerberos 5 kadmin
> kerberos-adm 749/udp # Kerberos 5 kadmin
> +domain-s 853/tcp # DNS query-response protocol
> run over TLS/DTLS
> +domain-s 853/udp # DNS query-response protocol
> run over TLS/DTLS
> rsync 873/tcp # rsync server
> cddb 888/tcp cddbp # Audio CD Database
> imaps 993/tcp # imap4 protocol over
> TLS/SSL
>
