This one is for whoever configures DNS — but also for any .mk owner who wonders why a site sometimes vanishes after a migration.
The new checker: tools.marnet.mk
In April 2026 MARnet launched a DNS parameter checking tool at tools.marnet.mk, with a web interface and an API so registrars can automate checks in their own systems.
Rule 1: the zone first, the change second
MARnet is explicit: before any nameserver change, the zone must already be active on the new servers. Wrong configuration causes DNS instability. The reverse order is the classic cause of a day-long outage.
Rule 2: when an IP belongs in an NS record (glue records)
- Allowed and needed — only when the nameserver is a subdomain of the domain itself: for
firma.mkyou usens1.firma.mk. Without glue there is a circular dependency. - Not allowed — when the nameserver is external, e.g.
ns1.provider.com. No IP is entered there.
Records that do not comply are treated as technically invalid. Registrars were given ten days to audit and clean up unnecessary IP addresses.
Why it matters to you
A wrong glue record means resolvers keep an old IP. The result: the site works for part of the world and not for the rest — the hardest failure to diagnose, because it works for me.
Migration checklist
- Zone active on the new server (tested) · TTL lowered in advance · NS changed last · checked via tools.marnet.mk · glue correct if you use your own nameservers · MX not forgotten — mail fails first and most quietly
Source: MARnet announcement of 14 April 2026 (marnet.mk).