[client] Disable dnssec for systemd explicitly

[lixmal]

Describe your changes

Issue ticket number and link

Updates #1483

Stack

Checklist

• Is it a bug fix
• Is a typo/documentation fix
• Is a feature enhancement
• It is a refactor
• Created tests that fail without the change (if possible)
• Extended the README / documentation, if necessary

[Copilot]

Pull Request Overview

This PR explicitly disables DNSSEC when applying DNS configurations via systemd on Linux.

• Introduces a new D-Bus method suffix constant for SetDNSSEC
• Refactors error wrapping for the existing SetDNS call
• Adds a call to disable DNSSEC ("no") and logs failures

Comments suppressed due to low confidence (3)

client/internal/dns/systemd_linux.go:103

• Add a unit or integration test to verify that DNSSEC is explicitly set to disabled when applying DNS configuration, ensuring this new behavior is covered by CI.

if err = s.callLinkMethod(systemdDbusSetDNSSECMethodSuffix, "no"); err != nil {

client/internal/dns/systemd_linux.go:103

• Verify that the D-Bus SetDNSSEC call signature matches this usage; if the method expects a structured input or array rather than a raw string, this may fail at runtime.

if err = s.callLinkMethod(systemdDbusSetDNSSECMethodSuffix, "no"); err != nil {

client/internal/dns/systemd_linux.go:104

• Confirm that the imported log package supports Errorf. The standard library log does not have Errorf, so ensure the correct logging library is in use.

    log.Errorf("set DNSSEC to 'no': %v", err)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud