DNS
Brightbox provides a number of dynamic DNS records for convenience.
| Record format | Response example | Description |
|---|---|---|
srv-xxxxx.gb1.brightbox.com |
|
Private IPv4 address of the Cloud Server |
ipv4.srv-xxxxx.gb1.brightbox.com |
|
Private IPv4 address of the Cloud Server |
ipv6.srv-xxxxx.gb1.brightbox.com |
|
IPv6 address of the Cloud Server |
public.srv-xxxxx.gb1.brightbox.com |
|
IPv4 and IPv6 address of the first Cloud IP mapped to the Cloud Server. Returns NXDOMAIN if no Cloud IPs are mapped |
*.public.srv-xxxxx.gb1.brightbox.com |
|
Wildcard alias for public.srv-xxxxx.gb1.brightbox.com
|
cip-xxxxx.gb1.brightbox.com |
|
IPv4 and IPv6 address of the Cloud IP with the identifier cip-xxxxx
|
ipv4.cip-xxxxx.gb1.brightbox.com |
|
IPv4 address of the Cloud IP with the identifier cip-xxxxx
|
ipv6.cip-xxxxx.gb1.brightbox.com |
|
IPv6 address of the Cloud IP with the identifier cip-xxxxx
|
*.cip-xxxxx.gb1.brightbox.com |
|
Wildcard alias for cip-xxxxx.gb1.brightbox.com
|
dbs-xxxxx.gb1.brightbox.com |
|
Private IPv4 address of the Cloud SQL instance with the identifier dbs-xxxxx
|
grp-xxxxx.gb1.brightbox.com |
|
IPv6 and private IPv4 addresses of all servers in the server group with the identifier |
ipv4.grp-xxxxx.gb1.brightbox.com |
|
Private IPv4 addresses of all servers in the server group with the identifier |
ipv6.grp-xxxxx.gb1.brightbox.com |
|
IPv6 addresses of all servers in the server group with the identifier |
public.grp-xxxxx.gb1.brightbox.com |
|
IPv6 and any mapped Cloud IPv4 addresses of all servers in the server group with the identifier |
Reverse DNS
Private Reverse DNS
Reverse DNS for private addresses works from within the Brightbox cloud network:
$ host 10.240.119.222
222.119.240.10.in-addr.arpa domain name pointer srv-su22m.gb1.brightbox.com.Cloud IP Reverse DNS
Reverse DNS for Cloud IPs defaults to the form
cip-109-107-38-125.gb1.brightbox.com. for both the IPv4 and IPv6 address.
You can customise Cloud IP reverse DNS using the API. Any custom reverse DNS setting will apply to both IPv4 and IPv6 addresses. The forward DNS mapping must be in place first otherwise the reverse DNS update will be rejected.
Forward mappings for custom reverse DNS are checked once a day and the account owner is sent an email notification if the forward mapping is found to be invalid. If the forward mapping is left invalid for 3 consecutive days, the custom reverse DNS mapping is reset to the default form.
The CLI Reverse DNS guide will take you through setting up reverse DNS step by step.