Why the smallest VPS includes two IPv4

The smallest LogicWeb VPS includes two IPv4 addresses so you can split services or keep a spare. You can run the site on one address and mail on the other, or hold the second for a hostname move. These are two individual addresses on the same guest, not a /29, not a routed prefix, and not anycast. Each address has its own reverse DNS. Use both on purpose, or leave the second quiet until you need it.

What the two addresses are for

A clean split is one address for the website and one for mail. You can also keep one in production and one free while you move a name. A spare means a future LOA or second vhost does not wait on a ticket. Two addresses are not twice the bandwidth. They are two doors on the same KVM guest. IPv6 is on as well, so dual-stack adds AAAA as another path. Count every address when you write allow-lists. A routed prefix is separate paperwork. Two IPv4 on the guest remain two addresses on that guest.

Mail reputation, SPF, and rDNS

SPF and PTR must match the IP that actually connects. If Postfix binds the second address while the site uses the first, mail reputation lives on the second. WHOIS on the primary will not fix a mismatch. Check the Received header on a test message, not only the dashboard label. Payment processors often allow-list one IP while mail leaves from the other, and then the processor sees a stranger. Set rDNS on the address that HELOs. Publish SPF for the address that sends.

Confirm the numbers on the guest

The guest reports the real addresses. Dashboard labels are not the envelope your peers see.

ip -br a

Pair that output with the Received header from a test message. Note both addresses and which job each one has. Saying “the VPS IP” is not enough when a firewall only allows one of them. Name the exact address in any ticket or allow-list request.

Assign rDNS for both addresses if both will ever send mail. If the second stays a spare, avoid A records you do not mean. Publishing an unused IP that points at nothing listening invites scanners. Write both addresses into your runbook so a later allow-list does not target the wrong one. For how those addresses sit on the guest, see what KVM actually virtualizes.