diff --git a/docs/networking/dns/common-dns-configurations/1121-dns9.png b/docs/networking/dns/common-dns-configurations-classic-manager/1121-dns9.png similarity index 100% rename from docs/networking/dns/common-dns-configurations/1121-dns9.png rename to docs/networking/dns/common-dns-configurations-classic-manager/1121-dns9.png diff --git a/docs/networking/dns/common-dns-configurations/1125-dns13.png b/docs/networking/dns/common-dns-configurations-classic-manager/1125-dns13.png similarity index 100% rename from docs/networking/dns/common-dns-configurations/1125-dns13.png rename to docs/networking/dns/common-dns-configurations-classic-manager/1125-dns13.png diff --git a/docs/networking/dns/common-dns-configurations/1126-dns15.png b/docs/networking/dns/common-dns-configurations-classic-manager/1126-dns15.png similarity index 100% rename from docs/networking/dns/common-dns-configurations/1126-dns15.png rename to docs/networking/dns/common-dns-configurations-classic-manager/1126-dns15.png diff --git a/docs/networking/dns/common-dns-configurations/1127-dns16.png b/docs/networking/dns/common-dns-configurations-classic-manager/1127-dns16.png similarity index 100% rename from docs/networking/dns/common-dns-configurations/1127-dns16.png rename to docs/networking/dns/common-dns-configurations-classic-manager/1127-dns16.png diff --git a/docs/networking/dns/common-dns-configurations-classic-manager/common-dns-configurations-title-graphic.jpg b/docs/networking/dns/common-dns-configurations-classic-manager/common-dns-configurations-title-graphic.jpg new file mode 100644 index 00000000000..3cbfbfcd6a0 Binary files /dev/null and b/docs/networking/dns/common-dns-configurations-classic-manager/common-dns-configurations-title-graphic.jpg differ diff --git a/docs/networking/dns/common-dns-configurations-classic-manager/index.md b/docs/networking/dns/common-dns-configurations-classic-manager/index.md new file mode 100644 index 00000000000..1a2e4f11047 --- /dev/null +++ b/docs/networking/dns/common-dns-configurations-classic-manager/index.md @@ -0,0 +1,55 @@ +--- +author: + name: Linode + email: docs@linode.com +description: 'Configurations for common DNS records.' +og_description: 'This guide explains how to use the Linode DNS manager, to configure DNS records' +keywords: ["dns", "dnssec"] +license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' +aliases: ['dns-manager/','dns-guides/configuring-dns-with-the-linode-manager/'] +modified: 2019-01-28 +modified_by: + name: Linode +published: 2015-01-20 +title: Common DNS Configurations +hiddenguide: true +cloud_manager_link: 'networking/dns/common-dns-configurations/' +--- + +![Common DNS Configurations](common-dns-configurations-title-graphic.jpg "Common DNS Configurations") + +## Set Up a Domain + +The most common DNS configuration is a single domain name on a single Linode. For this, you'll need to add *SOA* and *NS records* for all of your name servers, and *A/AAAA* records for your domain names. Use the screenshot below as a guide. + +[![The SOA record is set to "ns1.linode.com". The NS records are set to "ns1.linode.com" through "ns5.linode.com", inclusive. The MX record is set to "mail.example.org". There are A records for [blank], which is the primary domain, and the "mail" and "www" subdomains. They are all set to the same IP.](1121-dns9.png)](1121-dns9.png) + + {{< note >}} +The DNS Manager can automatically add all of these records when you create a domain zone. For instructions, see [Adding Domain Zones](/docs/networking/dns/dns-manager#add-a-domain-zone) in the [DNS Manager](/docs/networking/dns/dns-manager) guide. +{{< /note >}} + +## Configure Subdomains + +To configure a subdomain, such as `staging.example.org`, create an A record with the subdomain's hostname. Point the record at the IP address of the server you want to host the subdomain: + +[![Create a new A record, following the instructions in the "Adding" section. Add the subdomain text to the "Hostname" field. For example, you could type "staging" - NOT "staging.example.org".](1125-dns13.png)](1125-dns13.png) + +## Host Multiple Domains on a Single Server + +To host multiple domain names on a single server, create a separate domain zone for each domain name as shown below. When creating the new domain zones, we recommend that you allow the DNS Manager to automatically [insert basic records](/docs/networking/dns/dns-manager#add-a-domain-zone). At a minimum, you'll need an A record for each domain name pointing to the server's IP address. + +[![This page shows the DNS Manager tab with three different domain zones listed.](1126-dns15.png)](1126-dns15.png) + +## Use One Domain on Multiple Servers + +If you have more than one server, but only one domain name, you can point A records with server-specific hostnames to all servers that need domain names. One machine will be the "front end" for the domain, by virtue of the first-level domain's A record pointing to it, but the domain can serve as a proxy for services provided by other machines if needed. For example, if you wanted to create a development environment on another server, you could create an A record for `staging.example.org` and point it at another Linode's IP address. + +## Route Email to Third-Party Mail Services + +To route email to a third-party email service, create MX records that associate your mail server (for example, `mail.example.org`) with a *hostname* provided by the third-party service. For instructions, see the website of your third-party email service. + +## Use Wildcard DNS Records + +A *wildcard* DNS record matches requests for non-existent domain names. For example, if you create an A record for `*.example.org`, and a user visits `nonexistantname.example.org`, that user will be redirected to `example.org`. An example wildcard DNS record is shown below. + +[![Create a new A record, following the instructions in the "Adding" section. Add a single asterisk (\*) in the "Hostname" field. Set your IP address in the "IP Address" field. Then click the "Save Changes" button.](1127-dns16.png)](1127-dns16.png) diff --git a/docs/networking/dns/common-dns-configurations/common-dns-add-an-a-record-menu.png b/docs/networking/dns/common-dns-configurations/common-dns-add-an-a-record-menu.png new file mode 100644 index 00000000000..855968291c4 Binary files /dev/null and b/docs/networking/dns/common-dns-configurations/common-dns-add-an-a-record-menu.png differ diff --git a/docs/networking/dns/common-dns-configurations/common-dns-add-an-a-record.png b/docs/networking/dns/common-dns-configurations/common-dns-add-an-a-record.png new file mode 100644 index 00000000000..4b743bbefdf Binary files /dev/null and b/docs/networking/dns/common-dns-configurations/common-dns-add-an-a-record.png differ diff --git a/docs/networking/dns/common-dns-configurations/common-dns-multiple-domains-one-server.png b/docs/networking/dns/common-dns-configurations/common-dns-multiple-domains-one-server.png new file mode 100644 index 00000000000..9a0d7579514 Binary files /dev/null and b/docs/networking/dns/common-dns-configurations/common-dns-multiple-domains-one-server.png differ diff --git a/docs/networking/dns/common-dns-configurations/common-dns-set-up-a-domain.png b/docs/networking/dns/common-dns-configurations/common-dns-set-up-a-domain.png new file mode 100644 index 00000000000..b9b9962c846 Binary files /dev/null and b/docs/networking/dns/common-dns-configurations/common-dns-set-up-a-domain.png differ diff --git a/docs/networking/dns/common-dns-configurations/common-dns-use-wildcard.png b/docs/networking/dns/common-dns-configurations/common-dns-use-wildcard.png new file mode 100644 index 00000000000..e925640bca0 Binary files /dev/null and b/docs/networking/dns/common-dns-configurations/common-dns-use-wildcard.png differ diff --git a/docs/networking/dns/common-dns-configurations/index.md b/docs/networking/dns/common-dns-configurations/index.md index c8d4bd03bda..18be22a4b13 100644 --- a/docs/networking/dns/common-dns-configurations/index.md +++ b/docs/networking/dns/common-dns-configurations/index.md @@ -3,15 +3,16 @@ author: name: Linode email: docs@linode.com description: 'Configurations for common DNS records.' -og_description: 'This guide explains how to use the Linode DNS manager, to configure DNS records' +og_description: 'This guide explains how to use the Linode Cloud Manger to configure DNS records' keywords: ["dns", "dnssec"] license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' aliases: ['dns-manager/','dns-guides/configuring-dns-with-the-linode-manager/'] -modified: 2019-01-28 +modified: 2019-03-14 modified_by: name: Linode published: 2015-01-20 title: Common DNS Configurations +classic_manager_link: 'networking/dns/common-dns-configurations-classic-manager/' --- ![Common DNS Configurations](common-dns-configurations-title-graphic.jpg "Common DNS Configurations") @@ -20,34 +21,46 @@ title: Common DNS Configurations The most common DNS configuration is a single domain name on a single Linode. For this, you'll need to add *SOA* and *NS records* for all of your name servers, and *A/AAAA* records for your domain names. Use the screenshot below as a guide. -[![The SOA record is set to "ns1.linode.com". The NS records are set to "ns1.linode.com" through "ns5.linode.com", inclusive. The MX record is set to "mail.example.org". There are A records for [blank], which is the primary domain, and the "mail" and "www" subdomains. They are all set to the same IP.](1121-dns9.png)](1121-dns9.png) +[![The SOA record is set to "example-site-demo.com". The NS records are set to "ns1.linode.com" through "ns5.linode.com", inclusive. The MX record is set to "mail.example-site-demo.com". There are A records for [blank], which is the primary domain, and the "mail" and "www" subdomains. They are all set to the same IP.](common-dns-set-up-a-domain.png)](common-dns-set-up-a-domain.png) {{< note >}} -The DNS Manager can automatically add all of these records when you create a domain zone. For instructions, see [Adding Domain Zones](/docs/networking/dns/dns-manager#add-a-domain-zone) in the [DNS Manager](/docs/networking/dns/dns-manager) guide. +The Domains section of the Cloud Manager can automatically add all of these records when you create a domain. For instructions, see the *Add a Domain* section of the [DNS Manager](/docs/networking/dns/dns-manager) guide. {{< /note >}} ## Configure Subdomains -To configure a subdomain, such as `staging.example.org`, create an A record with the subdomain's hostname. Point the record at the IP address of the server you want to host the subdomain: +1. To configure a subdomain (e.g. `staging.example-site-demo.com`), create an A record with the subdomain's hostname. Click **Add an A/AAA Record**: -[![Create a new A record, following the instructions in the "Adding" section. Add the subdomain text to the "Hostname" field. For example, you could type "staging" - NOT "staging.example.org".](1125-dns13.png)](1125-dns13.png) + [![Create a new A record by first click on "Add an A/AAA Record"](common-dns-add-an-a-record.png)](common-dns-add-an-a-record.png) + +1. Add the subdomain under the **Hostname** field. Assign the IP address of the server you want to host the subdomain: + + [![Create a new A record, following the instructions in the "Adding" section. Add the subdomain text to the "Hostname" field. For example, you could type "staging" - NOT "staging.example-site-demo.com".](common-dns-add-an-a-record-menu.png)](common-dns-add-an-a-record-menu.png) + +1. Click on the **Save** button to create the record. + + {{< disclosure-note "Multi-level Subdomains" >}} +The Linode Cloud Manager does not support adding a subdomain of a subdomain in the same domain zone. For example, if you have `example.com` as a domain with an A record for `staging.example.com`, you cannot create `test.staging.example.com` within that same domain zone. Instead, create a separate domain zone for the subdomain `staging.example.com`. Then, add an A record for `test.staging.example.com` to that new zone. + +See the [subdomains](/docs/platform/manager/dns-manager/#subdomains) section of the [DNS manager](/docs/platform/manager/dns-manager/#subdomains) guide for more information. + {{}} ## Host Multiple Domains on a Single Server -To host multiple domain names on a single server, create a separate domain zone for each domain name as shown below. When creating the new domain zones, we recommend that you allow the DNS Manager to automatically [insert basic records](/docs/networking/dns/dns-manager#add-a-domain-zone). At a minimum, you'll need an A record for each domain name pointing to the server's IP address. +To host multiple domain names on a single server, create a separate domain entry for each domain name as shown below. When creating the new domain entry, we recommend that you allow the Domains section of the Cloud Manager to automatically [insert basic records](/docs/networking/dns/dns-manager#add-a-domain-zone). At a minimum, you'll need an A record for each domain name pointing to the server's IP address. -[![This page shows the DNS Manager tab with three different domain zones listed.](1126-dns15.png)](1126-dns15.png) +[![This page shows the Domains page with three different domain zones listed.](common-dns-multiple-domains-one-server.png)](common-dns-multiple-domains-one-server.png) ## Use One Domain on Multiple Servers -If you have more than one server, but only one domain name, you can point A records with server-specific hostnames to all servers that need domain names. One machine will be the "front end" for the domain, by virtue of the first-level domain's A record pointing to it, but the domain can serve as a proxy for services provided by other machines if needed. For example, if you wanted to create a development environment on another server, you could create an A record for `staging.example.org` and point it at another Linode's IP address. +If you have more than one server, but only one domain name, you can point A records with server-specific hostnames to all servers that need domain names. One machine will be the "front end" for the domain, by virtue of the first-level domain's A record pointing to it, but the domain can serve as a proxy for services provided by other machines, if needed. For example, if you wanted to create a development environment on another server, you could create an A record for `staging.example.com` and point it at another Linode's IP address. ## Route Email to Third-Party Mail Services -To route email to a third-party email service, create MX records that associate your mail server (for example, `mail.example.org`) with a *hostname* provided by the third-party service. For instructions, see the website of your third-party email service. +To route email to a third-party email service, create MX records that associate your mail server (for example, `mail.example-site-demo.com`) with a *hostname* provided by the third-party service. For more detailed instructions, see the website of your third-party email service. ## Use Wildcard DNS Records -A *wildcard* DNS record matches requests for non-existent domain names. For example, if you create an A record for `*.example.org`, and a user visits `nonexistantname.example.org`, that user will be redirected to `example.org`. An example wildcard DNS record is shown below. +A *wildcard* DNS record matches requests for non-existent domain names. For example, if you create an A record for `*.example.com`, and a user visits `nonexistantname.example.com`, that user will be redirected to `example.com`. An example wildcard DNS record is shown below. -[![Create a new A record, following the instructions in the "Adding" section. Add a single asterisk (\*) in the "Hostname" field. Set your IP address in the "IP Address" field. Then click the "Save Changes" button.](1127-dns16.png)](1127-dns16.png) +[![Create a new A record, following the instructions in the "Adding" section. Add a single asterisk (\*) in the "Hostname" field. Set your IP address in the "IP Address" field. Then click the "Save Changes" button.](common-dns-use-wildcard.png)](common-dns-use-wildcard.png)