(Bug) DHCP Server Primary DNS Settings not persisting after reboot
(Bug) DHCP Server Primary DNS Settings not persisting after reboot
Tags:
#DNS
Hello,
I have a TL-WA850RE - and it appears to have a bug. Namely, the DHCP settings are being reset to the default 0.0.0.0 after the repeater is rebooted. I've updated the Firmware to the latest version available for the UK region, but this issue is still persisting.
Reproduction steps:
- Set up the extended
- Log into the extender via the web interface
- Click on Network tab in the menu
- Set DHCP server setting to On
- Set Primary DNS setting to a custom value (in my case, it is 192.168.1.185 - since I am running a pihole)
- Save
- Confirm that the setting is working correctly
- Reboot the extender through the web interface, or through the scheduled reboot
- Log into extender via the web interface
Expected: DHCP server settings are persisted. Custom DNS is used.
Actual: DHCP server settings are reset. Primary DNS is set to 0.0.0.0 and default DNS is used instead.
