Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement] In reverse zone views like 8.168.192.in-addr.arpa sorting by name as numbers #1079

Open
LightTemplar opened this issue Oct 17, 2024 · 3 comments

Comments

@LightTemplar
Copy link

In reverse zone views name field is a part of IP address, also - number. I suggest to sort it not alphabetically, but as numbers, i.e. not "1, 102, 2, 201, 3" but "1, 2, 3, 102, 201"

@ShreyasZare
Copy link
Member

Thanks for the request. The default sort order is as per the DNS name ordering in lexical form which is the same for all the zones. This order allows manually inspecting records when the zone is signed with DNSSEC. The other thing is that the records can contain two octets if the reverse zone is for a /16 network. The table view component sorts only the listed entries that are visible so changing that too would give inconsistent results.

@LightTemplar
Copy link
Author

LightTemplar commented Oct 18, 2024

The default sort order is as per the DNS name ordering in lexical form which is the same for all the zones.

I would suggest then switching between sorting modes on every click. And this would possibly need to add some sort of indication of current mode, which (I imagine) could work with following after column name: ↓ᵃᵇᶜ, ↑ᵃᵇᶜ, ↓¹²³, ↑¹²³.

The other thing is that the records can contain two octets

And those could be sorted as numbers too: first octet, then second (then third) etc.

The table view component sorts only the listed entries that are visible

If I need to inspect them sorted I will (and already do) let it show max possible rows at once.

@ShreyasZare
Copy link
Member

Will see how this can be implemented. It will however take a while for this to be available since there is already some core features planned for next few major releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants