IP Address Management (IPAM)#
Every atom in the universe has a position. Every device on the internet has an IP address. The difference is that if you lose your IP address, your atoms won't scatter — but your customers might.
IPAM (IP Address Management) lets you view all your allocated IPv4 and IPv6 addresses from a single panel, manage them, and configure rDNS records. Grab your towel and head to Hub > IPAM.
Your Allocated IP Addresses#
When you open the IPAM page, you'll see all IP addresses assigned to you in a table:
| Column | Description |
|---|---|
| IP Address | IPv4 or IPv6 address |
| Subnet | The subnet it belongs to (e.g. /29, /64) |
| VLAN | Associated VLAN ID and name |
| rDNS (PTR) | Current reverse DNS record |
| Status | Active, reserved, or available |
| Assignment | Which service it's assigned to (VPS, server, etc.) |
IPv6 or IPv4?
Both. VeriTeknik provides dual-stack (IPv4 + IPv6) support to all customers. IPv6 addresses may seem infinite — there are more combinations than atoms in the universe — but it's still worth keeping them tidy. Even Zaphod can manage his two heads without mixing them up.
IP Pool Management#
IP pools represent the address blocks allocated to you. Each pool corresponds to a subnet:
- Pool name — a descriptive label (e.g. "Ankara DC - Web Servers")
- Subnet — the network block in CIDR notation (e.g.
185.96.170.0/24) - Usage — how many addresses are in use vs. available
- Type — IPv4 or IPv6
Click into a pool to see the status and assignment of every IP address within that subnet. To assign available addresses to new services, you can create a support ticket.
IP allocation
New IP address requests are evaluated in accordance with RIPE policies. VeriTeknik, as a RIPE LIR (AS15755), processes IP allocations through official procedures. Asking for a /24 isn't quite as easy as requesting a new planet in the galaxy — but we do our best.
Subnet Tracking#
Detailed information for each subnet:
| Field | Description |
|---|---|
| CIDR | Network block notation (e.g. 10.0.1.0/24) |
| Gateway | Default gateway address |
| Broadcast | Broadcast address |
| Usable IPs | Total number of usable addresses |
| In Use | Currently assigned address count |
| Utilization | Percentage usage |
Subnet tracking is especially useful when you manage multiple servers and services — you can see at a glance which addresses are free. The cover of the Hitchhiker's Guide said "Don't Panic" — and if your subnets are in order, there's really no reason to.
rDNS (Reverse DNS) Management#
rDNS maps an IP address back to a domain name. It's practically mandatory for mail servers — because most email providers check the PTR record of the sender's IP address.
Setting a PTR Record#
- Go to the IPAM page
- Click Edit PTR on the row of the IP address you want to configure
- Enter the domain name you want the reverse DNS to resolve to (e.g.
mail.yourcompany.com) - Save — the change propagates shortly
Email delivery and rDNS
If your mail server's IP address doesn't have a PTR record, your emails may land in spam or be rejected entirely. Gmail, Outlook, and other major providers perform PTR checks. This is one of the fundamental laws of the universe: messages that can't prove their identity vanish into the void. Set your PTR record now.
rDNS Rules#
- The PTR record must point to a valid domain name
- Forward DNS (A/AAAA) and reverse DNS (PTR) should match (FCrDNS)
- Changes typically propagate within 15-30 minutes
- Only one PTR record can be defined per IP address
What is FCrDNS?
Forward-Confirmed reverse DNS: if the PTR record of an IP address points to mail.example.com, then the A record of mail.example.com must resolve back to the same IP address. This two-way verification is the email world's equivalent of "show me your towel."
VLAN Information#
On the IPAM page, you can also see the VLAN details for each IP address:
| Field | Description |
|---|---|
| VLAN ID | Virtual network number (e.g. 100, 200) |
| VLAN Name | Descriptive label (e.g. "Web DMZ", "Database") |
| Location | Which data center |
| IP Range | Subnet assigned to the VLAN |
VLAN information is particularly useful for complex architectures spanning multiple network segments. Knowing which IP is in which VLAN is as important as knowing your own location on the galactic map.
IP Conflict Detection#
When two devices try to use the same IP address, neither works properly. The IPAM system automatically detects these conflicts:
- Conflict alerts — instant notification when multiple devices share an IP
- ARP table monitoring — real MAC-IP mappings are tracked on the network
- History logs — see who an IP address was previously assigned to
IP conflict detected!
If you see a red conflict warning in the IPAM panel, act immediately. IP conflicts cause network outages. Contact our support team or change the IP configuration on one of the conflicting devices. When two people try to pilot the same spaceship, both crash.
Accessing from the Hub#
You can reach the IPAM panel via:
- Navigate to veriteknik.com/hub/ipam
- Or click IPAM in the left sidebar of the Hub panel
All operations — IP listing, rDNS management, subnet viewing — are handled through this panel.
Need help?
IP address management doesn't have to be as complex as answering the Ultimate Question. If you need help with rDNS configuration, subnet planning, or IP allocation, write to destek@veriteknik.com. We respond faster and more usefully than Deep Thought — with a real solution instead of just "42."