# IP addresses, additional IPv4, hostname and DNS resolver settings

https://www.hostimor.com/en/knowledgebase/article/ip-addresses-additional-ipv4-hostname-dns

On Hostimor VDS and VPS servers, IPv4 addresses, additional IPs, the hostname and DNS resolvers are managed from the client area. This guide shows where each setting lives in the panel, how to verify a change from inside the server and how to fix the most common mistakes.

## How is your server's IP address assigned?

Every VDS and VPS comes with a 1 Gbit port and one dedicated IPv4 address. This main address is assigned to your server statically from Hostimor's IP pool and appears in the IP Address row of the **Sign-in Details** card on your service page in the client area. Networking is configured automatically during setup; DHCP is not available.

Servers do not get IPv6 addresses; connectivity is IPv4 only. For that reason, do not publish an AAAA record pointing to this server in your domain's DNS zone. A stray AAAA record sends IPv6 visitors and validation services such as Let's Encrypt to some other address instead of your server.

You can see the current address, the default gateway and the source address of outbound traffic from inside the server with the commands below. Run the commands in this guide as root or with `sudo`.

```
# IPv4 addresses on the interfaces
ip -4 addr show
# Default gateway and routing table
ip -4 route
# Source address of outbound traffic (the "src" field)
ip route get 1.1.1.1
```

The `src` value in the output of the last command shows which address the server uses to connect out. Normally it is your main IP address.

### Do not change network settings by hand

The IP address, netmask, gateway and DNS settings are written into the operating system by the panel's automation. Editing these files by hand, mistyping the address or switching the interface to DHCP cuts the server's network connection immediately: your SSH or RDP session drops and the server becomes unreachable over the network. Where the network configuration is stored depends on the distribution and the template. Look at the following locations for inspection only:

- **Ubuntu:** Netplan files, `/etc/netplan/*.yaml`.
- **Debian:** `/etc/network/interfaces` and `/etc/network/interfaces.d/`; Netplan on some installations.
- **AlmaLinux:** NetworkManager connection files, `/etc/NetworkManager/system-connections/`; run `nmcli connection show` for a summary.

> ****Warning****
> 
> If the network settings are broken, use the **VNC Console** in the panel to reach the server's screen independently of the network, undo your manual change if needed and then reapply the panel's settings with the **Network Config** tool. Never add an address that has not been assigned to you; it causes an address conflict with another server on the same network.

## Adding and removing additional IP addresses

