OK to use DHCP address for PBS?

[aweber1nj]

I have my VE server running a few months now and really like it. Setting up a PBS server over the holiday break, so it's "new to me".

Is it OK if I setup the PBS with a DHCP address as long as the name is resolved consistently on my LAN?

If so, is there an easy way to do this during installation or initial configuration?

Thanks in advance. Looking forward to getting it running!

 

[sb-jw]

You should never assign a DHCP address to a server, always a static one. If your DHCP server fails and your leases expire, your network is completely down.

 

[aweber1nj]

You should never assign a DHCP address to a server, always a static one. If your DHCP server fails and your leases expire, your network is completely down.

OK, I'm not really skilled with Proxmox VE or PBS, but I've worked my way around networks for a very long time. No offense, but this is a broad generalization and not actually true. Your network will not be "down". Thank you though.

Is there some reason the VE server needs to contact the PBS via static IP address, or will it use Debian-based name resolution?

 

[sb-jw]

but I've worked my way around networks for a very long time

But then you should also know that DHCP is not used in the data center for productive systems. To jump into your experience, I also have over 10 years of experience in the data center sector and also operate my own infrastructure in the data center. For me, the principle "no DHCP for servers" is the rule and is implemented that way.

Since you also have sufficient experience, you have to know the advantages and disadvantages as well as any problems yourself.

Is there some reason the VE server needs to contact the PBS via static IP address, or will it use Debian-based name resolution?

If you have worked in the network area, then you should also know how DNS works and that servers can also communicate wonderfully with it. I can't immediately think of any use case in which I would necessarily need an IP address because otherwise something wouldn't work. I exclude cases such as iSCSI or CEPH (or simply called SAN), where you simply don't do anything with DNS names.

Ultimately, the only important thing is that there is a DNS server that is used by everyone and that all records are known there. Of course it should also be stable and available.

Yes, and please excuse me for harping on your experience - but if you advertise it so aggressively, then I'll have to jump on it ;-)

 

[aweber1nj]

Maybe I should have included additional details to begin with.

This is a SOHO deployment, not a full-blown datacenter with sizable resources, run books, and staff. Using DHCP with a standby server/service in my case simplifies deployment and flexibility. Typically, and probably in this case, I would reserve the DHCP address to the MAC and straddle that middle ground between flexibility and consistency.

It is obvious you've been around the block as we older kids say, as you readily reference a protocol and storage solution that DO require more static IP address configuration. If the VE refers to PBS "targets" (probably not the correct term) via hostname/FQDN, that's really all I was asking.

Thanks again for the quick replies, and Happy Holidays.

 

[TErxleben]

But then you should also know that DHCP is not used in the data center for productive systems. To jump into your experience, I also have over 10 years of experience in the data center sector and also operate my own infrastructure in the data center. For me, the principle "no DHCP for servers" is the rule and is implemented that way.

Since you also have sufficient experience, you have to know the advantages and disadvantages as well as any problems yourself.


If you have worked in the network area, then you should also know how DNS works and that servers can also communicate wonderfully with it. I can't immediately think of any use case in which I would necessarily need an IP address because otherwise something wouldn't work. I exclude cases such as iSCSI or CEPH (or simply called SAN), where you simply don't do anything with DNS names.

Ultimately, the only important thing is that there is a DNS server that is used by everyone and that all records are known there. Of course it should also be stable and available.

Yes, and please excuse me for harping on your experience - but if you advertise it so aggressively, then I'll have to jump on it ;-)

If you aren't able to implement a reliable DNS/DHCP environment in your datacenter, dont't "manage" this!
Maybe the 90' calling?
Today, for example, it is important to operate a PBS with a weak internet connection. In the worst case scenario, I would like to automatically integrate this into the actual network via taxi. Stupid idea if DHCP/DNS doesn't work.

DHCP would be extremely appropriate. Nobody is stopping you from still settling the matter with a fixed IP

 

[springbd]

I also wish to have this option as i use tailscale to log into my pBS and will be shipping it off to family who can barely handle emailing. I will not have the ability to guarantee the IP scheme of a router change and wish not to drive hundreds of miles to change the settings.