"Last Used" timestamp never updates on authoritative zone records (A, AAAA, CNAME)

[raphaelprencipe-creator]

Hi,

I noticed that the "Last Used" timestamp on authoritative zone records never updates, even after querying them directly.

Setup:

• Technitium DNS as both recursive resolver and authoritative server for internal zone home.0n1.lab
• Windows 11 client configured with Technitium as DNS server (via DHCP)

What I observe:

• The SOA record does show a real "Last Used" timestamp
• All A, AAAA, and CNAME records in the zone show Last Used: 0001-01-01 00:00:00 (never)
• Even after explicitly querying a record via PowerShell (Resolve-DnsName beszel.home.0n1.lab -Server 192.168.0.15), which returns the correct answer, the "Last Used" field remains never

Question:
Is the "Last Used" timestamp on individual zone records (A, AAAA, CNAME) expected to update when those records are served to clients? If so, is there a setting to enable this behavior, or is it only tracked for specific record types (e.g., SOA)?

Thank you.

[ShreyasZare]

Thanks for the post. The Last Used time stamp is updating here for all zones that I checked. So not sure what could be the issue. Do you see the queries you make in the Query Logs? Try querying using the DNS Client tool on the admin panel and check the record state again.

[raphaelprencipe-creator]

Queries do appear in the Query Logs as Authoritative / NoError. I also tested with the built-in DNS Client tool and resolution works correctly. However, the "Last Used" field still shows never on the zone records after these queries.
I also noticed that the JSON response from the DNS Client does not include a lastUsedOn field in the Answer section, unlike what I've seen for cached records in other issues.
Could it be that "Last Used" tracking is only implemented for cache records and not for authoritative zone records?

[ShreyasZare]

Are you refreshing the zone records using the refresh icon that comes after the zone's name?

Its working well here for all cases.

[raphaelprencipe-creator]

Found it! The "Last Used" timestamp does update, but only when viewing records through the cluster interface. In the regular zone view, it stays at never. Looks like a UI display bug — the cluster view refreshes the timestamp correctly but the standard zone view does not.

[ShreyasZare]

Not sure what you are saying here. Please share screenshots.

[raphaelprencipe-creator]

Before!

[raphaelprencipe-creator]

But now it works!!

[ShreyasZare]

Good to know its working now.