Your IP allowance is the number of addresses included in your package plus any additional IPv4 service you have purchased. The **Additional IPs** tool lets you add or remove addresses on your server up to that allowance. The main IP address cannot be removed with this tool. If your allowance is used up, you can upgrade your package or, where your package supports it, order the additional IPv4 service; see the [resource upgrade guide](https://www.hostimor.com/en/knowledgebase/article/resource-upgrade-cpu-ram-disk) for the options.

1. Open your server service in the client area and go to the **Additional IPs** tool.
2. Make sure the server is running. The address is written into the operating system automatically while the server is on and VMware Tools is running; a change saved while the server is off is applied once it starts and Tools is running.
3. Add the address and wait for the task to finish. Added addresses are also listed in the Additional IP row of the **Sign-in Details** card.
4. Verify with the commands below that the address shows up in the operating system.
5. Configure the services that will use the address (web server, mail server) and review your firewall rules.

### Verifying on Linux and sending traffic from a specific IP

The additional address usually appears as a second `inet` line on the same network interface as the main address. On Linux, outbound connections leave from the main IP by default, and in most scenarios it is enough to use the additional address for incoming connections only. If an application must connect out from the additional address, use that application's own bind setting instead of changing the routing table.

```
# Is the additional address on the interface?
ip -4 addr show | grep 203.0.113.11
# Routing decision for traffic leaving from this address
ip route get 1.1.1.1 from 203.0.113.11
# Send a single request from the additional address
curl --interface 203.0.113.11 -sI https://example.com | head -n 1
# Make Postfix connect out from the additional address
postconf -e 'smtp_bind_address = 203.0.113.11'
systemctl reload postfix
```

For incoming traffic, what matters is which address the service listens on. For example, to serve a site in Nginx only from the additional address, put the address in the `listen` directive. For HTTPS you use the same address with port 443 together with your certificate settings.

```
server {
    # This site answers only on the additional IP address
    listen 203.0.113.11:80;
    server_name shop.example.com;
    root /var/www/shop.example.com/public;
}
```

After the change, test the configuration with `nginx -t` and reload it with `systemctl reload nginx`. Run `ss -tlnp` to see which service listens on which address and port.

### Verifying on Windows and SkipAsSource

On Windows servers, additional IPs are added with the SkipAsSource option. It keeps the address from being chosen as the source for outbound connections: the server connects out from the main IP, while the additional addresses serve incoming connections (IIS site bindings, for example). Leave this setting applied by the panel as it is; if an application must connect out from an additional address, use its bind setting.

```
# IPv4 addresses and their SkipAsSource state
Get-NetIPAddress -AddressFamily IPv4 | Format-Table IPAddress, PrefixLength, InterfaceAlias, SkipAsSource
# Detailed network information (addresses, gateway, DNS)
ipconfig /all
# Source address that outbound traffic will use
Find-NetRoute -RemoteIPAddress 1.1.1.1 | Select-Object -First 1 IPAddress, InterfaceAlias
```

In the output, the main IP address should show SkipAsSource as False and the additional addresses as True.

## Setting the hostname

The hostname is the name the server uses to identify itself; mail servers, control panels and log entries all rely on it. Set it with the **Change Hostname** tool. The tool accepts only lowercase letters, digits, hyphens and dots. Instead of a single word, we recommend a fully qualified domain name (FQDN) such as `server1.example.com`. On Windows servers this changes the computer name and the server restarts, so schedule it for a quiet hour.

For the FQDN to actually work, create an A record for that name in your domain's DNS management, pointing to the server's main IP address. See the [DNS records guide](https://www.hostimor.com/en/dns-records-what-do-a-aaaa-cname-mx-txt-and-ns-do) for record types and the [DNS propagation and TTL page](https://www.hostimor.com/en/dns-propagation-and-ttl-why-dont-changes-appear-for-everyone) for how long changes take to reach everyone. Then verify the name from inside the server:

```
# The name the system reports, with details
hostnamectl
# Short name and fully qualified name
hostname -s
hostname -f
# The name's entry in /etc/hosts
grep -i server1 /etc/hosts
# Does the A record point to the main IP?
dig +short server1.example.com A
```

If `hostname -f` returns the short name instead of the full name, or fails, `/etc/hosts` may have no line for the name. The convention on Debian and Ubuntu is to map the name to `127.0.1.1`. If you are going to run a mail server or a control panel, mapping the name to the main IP address is a better fit. The line lists the FQDN first, then the short name:

```
203.0.113.10   server1.example.com   server1
```

If you change the name inside the server with `hostnamectl set-hostname`, the panel record may keep the old name, so making the change from the panel is more consistent. If cloud-init is installed on the server and the name reverts on every reboot, check the `preserve_hostname` setting in `/etc/cloud/cloud.cfg`.

## DNS resolver settings

DNS resolvers are the servers your server queries to turn domain names into IP addresses. Package repositories, API calls and outgoing mail all depend on these lookups. Set the resolvers with the **Network Config** tool. The tool accepts IPv4 addresses only; 1.1.1.1 (Cloudflare), 8.8.8.8 (Google) and 9.9.9.9 (Quad9) are common public resolvers. When you save, the tool reapplies the network settings along with the DNS settings. Do not edit `/etc/resolv.conf` by hand; system services or the panel may overwrite it.

How you see the active resolvers depends on the distribution:

- **Ubuntu:** systemd-resolved is used. `/etc/resolv.conf` lists only the local stub resolver `127.0.0.53`; `resolvectl status` or `resolvectl dns` shows the real resolvers.
- **Debian 12 and 13:** A default installation usually has no systemd-resolved; the resolvers are listed directly in the `nameserver` lines of `/etc/resolv.conf`.
- **AlmaLinux 9:** NetworkManager generates `/etc/resolv.conf`; run `nmcli dev show | grep -i dns` to see the resolvers assigned to the interface.

```
# Install dig if needed
apt install bind9-dnsutils     # Debian / Ubuntu
dnf install bind-utils         # AlmaLinux
# Query through the system resolver
dig +short example.com A
getent hosts example.com
# Query a specific resolver directly
dig @1.1.1.1 +short example.com A
# Active resolvers: Ubuntu / AlmaLinux / Debian
resolvectl status
nmcli dev show | grep -i dns
cat /etc/resolv.conf
```

If a lookup through the system resolver fails while `dig @1.1.1.1` answers, the problem is the resolver setting on the server; reapply the resolvers with **Network Config**. If both fail, check whether a firewall rule blocks outbound UDP and TCP port 53. On Windows, run the same test with `nslookup example.com` and `Resolve-DnsName example.com`.

## Reverse DNS (PTR) records

Reverse DNS, or a PTR record, tells which name an IP address belongs to. Websites rarely need it, but if you plan to send mail directly from your server, most receiving servers check this record. PTR records are not set from the panel: send your request with the IP address and the name you want in a support ticket. Whether it can be applied is evaluated based on the IP block. The [support ticket guide](https://www.hostimor.com/en/knowledgebase/article/what-information-should-you-include-in-a-support-ticket) explains what to include in your request.

Before you ask, make sure the name's A record points to the same IP address. Forward and reverse records confirming each other (forward-confirmed reverse DNS) matters for mail delivery. On a mail server, the HELO/EHLO name, the hostname and the PTR record should be the same FQDN. For SPF, DKIM and DMARC records, see our [business email guide](https://www.hostimor.com/en/spf-dkim-and-dmarc-guide-for-business-email).

```
# PTR record of the IP address
dig -x 203.0.113.10 +short
# The name's A record must point to the same IP
dig +short server1.example.com A
# The name Postfix introduces itself with
postconf myhostname
```

## Troubleshooting: VMware Tools and the task log

All IP, hostname and DNS tasks are applied inside the server through VMware Tools (open-vm-tools on Linux); if this service is not running, a change you save in the panel cannot be written to the server. The table below lists the panel tool for each job and how to verify the result.

| Job | Panel tool | Verify inside the server |
| --- | --- | --- |
| Add or remove an additional IP | **Additional IPs** | `ip -4 addr show`, on Windows `Get-NetIPAddress` |
| Change the hostname | **Change Hostname** | `hostnamectl`, `hostname -f` |
| Set DNS resolvers | **Network Config** | `resolvectl status` or `cat /etc/resolv.conf` |
| Repair broken network settings | **VNC Console** and **Network Config** | `ip -4 route`, `ping -c 3 1.1.1.1` |
| Reverse DNS (PTR) record | Support ticket | `dig -x 203.0.113.10 +short` |
| Track completed tasks | **Activity Log** | `/var/log/wisecp-task.log` |

Panel tasks are written to a log inside the server: `/var/log/wisecp-task.log` on Linux and `C:\Windows\Temp\wisecp-task.log` on Windows. If a task did not end as expected, check the service status first and then this log:

```
# Is the open-vm-tools service running?
systemctl status open-vm-tools   # Debian / Ubuntu
systemctl status vmtoolsd        # AlmaLinux
# In-server log of panel tasks
tail -n 50 /var/log/wisecp-task.log
```

```
# Is the VMware Tools service running?
Get-Service VMTools
# In-server log of panel tasks
Get-Content C:\Windows\Temp\wisecp-task.log -Tail 50
```

> ****Note****
> 
> Do not remove the open-vm-tools package or stop its service. Panel tasks such as adding an additional IP, changing the hostname, setting DNS, resetting the password and a graceful shutdown all depend on it.

- **The additional IP is listed in the panel but not on the server:** Check that the server is on and VMware Tools is running. The change is applied once Tools starts; the task log has the details.
- **"Temporary failure in name resolution":** Check the resolver setting, compare with `dig @1.1.1.1` and reapply the resolvers from the panel if needed.
- **A panel task failed:** Add the relevant lines from the **Activity Log** and the task log to your support ticket. Never share passwords or one-time codes.

## Frequently asked questions

### Can I configure an IPv6 address on my server?

No. Servers run on IPv4 only and no IPv6 addresses are assigned. Do not publish an AAAA record pointing to this server for your domain; use A records only.

### Can I remove or change my main IP address?

The main IP address cannot be removed with the **Additional IPs** tool. If you have a different need regarding the address, send it in a support ticket.

## Related articles

- [Reach your server without SSH or RDP using the VNC Console](https://www.hostimor.com/en/knowledgebase/article/access-your-server-with-the-vnc-console)
- [Your first 30 minutes on a new VDS or VPS: a post-setup checklist](https://www.hostimor.com/en/knowledgebase/article/first-30-minutes-on-a-new-vds-or-vps-checklist)
- [What changes on your server after a CPU, RAM or disk upgrade?](https://www.hostimor.com/en/knowledgebase/article/resource-upgrade-cpu-ram-disk)
- [Setting up a Linux firewall with UFW and firewalld](https://www.hostimor.com/en/knowledgebase/article/linux-firewall-with-ufw-and-firewalld)
- [Free SSL certificates with Let's Encrypt (Certbot) and automatic renewal](https://www.hostimor.com/en/knowledgebase/article/lets-encrypt-certbot-free-ssl)
