Skip to content

IPv6 address valid check ignores scope ID #3022

@TonyRL

Description

@TonyRL

Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

Issue Details

  • Version of AdGuard Home server:
    • v0.106.0
  • How did you install AdGuard Home:
    • Docker
  • How did you setup DNS configuration:
    • Router
  • If it's a router or IoT, please write device model:
    • pfSense on ESXi
  • CPU architecture:
    • AMD64
  • Operating system and version:
    • pfSense 2.5.1

Expected Behavior

AdGuard Home should accept IPv6 address with scope ID and initialise normally.

Actual Behavior

AdGuard Home initialisation stop at dnsServer.Prepare: setting up resolvers: systemResolvers

Screenshots

Screenshot:
 2021/04/29 00:47:23 [info] AdGuard Home, version v0.106.0
 2021/04/29 00:47:23 [info] Upgrade yaml: 8 to 9
 2021/04/29 00:47:23 [info] Upgrade yaml: 9 to 10
 2021/04/29 00:47:23 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
 2021/04/29 00:47:23 [info] auth: initialized.  users:1  sessions:3
 2021/04/29 00:47:23 [info] number of certs - 1
 2021/04/29 00:47:23 [info] Initialize web module
 2021/04/29 00:47:23 [fatal] dnsServer.Prepare: setting up resolvers: systemResolvers: lookup test1619628443469047584.org on [fe80::1b0b:b8a6:e98a:cb58%br0]:53: parsing "fe80::1b0b:b8a6:e98a:cb58%br0": the passed string is not a valid IP address

Additional Information

I have my DHCPv6 Server disabled and RA Router mode set as Assisted in my pfSense IPv6 settings. The IPv6 DNS servers (fe80::1b0b:b8a6:e98a:cb58 and some others) are also entered there.
br0 is a custom network on my Docker host (Unraid).
The initialisation was smooth on v0.105.2 and older releases. I spent some time switching different version tags and find out this issue has occurred since v0.106.0-b.2.

Log of v0.105.2 (Nothing went wrong):

Details
 2021/04/28 16:54:54 [info] AdGuard Home, version v0.105.2, channel release, arch linux amd64
 2021/04/28 16:54:54 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
 2021/04/28 16:54:54 [info] Auth: initialized.  users:1  sessions:3
 2021/04/28 16:54:54 [info] number of certs - 1
 2021/04/28 16:54:54 [info] Initialize web module
 2021/04/28 16:54:55 [info] AdGuard Home is available on the following addresses:
 2021/04/28 16:54:55 [info] Go to https://**********.com
 2021/04/28 16:54:55 [info] Go to http://127.0.0.1:80
 2021/04/28 16:54:55 [info] Go to http://127.0.0.1:3001 (BETA)
 2021/04/28 16:54:55 [info] Go to http://[::1]:80
 2021/04/28 16:54:55 [info] Go to http://[::1]:3001 (BETA)
 2021/04/28 16:54:55 [info] Go to http://192.168.1.251:80
 2021/04/28 16:54:55 [info] Go to http://192.168.1.251:3001 (BETA)
 2021/04/28 16:54:55 [info] Go to http://[2404:**********]:80
 2021/04/28 16:54:55 [info] Go to http://[2404:**********]:3001 (BETA)
 2021/04/28 16:54:55 [info] Go to http://[2404:**********]:80
 2021/04/28 16:54:55 [info] Go to http://[2404:**********]:3001 (BETA)
 2021/04/28 16:55:01 [info] Starting the DNS proxy server
 2021/04/28 16:55:01 [info] The server is configured to refuse ANY requests
 2021/04/28 16:55:01 [info] DNS cache is enabled
 2021/04/28 16:55:01 [info] MaxGoroutines is set to 50
 2021/04/28 16:55:01 [info] Creating the UDP server socket
 2021/04/28 16:55:01 [info] Listening to udp://[::]:53
 2021/04/28 16:55:01 [info] Creating a TCP server socket
 2021/04/28 16:55:01 [info] Listening to tcp://[::]:53
 2021/04/28 16:55:01 [info] Creating a TLS server socket
 2021/04/28 16:55:01 [info] Listening to tls://[::]:853
 2021/04/28 16:55:01 [info] Creating a QUIC listener
 2021/04/28 16:55:01 [info] Listening to quic://[::]:784
 2021/04/28 16:55:01 [info] Entering the UDP listener loop on [::]:53
 2021/04/28 16:55:01 [info] Entering the DNS-over-QUIC listener loop on [::]:784
 2021/04/28 16:55:01 [info] Entering the tls listener loop on [::]:853
 2021/04/28 16:55:01 [info] Entering the tcp listener loop on [::]:53

Log of v0.106.0-b.1 (Still nothing went wrong)

