Search The Hostwinds Guides Knowledge Base

Cloud DNS Manager

Share This Article

Domain record management for your cloud services is made easy at Hostwinds by using our Cloud DNS Manager in the Cloud Portal.  Here you can add your domain to our DNS Manager and manage many of your DNS records without the need for going through your server itself if you so choose.

How Do I Access the Cloud DNS Manager?

In order to access and utilize the Cloud DNS Manager, you’ll want to ensure you are logged into your Hostwinds Client Area.

Step 1: From your Client Area, use the Cloud Control drop down to select the Cloud Portal.

The Cloud Portal link in the Client Area

Step 2: In the Cloud Portal, using the Network drop down to select the Domains option.

Hostwinds DNS Management

Here you will be able to see all of your available domains that have already been added to the Cloud DNS Manager, as well as the ability to add new domains to be managed by your Hostwinds account.

How Do I Manage My Domain Records?

Adding Domains

In order to add a domain, you only need to type the domain name in the text field and select Add Domain.

Adding a domain to the DNS Manager

It is important to note that in order to use the Domain Management with Hostwinds, you will want to set your domain to the Authoritative Nameservers that are provided after you add your domain so that you can use this feature.

Removing Domains

If you wish to remove any domains from the DNS Manager, you may do so by selecting the Actions drop down for the domain you wish to remove, and select Delete.

Removing a domain from the DNS Manager

Modifying DNS Records

To edit or modify any DNS records for domains that have been added to the DNS Manager, select the Actions drop down for the domain you wish to manager, and select Records.

Modifying domain records in the Cloud DNS Manager

From this screen, you have a number of records you may add or modify on the DNS manager:

A: Set an A record for your domain to map to the provided IPv4 Address.

Value format: <ipv4_address>
Example: 127.0.0.1

A Record

AAAA: Set an AAAA record for your domain to map to the provided IPv6 Address.

Value format: <ipv6_address>
Example: ::1

AAAA Record

MX: Set an MX (Mail Exchange) record to map the domain’s emails to the correct mail server.

Value format: <priority> <hostname>
Example: 0 example.com

MX Record

CNAME: Set a CNAME (Canonical Name) record to connect any aliases or other desired names to the true domain name.

Value format: <hostname>
Example: example.com

CNAME Record

SRV: Set a SRV (Service) record that specifies hostname and port number of servers for any services or software that require it.  An example is Session Initiation protocol (SIP).

Value format: <preference> <weight> <port> <hostname>
Example: 0 0 1234 example.com

SRV Record

SPF: Set a SPF (Sender Policy Framework) record for email validation that verifies the sender is not spoofed by a third-party.

Value format: v=spf1 <spf_option_one> [spf_option_two...]
Example: v=spf1 mx ~all

SPF Record

TXT: Set a TXT (Text) record for adding necessary TXT records, such as for remote eCommerce platforms or opportunistic encryption.

Value format: <txt_value> [txt_option_one...]
Example: variable=value

TXT Record

NS: Set a NS (Nameserver) record that determines which servers the domain will point to for data and information related to the domain name. 

Value format: <hostname>
Example: ns1.example.com

NS Record

PTR: Set a PTR record to report the domain that is associated to the IP.  Also called an rDNS (reverse DNS) record.

Value format: <hostname>
Example: example.com

DNSKEY: Set a DNSKEY that holds a public key that can be used to verify DNSSEC signatures. You need to specify the flags, protocol, and algorithm used for DNSSEC, along with your public key.

Value format: <flags> <protocol> <algorithm> <key>
Example: 257 3 13 publicKeyValue==

DNSKEY

DS: Set a DS (Delegation Signer) record which references a DNSKEY record for this domain.

Value format: <tag> <algorithm> <type> <digest>
Example: 12345 13 3 digestValue

DS Record

NAPTR: Set a NAPTR (Name Authority Pointer) record for mapping servers and addresses used in Session Initiation protocol or Internet telephony systems.

Value format: <flags> <services> <regex> <hostname>
Example: 100 10 "S" "SIP+D2U" "!^.!sip:sip@example.com!" _sip._tcp.example.com

SSHFP: Set a SSHFP (Secure Shell Fingerprint) record for public keys used with DNSSEC domains for the SSH.

Value format: <algorithm> <type> <fingerprint>
Example: 2 1 fingerprintValue

SSHFP Record

TLSA: Set a TLSA (Transport Layer Security Authentication) record for keys to be used with a domain’s TLS.

Value format: <certificate usage> <selector> <matching type> <certificate>
Example: 3 1 1 certificateValue==

TLSA Record

URI: Set a URI (Uniform Resource Identifier) record for publishing the mappings of hostnames to their URIs. Often used for FTP.

Value format: <priority> <weight> <url>
Example: 10 10 "ftp://ftp.example.com/"

URI Record

If your record requires a priority level, please include the priority in the text field in the order requested.  Here is an example of an MX record with the priority placed at the start:
0 example.com

Note: entries into the Cloud DNS manager must follow their respective value formats as listed above, with single spaces between the value components, and no leading or trailing whitespace.

Please note that after making any changes to DNS records, it can take up to 24 – 48 hours for those changes to be propagated and reflected over the internet.  If you would like to know more about DNS propagation, we have a handy article on What DNS Propagation is available for review at any time.

Related Articles: