API HTTP Status

[dada051]

I use Uptime-Kuma to monitor my services, and as the latest version of Technitium-DNS added a /api/dnsClient/healthCheck API, I wanted to configure it in U-K. But it seems that API always returns HTTP 200, even on a bad authentication. I expected a HTTP 401 in that case. So I have 3 questions:

• why HTTP 200 instead of HTTP 401?
• What's the HTTP status in case of a NOK in healh status?
• Why the health endpoint needs auth?

Thanks for your amazing product!

[Hemsby]

What are you checking? Your supposed to evaluate the JSON response not if the API is alive and responding. Please share what you are using

[dada051]

I configured uptime-kuma to send a GET request to https://IP:53443/api/dnsClient/healthCheck in place of the DNS monitor.

[Hemsby]

Anything other than "Status: OK" will give "Status: "Error" along with the error message

[ShreyasZare]

Thanks for asking. The DNS server does not implement REST API. Its a simpler HTTP API which does not alter HTTP response status code but uses status property in the json response.

What's the HTTP status in case of a NOK in healh status?

You will see the status return error.

Why the health endpoint needs auth?

Its done to prevent abuse. Imagine having it open on the Internet and someone making use of it to resolve victim's domain names to trigger some kind of amplification attack.

[Hemsby]

@ShreyasZare - I really should put more detail in my responses 😂, but glad your always here to confirm my replies, albeit in a better more verbose way.

[dada051]

OK, so I will use the other HTTP probe with keyword look-up. But thanks for your replies!