Details
 2021/04/28 16:35:36 [info] AdGuard Home, version v0.106.0-b.1, channel beta, arch linux amd64
 2021/04/28 16:35:36 [info] Upgrade yaml: 7 to 8
 2021/04/28 16:35:36 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
 2021/04/28 16:35:36 [info] Auth: initialized.  users:1  sessions:3
 2021/04/28 16:35:36 [info] number of certs - 1
 2021/04/28 16:35:36 [info] Initialize web module
 2021/04/28 16:35:38 [info] AdGuard Home is available on the following addresses:
 2021/04/28 16:35:38 [info] Go to https://**********
 2021/04/28 16:35:38 [info] Go to http://127.0.0.1:80
 2021/04/28 16:35:38 [info] Go to http://127.0.0.1:3001 (BETA)
 2021/04/28 16:35:38 [info] Go to http://[::1]:80
 2021/04/28 16:35:38 [info] Go to http://[::1]:3001 (BETA)
 2021/04/28 16:35:38 [info] Go to http://192.168.1.251:80
 2021/04/28 16:35:38 [info] Go to http://192.168.1.251:3001 (BETA)
 2021/04/28 16:35:38 [info] Go to http://[2404:**********]:80
 2021/04/28 16:35:38 [info] Go to http://[2404:**********]:3001 (BETA)
 2021/04/28 16:35:45 [info] Starting the DNS proxy server
 2021/04/28 16:35:45 [info] The server is configured to refuse ANY requests
 2021/04/28 16:35:45 [info] DNS cache is enabled
 2021/04/28 16:35:45 [info] MaxGoroutines is set to 50
 2021/04/28 16:35:45 [info] Creating the UDP server socket
 2021/04/28 16:35:45 [info] Listening to udp://[::]:53
 2021/04/28 16:35:45 [info] Creating a TCP server socket
 2021/04/28 16:35:45 [info] Listening to tcp://[::]:53
 2021/04/28 16:35:45 [info] Creating a TLS server socket
 2021/04/28 16:35:45 [info] Listening to tls://[::]:853
 2021/04/28 16:35:45 [info] Creating a QUIC listener
 2021/04/28 16:35:45 [info] Listening to quic://[::]:784
 2021/04/28 16:35:45 [info] Entering the UDP listener loop on [::]:53
 2021/04/28 16:35:45 [info] Entering the tls listener loop on [::]:853
 2021/04/28 16:35:45 [info] Entering the tcp listener loop on [::]:53
 2021/04/28 16:35:45 [info] Entering the DNS-over-QUIC listener loop on [::]:784

Log of v0.106.0-b.2 (Something went wrong from vv0.106.0-b.1 to v0.106.0-b.2)

Details
 2021/04/29 00:31:03 [info] AdGuard Home, version v0.106.0-b.2
 2021/04/29 00:31:03 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
 2021/04/29 00:31:03 [info] auth: initialized.  users:1  sessions:3
 2021/04/29 00:31:03 [info] number of certs - 1
 2021/04/29 00:31:03 [info] Initialize web module
 2021/04/29 00:31:04 [fatal] dnsServer.Prepare: setting up resolvers: systemResolvers: lookup test1619627463356613393.org on [fe80::1b0b:b8a6:e98a:cb58%br0]:53: parsing "fe80::1b0b:b8a6:e98a:cb58%br0": the passed string is not a valid IP address
Container stopped

Log of v0.106.0-b.3

Details
 2021/04/29 01:12:49 [info] AdGuard Home, version v0.106.0-b.3
 2021/04/29 01:12:49 [info] Upgrade yaml: 8 to 9
 2021/04/29 01:12:49 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
 2021/04/29 01:12:49 [info] auth: initialized.  users:1  sessions:3
 2021/04/29 01:12:49 [info] number of certs - 1
 2021/04/29 01:12:49 [info] Initialize web module
 2021/04/29 01:12:49 [fatal] dnsServer.Prepare: setting up resolvers: systemResolvers: lookup test1619629969253076409.org on [fe80::1b0b:b8a6:e98a:cb58%br0]:53: parsing "fe80::1b0b:b8a6:e98a:cb58%br0": the passed string is not a valid IP address
Container stopped

Log of v0.106.0-b.4

Details
 2021/04/29 01:13:58 [info] AdGuard Home, version v0.106.0-b.4
 2021/04/29 01:13:58 [info] Upgrade yaml: 9 to 10
 2021/04/29 01:13:58 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
 2021/04/29 01:13:58 [info] auth: initialized.  users:1  sessions:3
 2021/04/29 01:13:58 [info] number of certs - 1
 2021/04/29 01:13:58 [info] Initialize web module
 2021/04/29 01:13:58 [fatal] dnsServer.Prepare: setting up resolvers: systemResolvers: lookup test1619630038139649825.org on [fe80::1b0b:b8a6:e98a:cb58%br0]:53: parsing "fe80::1b0b:b8a6:e98a:cb58%br0": the passed string is not a valid IP address

Log of v0.106.0-b.5

Details
 2021/04/29 01:15:24 [info] AdGuard Home, version v0.106.0-b.5
 2021/04/29 01:15:24 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
 2021/04/29 01:15:24 [info] auth: initialized.  users:1  sessions:3
 2021/04/29 01:15:24 [info] number of certs - 1
 2021/04/29 01:15:24 [info] Initialize web module
 2021/04/29 01:15:24 [fatal] dnsServer.Prepare: setting up resolvers: systemResolvers: lookup test1619630124160017595.org on [fe80::1b0b:b8a6:e98a:cb58%br0]:53: parsing "fe80::1b0b:b8a6:e98a:cb58%br0": the passed string is not a valid IP address

Log of v0.106.0 (same as above)

Details
 2021/04/29 00:47:23 [info] AdGuard Home, version v0.106.0
 2021/04/29 00:47:23 [info] Upgrade yaml: 8 to 9
 2021/04/29 00:47:23 [info] Upgrade yaml: 9 to 10
 2021/04/29 00:47:23 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
 2021/04/29 00:47:23 [info] auth: initialized.  users:1  sessions:3
 2021/04/29 00:47:23 [info] number of certs - 1
 2021/04/29 00:47:23 [info] Initialize web module
 2021/04/29 00:47:23 [fatal] dnsServer.Prepare: setting up resolvers: systemResolvers: lookup test1619628443469047584.org on [fe80::1b0b:b8a6:e98a:cb58%br0]:53: parsing "fe80::1b0b:b8a6:e98a:cb58%br0": the passed string is not a valid IP address
Container stopped

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions