Skip to content

Conjoined address:port in dashboard #2885

Description

@SilmorSenedlen

Output of the following commands:

dnscrypt-proxy -config dnscrypt-proxy.toml -version
2.1.12

dnscrypt-proxy -config dnscrypt-proxy.toml -check
[2025-06-07 18:01:51] [NOTICE] Use of [blacklist] is deprecated - Update your config file
[2025-06-07 18:01:51] [NOTICE] Source [public-resolvers] loaded
[2025-06-07 18:01:51] [NOTICE] Source [relays] loaded
[2025-06-07 18:01:51] [NOTICE] Source [dnscry-pt-resolvers] loaded
[2025-06-07 18:01:51] [NOTICE] Configuration successfully checked

Resolving [example.com] using 127.0.0.1 port 53

Resolver : *********

Canonical name: example.com.

IPv4 addresses: 23.192.228.84, 23.215.0.136, 23.215.0.138, 96.7.128.175, 96.7.128.198, 23.192.228.80
IPv6 addresses: 2600:1406:3a00:21::173e:2e66, 2600:1406:bc00:53::b81e:94c8, 2600:1406:bc00:53::b81e:94ce, 2600:1408:ec00:36::1736:7f24, 2600:1408:ec00:36::1736:7f31, 2600:1406:3a00:21::173e:2e65

Name servers : b.iana-servers.net., a.iana-servers.net.
DNSSEC signed : yes
Mail servers : 1 mail servers found

HTTPS alias : -
HTTPS info : -

Host info : -
TXT records : _k2n1y4vw3qtb4skdx9e7dxt97qrmmq9, v=spf1 -all

What is affected by this bug?

Records in "server" column in http dashboard and /api/metrics display classic dns server address:port are conjoined.

Example

"recent_queries": [{
"timestamp": "2025-06-07T16:13:11.8659699+03:00",
"client_ip": "::1",
"domain": "drive-api.proton.me",
"type": "A",
"response_code": "FORWARD",
"response_time": 2,
"server": "192.168.99.153",
"cache_hit": false
},

Actually server is 192.168.99.1 with port 53.

When does this occur?

When using classic DNS server in forwarding-rules.

Where does it happen?

In http dashboard and /api/metrics

How do we replicate the issue?

  1. Add classic DNS server in forwarding-rules file
  2. Resolve domain from forwarding-rules
  3. Check http dashboard or /api/metrics

Expected behavior (i.e. solution)

Not conjoining address and port in "server" column in http dashboard and /api/metrics

Other Comments

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions