DNS servers aren't assigned after system reboot

[neilio]

trafficstars

Issue Details

• Version of AdGuard Home server: AdGuard Home Version: v0.107.3 Channel: release Go version: go1.16.12 Build time: 2022-01-25T13:34:45Z+0000 GOOS: darwin GOARCH: arm64 Race: false Dependencies:
• How did you install AdGuard Home: Downloaded from Github
• How did you setup DNS configuration: Running on an M1 Mac Mini (2020 edition)
• CPU architecture: amd64
• Operating system and version: macOS 12.2

Expected Behavior

I am using AGH for DHCP as well as filtering. After rebooting the OS, AdGuardHome should launch and propagate its IP as a DNS server to itself and the rest of the network. When I look at the AGH mac's network settings I should see its network IP (192.168.2.2) as the main DNS server.

Actual Behavior

After a reboot the DNS servers are set to 169.x.x.x and DNS is not working on the AGH system itself or the rest of the network. I need to manually stop, and then restart the AdGuardHome service from the command line to fix this.

[EugeneOne1]

@neilio, hello and thanks for the report. DHCP server shouldn't propagate its address to its own host machine since it doesn't expect that the host needs a configuration received by DHCP. So to achieve a more stable setup it'd be better to set a static IP address on the DHCP server's host and a loopback (i.e. 127.0.0.1) as a DNS server.

However the fact that rebooting AdGuard Home fixes the problem is rather interesting. Could you please collect a verbose log to help us troubleshoot the issue? You may either post it here or send to [email protected].

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Birbber]

Closing this issue as completed. Feel free to re-open if needed.