OK made https://github.com/systemd/systemd/issues/9634
On Sun, 13 May 2018 13:47:25 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
wrote:
> Package: systemd
> Version: 238-4
> Severity: minor
>
> Upon connecting to the Internet one sees
>
> (1) systemd-resolved[482]: Server 127.0.0.1 does not support DNSSEC,
> downgrading to non-DNSSEC mode.
> (2) sys
>> Upon connecting to the Internet one sees
>>
>> (1) systemd-resolved[482]: Server 127.0.0.1 does not support DNSSEC,
>> downgrading to non-DNSSEC mode.
OK, it says "Server 127.0.0.1 does not support DNSSEC"
So there is no reason to proceed with
>> (2) systemd-resolved[482]: DNSSEC validation
Just like they tell you "You are not qualified for a Mexican visa"
so no reason to telephone the embassy again and ask
"Can I have a Mexican visa to Acapulco?"
"Can I have a Mexican visa to Guadalajara?"
"Can I have a Mexican visa to Tabasco?"
"Can I have a Mexican visa to Oaxaca?"
Control: tags -1 + moreinfo
On Sun, 13 May 2018 13:47:25 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
wrote:
> Package: systemd
> Version: 238-4
> Severity: minor
>
> Upon connecting to the Internet one sees
>
> (1) systemd-resolved[482]: Server 127.0.0.1 does not support DNSSEC,
> downgrading
Package: systemd
Version: 238-4
Severity: minor
Upon connecting to the Internet one sees
(1) systemd-resolved[482]: Server 127.0.0.1 does not support DNSSEC,
downgrading to non-DNSSEC mode.
(2) systemd-resolved[482]: DNSSEC validation failed for question ntp.org IN
SOA: failed-auxiliary
systemd
6 matches
Mail list logo