mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Keep DNS rewrites when protection is disabled #2902
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#2902
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jicho on GitHub (Jul 15, 2021).
Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Problem Description
When I temporary disable the protection this also results in a disabled DNS rewrite as a result I can't use my internal used domain names
Proposed Solution
When disabling protection it would be nice when it is possible to keep the DNS rewrite function active so internal subdomains that are not in an external DNS are still internally available.
I'm talking about the DNS rewrites on this page:
http://x.x.x.x/#dns_rewrites
Additional Information
I'm using AGH only internally and have custom domains running to access some internal services with ease, but... when I disable protection I need to come up with the IP's to access the services and... I need to access AGH by IP so I can enable protection again.
@ainar-g commented on GitHub (Jul 15, 2021):
Dup of #1558.
@jicho commented on GitHub (Jul 15, 2021):
Argh... sorry... I looked for an issue like mine, but didn't found it :(