I have 2 MT routers.
MT2 supports WLAN and has several virtual WLAN's. And is connected to MT1 - the main router
Every WLAN has its own IP address segment and address pool.
One of the virtual WLAN's is protected by an Pi-hole connected to a different IP segment on MT1.
During the day the kids should only surf school related.
So I entered as DNS server 192.168.177.185 (which is the Pi-hole) in the DHCP Network settings for this virtual WLAN (10.10.50.0/24).
Works fine.
But in the evening the kids should have full access to internet, without re-routing through the Pi-hole.
Therefore DNS servers are set to 8.8.8.8 and 4.4.4.4 in the DHCP Network settings for this virtual WLAN.
The changes are not recognized by the system until MT2 (the WLAN router) is rebooted. ?:-|
To change the server settings I have to scheduled scripts:
Script 1
Code: Select all
/ip dhcp-server network set 4 address=10.10.50.0/24 dns-server=8.8.8.8,4.4.4.4 gateway=10.10.50.1 comment="redirect DNS to 8.8.8.8+4.4.4.4"
Code: Select all
/ip dhcp-server network set 4 address=10.10.50.0/24 dns-server=192.169.177.185 gateway=10.10.50.1 comment="redirect DNS to Pi-hole 192.168.177.185"
What do I have to do that the DNS changes will be reflected in the connections promptly without rebooting MT2?
Thanks, Tom