This bug was fixed in the package netplan.io - 1.0-2
---------------
netplan.io (1.0-2) unstable; urgency=medium
[ Lukas Märdian ]
* Versioned dep on meson >= 1.3.0 for python.limited_api (Closes: #1066889)
* d/control: downgrade python3-rich to Recommends.
[ Danilo Egea Gondolfo ]
* debian/netplan.io.preinst.
Add a preinst maintainer script for netplan.io to cleanup .pyc cached
files. Due to these files, the directory /usr/share/netplan/netplan is
not being removed after the python3-netplan package split. By removing
these files (and __pycache__ directories), dpkg can remove the old
directory during upgrade.
* d/p/0002-parse-nm-add-a-workaround-for-the-DoT-DNS-option.patch.
Workaround to prevent parse-nm to generate invalid DNS entries in the
resulting YAML if SNI is used. (LP: #2055148)
-- Lukas Märdian <sl...@debian.org> Thu, 28 Mar 2024 12:47:41 +0100
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2055148
Title:
NetworkManager connections with an explicit DoT (DNS over TLS) are not
supported with Netplan
Status in Netplan:
Fix Committed
Status in netplan.io package in Ubuntu:
Fix Released
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
From: https://discourse.ubuntu.com/t/blog-netplan-developer-
diaries/35932/11
Hi all,
NetworkManager connections with an explicit DoT (DNS over TLS)
configuration are not supported with Netplan, but NetworkManager does
feed back the DoT DNS info with server address and Server Name
Indication (SNI) in the form server_address#SNI, e.g.
1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a
result, subsequent Netplan config applications fail because DNS
servers don’t have the expected dotted decimal (IPv4) or colon’ed hex
(IPv6) form.
```
nmcli> describe ipv4.dns
=== [dns] ===
[NM property description]
Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server
name can be specified by appending "#example.com" to the IP address of the DNS
server. This currently only has effect when using systemd-resolved.
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2055148/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
