Network & ports
How you reach your server on NAT and dedicated-IP plans, what works outbound, and reverse DNS.
NAT plans
A NAT server has no public IPv4 of its own. You connect with SSH on a personal port shown in the dashboard (Windows servers: RDP on a personal port) — for example ssh -p 20123 root@host. Other inbound ports aren't reachable from the internet, so websites, mail servers, game servers and VPN endpoints need a dedicated-IP plan. Outbound connections work normally, which makes NAT a good fit for bots, agents, workers and scheduled jobs.
Dedicated-IP plans
A dedicated-IP server has its own public IPv4. SSH is on port 22 (RDP on 3389 for Windows), and any port you open in your firewall is reachable. You can switch a NAT server to a dedicated IP later without reinstalling — see Changing your plan.
Outbound traffic and email
All outbound traffic is allowed except the SMTP ports 25 and 465, which are closed by default on every plan to keep spam off our network. Sending through a mail provider on port 587 works. If you run a real mail server on a dedicated-IP plan, ask support to open port 25 and tell us what you'll be sending.
Reverse DNS (PTR)
On dedicated-IP plans you set the reverse DNS name of your IPv4 yourself from the server page — mail servers need it to match their hostname. NAT plans don't have an address of their own, so there's no PTR to set.
IPv6
Every plan is built around IPv4 — through NAT on NAT plans, directly on dedicated-IP plans. IPv6 isn't a guaranteed part of any plan yet, so don't build anything that depends on it.
Comments
No comments yet. Be the first.