starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

DNS loop with AdGuard LXC #1800

New Issue
Closed
opened 2026-02-05 02:17:44 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 02:17:44 +03:00
Owner
Copy Link

Originally created by @rollodroid on GitHub (Oct 15, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

AdGuard Home LXC

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/adguard.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/8.3.3/f157a38b211595d6 (running kernel: 6.8.12-15-pve)

📝 Provide a clear and concise description of the issue.

The DNS settings are "use host settings" It is necessesary to use no DNS at all because adguard uses whatever is set as upstream, even when not set in the webinterface. This can create DNS loops for some percentage of the requests and response times of several seconds instead of ms for that requests.

🔄 Steps to reproduce the issue.

Set the adguard server as DNS server in the router, set the router as DNS for clients via dhcp (typically), set some upstream servers on the internet as upstream in adguard. Set the container to use the dhcp setting (the conttainer itself or inherited from the host)
After some time of usage, some requests are upsreamed to the router ip.

❌ Paste the full error output (if available).

Image

🖼️ Additional context (optional).

No response

Originally created by @rollodroid on GitHub (Oct 15, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? AdGuard Home LXC ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/adguard.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/8.3.3/f157a38b211595d6 (running kernel: 6.8.12-15-pve) ### 📝 Provide a clear and concise description of the issue. The DNS settings are "use host settings" It is necessesary to use no DNS at all because adguard uses whatever is set as upstream, even when not set in the webinterface. This can create DNS loops for some percentage of the requests and response times of several seconds instead of ms for that requests. ### 🔄 Steps to reproduce the issue. Set the adguard server as DNS server in the router, set the router as DNS for clients via dhcp (typically), set some upstream servers on the internet as upstream in adguard. Set the container to use the dhcp setting (the conttainer itself or inherited from the host) After some time of usage, some requests are upsreamed to the router ip. ### ❌ Paste the full error output (if available). <img width="606" height="227" alt="Image" src="https://github.com/user-attachments/assets/6a68f700-3bf8-4cca-9c5c-6a7fe2f55509" /> ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 02:17:44 +03:00
OVERLORD commented 2026-02-05 02:17:51 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 15, 2025):

Ive exact the Same config running since over 2 years. Never get Problems. Issue should Not exist Here. Script Work as expected. If you think, something is wrong -> adguard Home Repo.

@MickLesk commented on GitHub (Oct 15, 2025): Ive exact the Same config running since over 2 years. Never get Problems. Issue should Not exist Here. Script Work as expected. If you think, something is wrong -> adguard Home Repo.
OVERLORD commented 2026-02-05 02:17:54 +03:00
Author
Owner
Copy Link

@rollodroid commented on GitHub (Oct 15, 2025):

The issue exists, I even provided a screenshot that tells the upstream 192.168.188.1 is used, which is not configured:

Image

The issue might not appear for you because it depends on other settings, which in your case may not inject the addidtional upstream. But the issue is still real!

@rollodroid commented on GitHub (Oct 15, 2025): The issue exists, I even provided a screenshot that tells the upstream 192.168.188.1 is used, which is not configured: <img width="520" height="269" alt="Image" src="https://github.com/user-attachments/assets/0cbe2c14-cc3f-4bae-8808-daf582c98b4e" /> The issue might not appear for you because it depends on other settings, which in your case may not inject the addidtional upstream. But the issue is still real!
OVERLORD commented 2026-02-05 02:17:58 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 15, 2025):

Then Report it to adguard. We only deploy there deb File. We dont Change any Things at this

@MickLesk commented on GitHub (Oct 15, 2025): Then Report it to adguard. We only deploy there deb File. We dont Change any Things at this
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1800
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?