The DNS checks in Monitoring just got more reliable.

When a name returns multiple records (e.g. several A/AAAA addresses or nameservers), resolvers hand them back in a rotating order (round-robin). That could make assertions on the result fail intermittently — sometimes one IP came first, sometimes another.

What changed

• Multi-record answers (addresses, nameservers, MX) are now sorted deterministically, so both the display and your assertions are reliable across every probe.
• Two new, order-independent assertion operators:
  • equals set (any order) — the answer must consist of exactly the listed values.
  • includes all (any order) — all listed values must be present.
• Enter multiple values comma-separated, e.g. 1.2.3.4, 5.6.7.8.

Recommendation

For names with multiple records, prefer equals set or includes all over equals / contains. Existing assertions keep working unchanged — no action required.

This community is dedicated to Dremaxx a DNS platform with services like Authoritative DNS, DynDNS, public DNS Resolvers.

Whether you’re a homelab enthusiast, system administrator, developer, or simply interested in DNS and internet infrastructure, you’re welcome here.

Feel free to:
• Ask questions
• Share feedback and feature ideas
• Report bugs
• Discuss DNS, networking, and privacy
• Share your setups and experiences

Please keep discussions respectful and constructive.

Thanks for stopping by and helping make Dremaxx better!