Apr 12, 2026 · Written by: Netspare Team

Dedicated IPv4, IPv6, TLS Certificates, and rDNS on a Public Server

A public server’s IP addresses participate in TLS, firewall rules, email reputation, and sometimes regulatory evidence. IPv4 scarcity and IPv6 adoption change how you document and test connectivity.

Forward DNS (name → address) and reverse DNS (address → PTR name) are independent; both must be coherent when mail servers or strict APIs validate your host.

Dual stack and certificate coverage

If you advertise AAAA records, ensure your TLS certificate includes the same hostname and that firewalls open the same ports for IPv6 as IPv4.

Some clients prefer IPv6 when present; broken AAAA records cause intermittent failures that look like “random” user issues.

Reverse DNS (PTR) basics

PTR is controlled by whoever owns the IP allocation (usually your provider), not your domain registrar. Request rDNS that matches the hostname used in SMTP banners.

Mismatched PTR/HELO is a common spam-score penalty on outbound mail.

TLS, SNI, and multiple sites per IP

Modern HTTPS relies on Server Name Indication to pick the correct certificate when many virtual hosts share one IP.

Very old clients without SNI are rare now but still appear in embedded systems—know your audience if you support legacy IoT.

Operational checklist

Document every elastic/floating IP and what service owns it.
After IP change, update SPF-related records if you send mail from that address space.
Test from outside your office network; split DNS hides mistakes.

Frequently asked questions

Do I need a dedicated IP for HTTPS?

Not for ordinary websites—SNI allows shared IPs. You may need dedicated IPs for certain legacy clients or provider-specific mail reputation workflows.

Why was my email rejected?

Often SPF/DKIM/DMARC, PTR mismatch, or blacklists. Collect the SMTP error text; it usually names the failing check.

Netspare Team