starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Compare serial return by all specified authoritatives DNS server #977

New issue

Open

opened 2026-02-28 02:05:58 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-28 02:05:58 -05:00

Owner

Originally created by @Dryusdan on GitHub (Apr 12, 2022).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

All DNS have a serial number (for dryusdan.space for exemple actually is it 1649768496 (SOA record in zone file)).
Sometime (when I failed something), serial is not the same between my primary DNS server and the two other DNS server and I don't detect it automatically.

✔️ Solution

Kuma detects if the SOA records between the 3 authoritative DNS are identical (and if it returns something) and if it is the case it is OK otherwise NOK.

❓ Alternatives

Actually I don't found this feature in Zabbix community repository. I can develop a bash or python script for Zabbix but I think Kuma can do this ^^
I found this feature in ZoneMaster but is not a tool for monitoring, just a tool for diagnose some problem in domain

📝 Additional Context

No response

Originally created by @Dryusdan on GitHub (Apr 12, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Monitor ### 🔖 Feature description All DNS have a serial number (for dryusdan.space for exemple actually is it 1649768496 (SOA record in zone file)). Sometime (when I failed something), serial is not the same between my primary DNS server and the two other DNS server and I don't detect it automatically. ### ✔️ Solution Kuma detects if the SOA records between the 3 authoritative DNS are identical (and if it returns something) and if it is the case it is OK otherwise NOK. ### ❓ Alternatives Actually I don't found this feature in Zabbix community repository. I can develop a bash or python script for Zabbix but I think Kuma can do this ^^ I found this feature in [ZoneMaster](https://zonemaster.net/domain_check) but is not a tool for monitoring, just a tool for diagnose some problem in domain ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:monitor

labels

2026-02-28 02:05:58 -05:00

deekerman commented

2026-02-28 02:06:00 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Aug 1, 2023):

@Dryusdan
Is the serial number you are referring to a duplicate of https://github.com/louislam/uptime-kuma/issues/432?
If true, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If false, could you explain what would be needed in addition to https://github.com/louislam/uptime-kuma/issues/432?

@CommanderStorm commented on GitHub (Aug 1, 2023): @Dryusdan Is the serial number you are referring to a duplicate of https://github.com/louislam/uptime-kuma/issues/432? If true, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If false, could you explain what would be needed in addition to https://github.com/louislam/uptime-kuma/issues/432?

deekerman commented

2026-02-28 02:06:00 -05:00

Author

Owner

@Dryusdan commented on GitHub (Aug 16, 2023):

In issue #432 Kuma is used to getting value in TXT.

In this issue Kuma is used to check if all nameserver have the same SOA.

@Dryusdan commented on GitHub (Aug 16, 2023): In issue #432 Kuma is used to getting value in TXT. In this issue Kuma is used to check if all nameserver have the same SOA.

deekerman commented

2026-02-28 02:06:00 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Aug 16, 2023):

In issue #432 Kuma is used to getting value in TXT.

Not quite true. TXT is just one example of said issue:

DNS should have a 'keyword'-like field

=> I think this issue can be closed in favour of #432

@CommanderStorm commented on GitHub (Aug 16, 2023): > In issue #432 Kuma is used to getting value in TXT. Not quite true. TXT is just one example of said issue: > DNS should have a 'keyword'-like field => I think this issue can be closed in favour of #432

deekerman commented

2026-02-28 02:06:00 -05:00

Author

Owner

@Computroniks commented on GitHub (Aug 16, 2023):

In issue #432 Kuma is used to getting value in TXT.

Not quite true. TXT is just one example of said issue:

DNS should have a 'keyword'-like field

=> I think this issue can be closed in favour of #432

I would argue that these are separate issues. The serial in the SOA record is updated each time the DNS records are updated. If the three authoritative servers are returning different serials, one or more of them is serving an old zone file. What makes this different is that we are not looking for a specific keyword, we are looking for a match between the three servers. Whilst this could be implemented with a key work check, the key word would have to be updated each time the zone file is updated (the serial of the zone must be increased on each update in order to propagate changes).

@Computroniks commented on GitHub (Aug 16, 2023): > > In issue #432 Kuma is used to getting value in TXT. > > Not quite true. TXT is just one example of said issue: > > > DNS should have a 'keyword'-like field > > => I think this issue can be closed in favour of #432 > I would argue that these are separate issues. The serial in the SOA record is updated each time the DNS records are updated. If the three authoritative servers are returning different serials, one or more of them is serving an old zone file. What makes this different is that we are not looking for a specific keyword, we are looking for a match between the three servers. Whilst this could be implemented with a key work check, the key word would have to be updated each time the zone file is updated (the serial of the zone must be increased on each update in order to propagate changes).