Well my entire network doc is a 30ish lines .txt file that looks like this example:

• Hostname11 10.0.0.11 master db1
• Hostname12 10.0.0.12 db1 backup
• Hostname13 10.0.0.13 ui back end 1
• Hostname21 10.0.0.21 master db2
• Hostname22 10.0.0.22 db2 backup
• Hostname23 10.0.0.23 ui back end 2

Then some other general stuff on some other 10.0.1.x network etc

Once you take care assigning static blocks and it makes sense you don’t have any surprises. Db1 crashed? Lookup its config data, reinstall machine, recover from backup and nothing else needs to be configured.

That is just static ip with extra steps

You can have some weird workaround creep up yesrs later also with dhcp and dns ,😉

No what I meant is I don’t use dhcp at all, but apparently I am an old gremlin and all these youngsters do it some variation of your way. If you want ro do it like that I leave you with them.

No worries, I just don’t want to get you confused

I agree with you. I am not at a scale were it matters so I don’t bother. I only have a couple dozen servers to harness for work. Point is that OP does not sound to be at that scale either

Dhcp and ensuring it works is someting I don’t care about. I tell the kernel wich packets it should be interested in and how to sign itself and that will be it thank you very much.

I configure static routes and have all my machines and network segments neatly arranged in my database. I setup a new machine I know exactly what address it should have,it goes up and until it has a problem it will keep the address it was installed with.

Its 2026 I work like that, you can have your opinions I have mine. The difference is that I depend on one less thing that I don’t care about, so I have more profit margin.

Is there a reason you sre using dhcp instead of assigning ips manually?

Dhcp is great if you don’t care about stuff, in my experiece as soon as you start caring you should do it manually