Skip to content
DNS-Editor

Inventory and Search

The Inventory (binoculars icon in the header, /inventory) answers two questions that get lost inside individual projects: What do I actually have? and Where is this value used?

Inventory

Section titled “Inventory”

The overview lists every reachable zone with provider, account, project, and number of record sets — along with key figures on domains, zones, providers, and projects.

If the same domain lives under multiple accounts — for instance during a provider migration — its zones appear grouped under a domain heading. The core model remains untouched: a zone still belongs to exactly one account; only the view looks across.

Subzones sit indented below their zone, just as in the zone overview. The number on the zone’s row is the total of its record sets — what stands at the provider; the subzone numbers below it are a breakdown of that, which is why they read “of which”.

Section titled “Search”

The search spans the record sets of all zones at once:

Inventory search with hits across multiple zones

  • Name — shop
  • Full name — shop.example.com
  • Value — 198.51.100.7, a substring is enough

Three facets filter on top: record type, provider, and project. A click on a hit takes you straight to its location.

Hits inside subzones

Section titled “Hits inside subzones”

If an entry belongs to a subzone, the Location column names the subzone rather than the zone — and the name beside it is relative to it. An entry www.dev in example.com therefore reads www with the location dev.example.com; only together do they make the full name. The click goes into the subzone accordingly, because the zone view hides its entries.

Matching still happens on the full name: typing dev finds the entries of subzone dev, even though they are called www there.

Typical questions this answers: What still points at the old load balancer? Which domains have no DMARC? Where is this mail server entry?

Limits

Section titled “Limits”
  • The result list is capped at 200 hits. If it is cut off, the interface says so explicitly — nothing is truncated silently.
  • Only zones the signed-in user has access to are considered. Anyone restricted to individual zones of a project sees only those in the Inventory as well.