The inventory collapsed rows that shared a name, domain, address and type, which was meant to hide the alias records searchhostoverride lists alongside their parent. It hid genuine duplicates too — and since sync_dns_zone deletes what the inventory tells it about, it could only ever remove one copy per name before adding a fresh one. A pile of identical overrides could grow but never shrink. An office firewall reached fifteen identical A records for its own name, all tagged [netork], while netOrk's database showed one. OPNsense flags alias rows with isAlias, so filter on that and report every remaining row under its own UUID. Releases that predate the flag give no way to tell an alias from a copy, so the content collapse stays as a fallback there. sync_dns_zone now also pushes one override per logical record, because two netOrk rows for one host is a state its database can legitimately be in. The auto-PTR flag is read from addptr, which is what OPNsense 26.1 returns; ptrrecord was absent from every row, so the default made every A record claim it managed a PTR — and netOrk derives reverse-zone entries from exactly that flag. addptr now goes out on writes alongside the legacy name. Refs christianmanivong/netork#103, christianmanivong/netork#107