Hostname, password, and networking settings are configured automatically via cloud-init. This applies to standard operating system installations that support cloud-init. However, if you are:
You will need to manually configure networking, security settings, and hostname within the operating system, as cloud-init will not be available in these scenarios.
Instantly compare what this service is entitled to with how much it is consuming right now.
Values refresh alongside the live status poll.
{{ $resource['label'] }}
{{ $resource['usage_summary'] }}
{{ $resource['entitlement_label'] }}
{{ $resource['description'] }}
Configuration and access information
Real-time bandwidth monitoring • Updates every 30 seconds
Loading live network statistics…
IPv6 DNS records for your server
IPv6-based DNS records for {{ $server->primaryIpv6->ip }}
@ points the root domain directly to the server IP ({{ $server->primaryIpv6->ip }})
*.@ points all subdomains (wildcard) to the same IP ({{ $server->primaryIpv6->ip }})
@ — Represents the root domain (also called the apex domain).
This means the base domain name (e.g. example.com) will point directly to the server IP.
*.@ — Represents a wildcard record.
This ensures that any subdomain also points to the same server IP.
Together, using both @ and *.@ ensures that your server will respond to requests for the root domain and all possible subdomains.
rDNS PTR Records: Please make note that at no time will PTR records be generated for any IP address via the RIR systems. No exceptions will be made other than for direct contract business customers due to the security risks involved with allowing arbitrary PTR records to be set and the potential for abuse.
Store notes about this server, Markdown is supported. (These do not persist reinstalls)
No notes stored. Click Edit to add notes.
@endifInstallation and configuration notes
Windows Server Networking (IPv4/IPv6 Setup):
Cloud-init does not automatically configure IPv4 or IPv6 networking on Windows Server installations. Please configure the addresses manually as assigned in the control panel of your installation.
Windows Server Activation (Licensing):
No Windows Server license key is provided by Virtnet.bond. It is the responsibility of the account holder to provide and maintain active and compliant licensing with all Windows Server products.
Periodic Licensing Audits and User Compliance:
Virtnet.bond reserves the right to perform periodic audits of Windows Server installations to ensure compliance with Microsoft's licensing terms. Non-compliant installations may be subject to suspension or termination. If you have any questions regarding licensing compliance, please contact our support team.