What is the point of owning public address space?

Anything in your private network (even if it goes over public internet) should be encrypted and locked up anyway. Something like Wireguard or Nebula only needs a few (maybe just one) publicly accessible address. Inside the overlay network, it's easy to keep IP addresses stable.

Anything public-facing likely needs a DNS record, updatable quickly when the IP of a publicly accessible interface changes (infrequently).

What am I missing?

▲

direwolf20 4 hours ago | parent | next [-]

The realistic point is to have your own abuse email contact, to evade the banhappy policies that most server hosts have even when you did nothing wrong. Usually they suspend your account if you don't reply within 24 hours, even if the complaint is obvious nonsense.

▲

cyberax 3 hours ago | parent | prev | next [-]

It's the only real way of running reliable IPv6 networks with multiple uplinks. Unless you want NATv6.

▲

kortilla 2 hours ago | parent | prev [-]

DNS updates are slow. BGP can react to a downed link in <1 sec.

	▲	zamadatix 7 minutes ago \| parent [-]
		I have both my own multihomed ASN and operate my own nameservers. The latter has usually been about as fast overall in practice. BGP may look to converge near instantly from your 2-3 peer outbound perspective but the inbound convergence from the rest of the internet is much slower and has a very long tail very akin to trying to set your DNS TTL to 0 and having the rest of the internet decide to do it slower for cache/churn reasons anyways.