DNS zones

Create a DNS zone if you want a hostname pointed at Gozunga Cloud, not only a public IP.

A new server gets a public IPv4 on the Internet network. That is enough to SSH. Applications and users expect a name pointing at that address. Cloud → DNS is Gozunga's managed DNS: you create a zone for the domain, then add records. The service runs on redundant infrastructure with DNSSEC. Pricing starts at $0.50 per domain each month (see Network Services).

When you need this

• You launched a VM and want HTTPS on a real hostname.
• You are putting a load balancer in front of servers and want the name to follow that address.
• You want Gozunga to host the zone so records can change with the portal or the API, instead of only at the registrar.

If you already host DNS elsewhere, you can skip this page and create an A record there that points at the server's public IP. The IP is on the server Overview page. See Creating and Managing Virtual Machines.

Create a zone

This walkthrough creates gozungaexample.com. Use your own domain in the same fields.

Open Cloud → DNS. The page title is DNS Zones. Click + Create Zone. An empty project says There are no zones.

On the create form, enter the domain (gozungaexample.com), an Email for the zone owner (hostmaster@gozungaexample.com), and TTL in seconds (3600 is the usual default). Location and Description are optional. Domain name and Email are required. Click Add Domain.

Set nameservers at the registrar

The zone is not used on the internet until the registrar points the domain at Gozunga's nameservers. The zone Nameservers panel lists them. For gozungaexample.com they are:

• ns1.fsd1.gozunga.com
• ns2.fsd1.gozunga.com
• ns3.fsd1.gozunga.com

Copy those hostnames at the registrar. Until you do, lookups still use the old DNS.

Add records

Open the zone. The records table has Name, Type, Input, and TTL. Click Add in DNS.

An A record maps a hostname to an IPv4 address. In the portal, the apex can be @. This example points gozungaexample.com and www.gozungaexample.com at 103.229.152.236, the public IPv4 of a demo Ubuntu 26.04 server on the Internet network. The IP is on the server Overview page.

A CNAME aliases one name to another. app.gozungaexample.com can CNAME to www.gozungaexample.com. A CNAME cannot coexist with other records on the same name.

Same steps with the OpenStack CLI

Authenticate with application credentials from Cloud → Access. See API Authentication. You need python-openstackclient and python-designateclient.

openstack zone create --email hostmaster@gozungaexample.com gozungaexample.com.

openstack recordset create gozungaexample.com. --type A --record 103.229.152.236 gozungaexample.com.

openstack recordset create gozungaexample.com. --type A --record 103.229.152.236 www.gozungaexample.com.

openstack recordset create gozungaexample.com. --type CNAME --record www.gozungaexample.com. app.gozungaexample.com.

The working flag is --record (repeatable). The CLI does not accept @ as the record name; use the FQDN for the apex. Wait until the zone and recordsets are ACTIVE before you point production traffic at them.

Related: Infrastructure Networking, Load balancers.