RIPE NCC lists dnsmon here: http://www.ripe.net/data-tools/stats/dnsmon/ripe-ncc-dns-monitoring-services and indicates on that page to go to: http://dnsmon.ripe.net/ yet going to that link provides an "internal server error". Aren't RIPE NCC services monitored to make sure they are up? -Hank
Dear Hank, Hank Nussbacher wrote:
RIPE NCC lists dnsmon here: http://www.ripe.net/data-tools/stats/dnsmon/ripe-ncc-dns-monitoring-services
and indicates on that page to go to: http://dnsmon.ripe.net/ yet going to that link provides an "internal server error".
Aren't RIPE NCC services monitored to make sure they are up?
All of our services, DNSMON included, are constantly monitored. We've fixed the issue with DNSMON, and engineers are investigating exactly what happened and why, in this instance, we weren't properly alerted. Please accept my apologies for any inconvenience caused by this. Mark -- Mark Dranse RIPE NCC
Mark Dranse wrote:
Hank Nussbacher wrote:
RIPE NCC lists dnsmon here: http://www.ripe.net/data-tools/stats/dnsmon/ripe-ncc-dns-monitoring-services
and indicates on that page to go to: http://dnsmon.ripe.net/ yet going to that link provides an "internal server error".
Aren't RIPE NCC services monitored to make sure they are up?
All of our services, DNSMON included, are constantly monitored.
We've fixed the issue with DNSMON, and engineers are investigating exactly what happened and why, in this instance, we weren't properly alerted.
An update on this: We discovered an error in our monitoring where one specific check wasn't sending the correct hostname in the HTTP GET request. This has now been rectified. Regards, Mark -- Mark Dranse RIPE NCC
participants (2)
-
Hank Nussbacher -
Mark Dranse