On 2/15/21 8:16 PM, Ed Greshko wrote: > On 16/02/2021 09:10, Steve Dickson wrote: >> On 2/15/21 7:55 PM, Ed Greshko wrote: >>> On 16/02/2021 08:50, Steve Dickson wrote: >>>> But I think this is the problem... >>>> >>>> systemctl start systemd-resolved >>>> systemctl -o cat status systemd-resolved >>>> Starting Network Name Resolution... >>>> Positive Trust Anchors: >>>> . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d >>>> Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.i> >>>> Failed to add DNS server address '67.207.67.2,67.207.67.3', ignoring: Invalid argument >>>> Using system hostname 'steved-v4dev-f33.nfsv4.dev'. >>>> Started Network Name Resolution. >>>> >>>> What has changed in the parsing of DNS server addresses??? >>> I get... >>> >>> Positive Trust Anchors: >>> . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d >>> Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 1> >>> Using system hostname 'meimei.greshko.com'. >>> >>> I don't see where your DNS servers are defined from the previous post you showed. >>> >>> My primary interface is enp2s0 and I get... >>> >>> [egreshko@meimei ~]$ nmcli device show enp2s0 | grep -i dns >>> IP4.DNS[1]: 192.168.1.142 >>> IP6.DNS[1]: 2001:b030:112f::19 >>> >>> Does something get returned for your eth0 device? >> No... >> >> nmcli device show eth0 | grep -i dns >> nmcli device show eth1 | grep -i dns >> >> but... after changing /etc/systemd/resolved.conf to DNS=8.8.8.8 >> Then doing a systemctl restart systemd-resolved >> The dns started to work... There is an issue >> with the latest systemd-resolved > > I don't think so.... > > In my /etc/systemd/resolved.conf I have > > #DNS= When I have DNS=67.207.67.3,67.207.67.2 I get # systemctl -o cat status systemd-resolved Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.i> Failed to add DNS server address '67.207.67.2,67.207.67.3', ignoring: Invalid argument When I change DNS=67.207.67.2 and restart systemd-resolved my dns comes back... w/out the error. > > So, you're just manually adding a DNS server. No... the DNS=67.207.67.2,67.207.67.3 is coming from the cloud provider. > You're interface still doesn't have a DNS server defined. > As Far As I can Tell. Right! Because whatever changed in systemd-resolved can longer parse DNS=<address>,<address>. Which it could before... > > Why don't you try adding servers to your network configuration instead? I'm a VM in a cloud... I have no control over the network servers. > > I have systemd-246.10-1.fc33.x86_64 installed on all systems with no problems. I do to... # rpm -q systemd systemd-246.10-1.fc33.x86_64 But you don't have in ',' in your DNS statments. steved. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
