DNS is the solution. Going to "router.domain.local" or whatever your internal domain is, is easier to remember than.... Which subnet am I on again? Is this one 192.168.22.254? Or 192.168.21.1?

Stop punching in numbers like a cave man. Use DNS. You won't even notice if it's IPv6 after that

[–] Semi_Hemi_Demigod@lemmy.world 4 points 5 months ago* (last edited 5 months ago) (2 children)

And what happens when DNS inevitably falls over and I need to fix it?

And when I'm watching IP addresses scroll by, IPv6 ones are a lot harder to read than v4

[–] KillingTimeItself@lemmy.dbzer0.com 1 points 5 months ago (1 children)

some super gigabrained chad linux nerd will have written a tool to automatically configure it and have open sourced it.

You could probably just use that. I think like most things in life, the answer is automation.

[–] Semi_Hemi_Demigod@lemmy.world 2 points 5 months ago (1 children)

I wouldn't trust it unless I wrote it myself. And even then maybe not.

[–] KillingTimeItself@lemmy.dbzer0.com 1 points 5 months ago

well then go and do it manually, surely you as a human wouldn't make any mistakes. Would you?

[–] MystikIncarnate@lemmy.ca 1 points 5 months ago

DNS, by its very nature is redundant. So DNS shouldn't just fall over. If it does, you're doing something wrong.

If you absolutely need to go to IP addresses, they should be documented.

Unless DNS is outright wrong, there should not be an issue.

For scrolling: are you staring at active log files? Who isn't using a syslog aggregator? You can easily look up the IP of whatever device that is interesting and filter the log by that IP.