mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1769] Make the agent more resilient against DNS issues #1101
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#1101
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 @P6g9YHK6 on GitHub (Feb 23, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1769
Is your feature request related to a problem? Please describe.
When an agent loses DNS services it will not work anymore. (Mesh is not or less impacted)
Describe the solution you'd like
when a dns resolution fails it should fallback to the latest known working ip that was replied and probably changes the color of the "connectivity icon" to yellow or else.
Additional context
https://discord.com/channels/736478043522072608/1204337171633283092
@dinger1986 commented on GitHub (Mar 10, 2024):
could this not be simply accomplished by using a script which updates the hosts file?
@P6g9YHK6 commented on GitHub (Mar 11, 2024):
yes, but in this case i got the feeling that this is more a global "tactical" issue than a client sided one :)
for exemple the ESET management agent allow to set a list of whole lists of different addresses to access to the console. while my proposal does not go as far as this it is a common industry issue.
@bbrendon commented on GitHub (Mar 13, 2024):
LoL. I came here to say WTF. but I see the comment was deleted.