Managing DNS Records Through Your 220 Internet Services Support Portal

Summary

This guide helps you troubleshoot and resolve: Managing DNS Records Through Your 220 Internet Services Support Portal. Follow the steps below to fix the issue.

Common Causes

Your Domain Name System (DNS) records act as a directory for your domain, directing web traffic to your server and email to your mail provider. Making changes to these records through the 220 Internet Services support portal allows you to manage your online presence without needing to contact technical support for every update. This guide covers the management of A, CNAME, MX, and TXT records while minimizing the risk of website downtime or email delivery failures.

Detailed Instructions

Accessing the DNS Management Page

1. Open your web browser and go to app.220.com.au.
2. Enter your credentials to log in to the support portal.
3. From the main dashboard, click on the Domains tab in the navigation menu.
4. Select Manage DNS from the dropdown options.
5. Locate your domain in the list and click Manage Records.

Adding or Editing an A Record

An A record maps your domain to an IPv4 address. Use this when pointing your website to a specific web server.

1. Click the Add Record button.
2. Select A from the Type dropdown menu.
3. Enter the hostname (e.g., www or @ for the root domain) in the Name field.
4. Enter the destination IP address in the Value field.
5. Set the TTL (Time to Live) to the recommended default or a lower value if you expect frequent changes.
6. Click Save Record.

Adding or Editing a CNAME Record

A CNAME (Canonical Name) record maps an alias name to a true domain name. This is commonly used for subdomains.

1. Click the Add Record button.
2. Select CNAME from the Type dropdown menu.
3. Enter the alias (e.g., blog or shop) in the Name field.
4. Enter the target domain name in the Value field.
5. Click Save Record.

Warning: Do not create a CNAME record for the root domain (@). Doing so can interfere with your MX records and cause email delivery failures.

Adding or Editing MX Records

MX (Mail Exchange) records direct email to the correct mail server. Incorrect MX records will result in bounced emails.

1. Click the Add Record button.
2. Select MX from the Type dropdown menu.
3. Leave the Name field as @ unless otherwise specified by your email provider.
4. Enter the mail server address provided by your email suite (e.g., Google Workspace or Microsoft 365) in the Value field.
5. Set the Priority value (lower numbers have higher priority).
6. Click Save Record.

Adding or Editing TXT Records

TXT records are used for verification and email authentication, such as SPF, DKIM, and DMARC, to prevent spoofing and improve deliverability.

1. Click the Add Record button.
2. Select TXT from the Type dropdown menu.
3. Enter the host (usually @) in the Name field.
4. Paste the full text string provided by your service provider into the Value field.
5. Click Save Record.

Troubleshooting

Diagnosing Propagation Delays

After saving changes, DNS records do not update instantly across the internet. This delay is known as propagation.

• Changes may take anywhere from a few minutes to 48 hours to reflect globally.
• Use an online DNS lookup tool to verify if your new records are visible in different regions.
• Lowering the TTL value before making changes can help speed up the propagation process.

Note: If you have just updated your records, clear your local DNS cache or try viewing your site in an incognito window to see if the changes have taken effect on your device.

Resolving Misconfigured Routing

If your website is offline or email is not arriving after a DNS change, check the following:

• Ensure there are no duplicate A records for the same hostname pointing to different IP addresses.
• Verify that MX records do not point to a CNAME; they must point to an A record or a hostname.
• Check for typos in the Value field, as a single misplaced character will break the record.

Preventing Email Disruption

When altering web settings (A records) while using an external email suite, ensure your MX records remain untouched. Changing the A record for @ will move your website but will not move your email unless the MX records are also updated. To avoid spoofing and deliverability failures, always maintain accurate SPF and DKIM TXT records.

Getting Further Assistance

If you are unable to resolve the issue or are unsure which records to update, you can Open a Ticket through the support portal for assistance from our Brisbane-based team.

Still Having Issues?