mirror of
https://github.com/nsupdate-info/nsupdate.info.git
synced 2026-04-25 08:35:56 +03:00
[GH-ISSUE #134] Add DNS server status to status page #124
Labels
No labels
bug
bug
duplicate
easy
easy
enhancement
enhancement
invalid
needs help
pull-request
scalability
security
task
urgent
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nsupdate.info-nsupdate-info#124
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 @elnappo on GitHub (Jan 17, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/134
with this you can see problems with DNS Servers, also as a "systemstatus"
@ThomasWaldmann commented on GitHub (Jan 18, 2014):
well, there could be many dns servers, so do you want to list each with name and status?
currently it just shows the overall counts of available / public / down domains (which is partly related to whether the dns server is reachable and working ok).
@elnappo commented on GitHub (Jan 18, 2014):
Yes a status for every host and domain, maybe ping and a test query.
@ThomasWaldmann commented on GitHub (Jan 18, 2014):
ping is not very useful/reliable as ping may be disallowed (not a uncommon setting in routers) or you might just ping some arbitrary other machine if the dns entry does not point to the correct / current IP.
what does "test query" mean?
@elnappo commented on GitHub (Jan 18, 2014):
Im talking about status of the domains and their dns servers. So you could send a ping to all DNS servers which are hosting a domain at nsupdate. In the next step you could test if the DNS server is working by sending a request for a random host within this domain. the status pages shows a list with all public domains and their availability and maybe respond time?
@ThomasWaldmann commented on GitHub (Jan 18, 2014):
well, there is no obligation for a dns server to answer pings either (and even if it does, it doesn't mean the dns server works correctly).
so the only good test for it is whether it answers queries for the respective domain - and we already have an indicator for that, the "available" attribute. the code sets "available" to False if querying the NS fails (no connectivity, wrong secret, other errors).
the list (domain, available) is already shown on the domains overview view - for all domains you have access to.
respond time: is it useful? that time could vary all the time, depending on ns load, network load, etc. - so I think it does not give a useful information except if one would monitor the nameservers frequently (and server monitoring is not quite in scope of nsupdate.info).
@elnappo commented on GitHub (Jan 20, 2014):
okay, i thought this could be useful to have a systemstatus page.
close?
@ThomasWaldmann commented on GitHub (Jan 20, 2014):
yeah, guess we can close it for now. lots of other stuff to do anyway. :D