Manage DNS records for your domain
DNS records tell the internet where services for your domain are located. They can be used to connect your domain to a website, direct email to the correct mail server, and verify services or domains.
For domains hosted with PalmHost, DNS records are managed through the PalmHost Hosting Panel, rather than through the PalmHost Client Area.
Open DNS management
- Log in to your PalmHost Client Area.
- Open Services.
- Select Manage Service for your hosting service.
- Select Login to Control Panel.
- In the hosting panel, open Websites.
- Select Manage for the website or domain.
- Open DNS.
You can manage the DNS records associated with the domain from this area.
Common DNS records
The following are some of the DNS records you may encounter when managing a domain.
A record
An A record points a domain or hostname to an IPv4 address.
For example, an A record may be used to point your domain to the IPv4 address of the server hosting your website.
Do not replace an existing A record unless you know which service it is being used for. Changing it can cause the website or another service to stop resolving correctly.
CNAME record
A CNAME record points one hostname to another hostname rather than directly to an IP address.
CNAME records are commonly used for subdomains or services that provide a hostname for you to point to.
Check the instructions provided by the service you are connecting before changing or adding a CNAME record.
MX record
An MX record specifies which mail server should receive email for your domain.
If you use PalmHost email, the MX records must match the mail service configured for your domain. Do not change existing MX records simply because they look unfamiliar.
Changing MX records can affect where new email is delivered.
TXT record
A TXT record stores text information associated with a domain. Services commonly use TXT records for domain verification and email authentication.
When a service gives you a TXT record to add, copy the value carefully and add it to the correct domain or hostname.
SPF
SPF is an email authentication mechanism that uses a TXT record to specify which mail servers are authorised to send email for your domain.
If you use PalmHost email, use the SPF information supplied for your PalmHost email service. If you also send email through another legitimate service, the SPF configuration needs to account for that service as well.
A domain should not have multiple separate SPF policies. If you need to authorise more than one sending service, the authorised mechanisms should be combined into the appropriate SPF record.
DKIM
DKIM adds a digital signature to outgoing email so that receiving mail systems can verify that the message was authorised by the sending domain.
DKIM normally uses DNS records containing information supplied by the email service. If PalmHost provides DKIM information for your mailbox or domain, add the supplied record exactly as provided.
DMARC
DMARC builds on SPF and DKIM and allows a domain owner to publish instructions for how receiving mail systems should handle messages that do not pass the required authentication checks.
DMARC is configured through a DNS record. The correct policy depends on how your domain sends email and which services are authorised to send on its behalf.
Do not apply a strict DMARC policy without first confirming that your legitimate email-sending services are correctly configured. Otherwise, legitimate messages may be affected.
Before changing a DNS record
Before editing or deleting a record, make sure you know which service uses it.
- Check whether the record is related to your website.
- Check whether it is used for email delivery or authentication.
- Check whether another service uses it for verification.
- Keep a record of the existing value before making a change.
If you are unsure what a record does, it is safer to check before changing it.
DNS changes are not instant
After you change a DNS record, the new information does not necessarily become visible everywhere immediately.
DNS resolvers and other systems can temporarily cache DNS information according to the record's TTL (Time to Live). This means some users may continue to receive the previous DNS information while others receive the updated information.
How quickly a change is seen can therefore vary depending on the record, its previous TTL, and the DNS resolvers involved. A DNS change should not be considered failed simply because it is not visible immediately.
During a DNS change, avoid repeatedly changing the same record just because you cannot see the new result straight away. This can make troubleshooting more difficult.
DNS changes and PalmHost services
DNS management is separate from domain registration and from moving your website or email service.
For example, transferring a domain to PalmHost does not automatically mean that you should change all of its DNS records. If your website or email is still operating through another provider, changing DNS records without planning the move can interrupt those services.
If you are moving a website or email service to PalmHost, make the required DNS changes when the new service is ready and allow time for DNS caching and propagation.
If something stops working after a DNS change
First check the record you changed and confirm that the value matches the instructions for the service you are trying to connect.
Remember that DNS changes can take time to appear consistently because of caching and propagation.
If you need help with a PalmHost DNS configuration, contact PalmHost through Support in your Client Area. Include the domain name, the record you changed, and any relevant error message or service information.
Do not include passwords, API keys, authentication codes, or other confidential credentials in a support ticket.