SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

DNS lookup Failure with Homeassistant and AdGuard Helper Script #92

New Issue
Closed
opened 2025-11-20 04:43:34 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 04:43:34 -05:00
Owner
Copy Link

Originally created by @TKK91 on GitHub (Nov 20, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

I have always the same issue when i run the Homeassistant Helper Script, as well as Adguard (LXC Debian 12 related Helper Scrips). The Error: "DNS Lookup Failure" occurs everytime. When i use verbose mode the next lines are the failed name resolving and thus not fetching the required data.
I tried homeassistant-core helper script and it worked just fine.
Internet connection works just fine, DNS is working properly.
In the PVE Shell the command "apt update" is working fine as well.
I can ping domains as well as ip addresses.

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

Starting Helper Script for Homeassistant or AdGuard

Originally created by @TKK91 on GitHub (Nov 20, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. I have always the same issue when i run the Homeassistant Helper Script, as well as Adguard (LXC Debian 12 related Helper Scrips). The Error: "DNS Lookup Failure" occurs everytime. When i use verbose mode the next lines are the failed name resolving and thus not fetching the required data. I tried homeassistant-core helper script and it worked just fine. Internet connection works just fine, DNS is working properly. In the PVE Shell the command "apt update" is working fine as well. I can ping domains as well as ip addresses. ### What settings are you currently utilizing? - [X] Default Settings - [X] Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. Starting Helper Script for Homeassistant or AdGuard
saavagebueno added the not a script issue label 2025-11-20 04:43:34 -05:00
saavagebueno commented 2025-11-20 04:43:34 -05:00
Author
Owner
Copy Link

@Mellowlynx commented on GitHub (Nov 20, 2024):

Please verify that the VM/LXC has a correct DNS and can ping to the outside.
Also, make sure not to block outdoing DNS requests to public DNS servers.

@Mellowlynx commented on GitHub (Nov 20, 2024): Please verify that the VM/LXC has a correct DNS and can ping to the outside. Also, make sure not to block outdoing DNS requests to public DNS servers.
saavagebueno commented 2025-11-20 04:43:35 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 20, 2024):

And next time, add output logs / screenshot or something else. It's like looking through a crystal ball.

@MickLesk commented on GitHub (Nov 20, 2024): And next time, add output logs / screenshot or something else. It's like looking through a crystal ball.
saavagebueno commented 2025-11-20 04:43:35 -05:00
Author
Owner
Copy Link

@TKK91 commented on GitHub (Nov 20, 2024):

H

Please verify that the VM/LXC has a correct DNS and can ping to the outside. Also, make sure not to block outdoing DNS requests to public DNS servers.

Thanks for the fast response, it was indeed a problem on my site. The VM was pointing to my router as a DNS (altough Proxmox did not, as i changed it in the .conf files) and there was a not working DNS stored.

@TKK91 commented on GitHub (Nov 20, 2024): H > Please verify that the VM/LXC has a correct DNS and can ping to the outside. Also, make sure not to block outdoing DNS requests to public DNS servers. Thanks for the fast response, it was indeed a problem on my site. The VM was pointing to my router as a DNS (altough Proxmox did not, as i changed it in the .conf files) and there was a not working DNS stored.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#92
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?