You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platform: Raspberry Pi (PiHole is installed natively)
Expected behavior
If one has multiple local CNAME Records, one should be able to quickly add/remove those records without having to wait till the server has restarted
Actual behavior / bug
After adding/removing 1 Record the Web Interface is down since the server is restarting, therefore not making it able to add/remove more items in a quickly manner.
Steps to reproduce
Steps to reproduce the behavior:
Go to your pi-hole Admin interface
Go To Settings => Local DNS Records
Add a local CNAME record like test1.mydomain.com => server.mydomain.com
Add another local CNAME record test2.mydomain.com => server.mydomain.com
I am using a NGINX Reverse Proxy to make PiHole accessible externally
Possible solution
I can understand, that trying to make the changes apply instantaniously is desireable, but it shouldn't get in the way of using the tool.
One way to achieve this kind of behaviour could be a queue to push changes to (currently only add and delete are possible anyways) and then a final button to apply the changes when everything is ready.
The text was updated successfully, but these errors were encountered:
Versions
Platform
Expected behavior
If one has multiple local CNAME Records, one should be able to quickly add/remove those records without having to wait till the server has restarted
Actual behavior / bug
After adding/removing 1 Record the Web Interface is down since the server is restarting, therefore not making it able to add/remove more items in a quickly manner.
Steps to reproduce
Steps to reproduce the behavior:
Debug Token
Screenshots
Additional context
I am using a NGINX Reverse Proxy to make PiHole accessible externally
Possible solution
I can understand, that trying to make the changes apply instantaniously is desireable, but it shouldn't get in the way of using the tool.
One way to achieve this kind of behaviour could be a queue to push changes to (currently only add and delete are possible anyways) and then a final button to apply the changes when everything is ready.
The text was updated successfully, but these errors were encountered: