Custom Redirects

yubiuser · August 22, 2020, 6:19am

That's what CNAME entries do.
Pihole will likely contain the ability to set those in a next version

github.com/pi-hole/AdminLTE

Added support for CNAME records add/remove

pi-hole:devel ← marank:devel

opened 08:29PM - 12 May 20 UTC

marank

+473 -31

Signed-off-by: Matthias rank <development@m-rank.de> **By submitting this pul…l request, I confirm the following:** `{please fill any appropriate checkboxes, e.g: [X]}` `{Please ensure that your pull request is for the 'devel' branch!}` - [X] I have read and understood the [contributors guide](https://github.com/pi-hole/AdminLTE/blob/master/CONTRIBUTING.md), as well as this entire template. - [X] I have made only one major change in my proposed changes. - [X] I have commented my proposed changes within the code. - [X] I have tested my proposed changes. - [X] I am willing to help maintain this change if there are issues with it later. - [X] I give this submission freely and claim no ownership. - [X] It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) - [X] I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) - [X] I have Signed Off all commits. ([`git commit --signoff`](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff)) --- **What does this PR aim to accomplish?:** `{A detailed description, screenshots (if necessary), as well as links to any relevant GitHub issues}` This PR enables adding/removing CNAME records via the admin interface. To do so, the following PR needs to be accepted as well, because it allows editing the neccessary file using the pihole CLI: pi-hole/pi-hole#3351 **How does this PR accomplish the above?:** `{A detailed description (such as a changelog) and screenshots (if necessary) of the implemented fix}` ![grafik](https://user-images.githubusercontent.com/7427683/81742024-bb38e380-949f-11ea-9ec5-5567a54ceb36.png) I changed the menu accordingly to have both Local DNS records and CNAME records in one submenu. **What documentation changes (if any) are needed to support this PR?:** `{A detailed list of any necessary changes}`