You bought a domain name from a company (which is called a domain name registrar or shortly a registrar). You created a website in Plesk and filled it with content. Now you want to bring your website online. In other words: connect your domain name with your website running on Plesk. This topic will explain to you how to do so.

Getting your website up and running comes down to choosing your DNS configuration and then configuring DNS. Both tasks may seem intimidating at first. We will help you by describing configuration types and step-by-step procedures of configuring DNS.

You can choose from the following DNS configurations:

  • (Recommended) Using Plesk as the primary DNS Server.

    If you go with this configuration, Plesk will create and manage your website DNS records automatically.

    We will show you how to switch from the DNS services of the following registrars to Plesk:

  • Using the DNS service offered by your domain registrar.

    You will need to create and manage your website DNS records manually on the DNS service portal of your domain registrar. We will show you how to put your website online and configure mail with the most popular registrars:

  • Using a third-party DNS service synced with Plesk, namely:

Using Plesk as the Primary DNS Server

To put your website online, you can use Plesk as the primary DNS service.

This DNS configuration is easy to set up. After you do so, Plesk will manage your website DNS records automatically.

The general procedure of setting up Plesk as the primary DNS server looks as follows:

  1. Log in to the DNS service portal of your domain registrar.

  2. Add the glue records for the nameservers. The glue records have the following pattern:

    ns1.<domain_name>   <the Plesk server IP address>
    ns2.<domain_name>   <the Plesk server IP address>
    

    For example:

    ns1.example.com   192.0.2.1
    ns2.example.com   192.0.2.1
    
  3. Change the nameservers of the domain registrar to those you added during the previous step (ns1.<domain_name> and ns2.<domain_name>).

We will now show you the exact procedures for the most popular top registrars.

Hover (Enom)

  1. Log in to Plesk.

  2. Go to Websites & Domains > your domain > the “Hosting & DNS” tab > DNS Settings.

  3. Locate two glue records. They have the following pattern:

    ns1.<domain_name>   <the Plesk server IP address>
    ns2.<domain_name>   <the Plesk server IP address>
    

    Copy the NS records’ hostnames (ns1.<domain_name> and ns2.<domain_name>) and the server IP address. You will need them later.

    image plesk ns records

  4. Log in to Hover.

  5. Make sure you are on the page of the domain for which you want to configure DNS hosting in Plesk.

  6. Go to the “Advanced” tab and then click ADD A GLUE RECORD.

    image hover plesk 1

  7. Add the first glue record. To do so, specify ns1.<domain_name>, your Plesk IP address, and then click ADD RECORD.

    image hover plesk 2

  8. Add the second glue record. To do so, repeat the previous step but specify ns2.<domain_name>.

  9. Go to the “Overview” tab, scroll down to the “NAMESERVERS” section on the left, and then click EDIT next to it.

    image hover plesk 3

  10. Delete three nameservers and keep only the first two. As “NAMESERVER 1” and “NAMESERVER 2”, specify the nameservers you have created earlier (ns1.<domain_name> and ns2.<domain_name>), and then click SAVE NAMESERVERS.

    image hover plesk 4

You have finished configuring Plesk as the primary DNS server. Your website will be up and running once changes come into effect. Propagation can take up to 24 hours.

GoDaddy

  1. Log in to Plesk.

  2. Go to Websites & Domains > your domain > the “Hosting & DNS” tab > DNS Settings.

  3. Locate two glue records. They have the following pattern:

    ns1.<domain_name>   <the Plesk server IP address>
    ns2.<domain_name>   <the Plesk server IP address>
    

    Copy the NS records’ hostnames (ns1.<domain_name> and ns2.<domain_name>) and the server IP address. You will need them later.

    image plesk ns records

  4. Log in to GoDaddy Domain Manager.

  5. Click the domain name, scroll down to the “Additional Settings” section, and then click “Manage DNS” on the right.

    image godaddy plesk 0

  6. Scroll down to the “Advanced Features” section, click “Host names”, and then click ADD.

    image godaddy plesk 1

  7. Add two glue records. To do so, specify ns1.<domain_name>, ns2.<domain_name>, your Plesk IP address, and then click Save.

    image godaddy plesk 2

  8. Next to “Nameservers”, click Change.

    image godaddy plesk 3

  9. Click “Enter my own nameservers (advanced)”.

    image godaddy plesk 4

  10. Specify the nameservers you have created earlier (ns1.<domain_name> and ns2.<domain_name>) and then click Save.

    image godaddy plesk 5

  11. Select “Yes, I consent to update Nameservers for the selected domain(s)” and click Continue.

    image godaddy plesk 6

You have finished configuring Plesk as the primary DNS server. Your website will be up and running once changes come into effect. Propagation can take up to 24 hours.

NameCheap

  1. Log in to Plesk.

  2. Go to Websites & Domains > your domain > the “Hosting & DNS” tab > DNS Settings.

  3. Locate two glue records. They have the following pattern:

    ns1.<domain_name>   <the Plesk server IP address>
    ns2.<domain_name>   <the Plesk server IP address>
    

    Copy the NS records’ hostnames (ns1.<domain_name> and ns2.<domain_name>) and the server IP address. You will need them later.

    image plesk ns records

  4. Log in to NameCheap.

  5. On the row corresponding to the domain, click MANAGE.

    image namecheap plesk 1

  6. Go to the “Advanced DNS” tab and scroll down to the “PERSONAL DNS SERVER” section.

    image namecheap plesk 2

  7. Add the first glue record. To do so, click ADD NAMESERVER. Under the “Nameserver” drop-down list, select ns1, specify the Plesk IP address, and then click DONE.

    image namecheap plesk 3

  8. Add the second glue record. To do so, repeat the previous step but select ns2.

    Note: The added glue records do not appear on the screen right away. To see them, in the “PERSONAL DNS SERVER” section, click SEARCH.

    image namecheap plesk 4

  9. Go to the “Domain” tab.

  10. In the “NAMESERVERS” section, select “Custom DNS”, specify the nameservers you have created earlier (ns1.<domain_name> and ns2.<domain_name>), and then click image namecheap icon to save changes.

    image namecheap plesk 5

You have finished configuring Plesk as the primary DNS server. Your website will be up and running once changes come into effect. Propagation can take up to 24 hours.

Network Solutions

  1. Log in to Plesk.

  2. Go to Websites & Domains > your domain > the “Hosting & DNS” tab > DNS Settings.

  3. Locate two glue records. They have the following pattern:

    ns1.<domain_name>   <the Plesk server IP address>
    ns2.<domain_name>   <the Plesk server IP address>
    

    Copy the NS records’ hostnames (ns1.<domain_name> and ns2.<domain_name>) and the server IP address. You will need them later.

    image plesk ns records

  4. Log in to Network Solutions.

  5. Click “My Domain Names”.

    image network solutions plesk 1

  6. Under your domain, scroll down to the “Advanced Tools” section and click its name to unfold the section.

    image network solutions plesk 2

  7. Next to “Nameservers (DNS)”, click “MANAGE”.

    image network solutions plesk 3

  8. Add two nameservers ns1.<domain_name> and ns2.<domain_name> and then click SAVE.

    image network solutions plesk 4

  9. At the bottom of the “Advanced Tools” section, click “Custom Nameservers”.

    image network solutions plesk 5

  10. Locate the two nameservers you have added earlier.

    image network solutions plesk 6

  11. Click the first nameserver (ns1.<domain_name>), specify the Plesk server IP address, click Go, and then click Save Changes.

    image network solutions plesk 7

  12. Repeat the previous step for the second nameserver ns2.<domain_name>.

You have finished configuring Plesk as the primary DNS server. Your website will be up and running once changes come into effect. Propagation can take up to 72 hours.

IONOS

  1. Log in to Plesk.

  2. Go to Websites & Domains > your domain > the “Hosting & DNS” tab > DNS Settings.

  3. Locate two glue records. They have the following pattern:

    ns1.<domain_name>   <the Plesk server IP address>
    ns2.<domain_name>   <the Plesk server IP address>
    

    Copy the NS records’ hostnames (ns1.<domain_name> and ns2.<domain_name>) and the server IP address. You will need them later.

    image plesk ns records

  4. Log in to IONOS.

  5. At the top, click MENU > Domains & SSL.

    image ionos plesk 1

  6. Next to your domain, click the image ionos 1 icon and then click Nameserver.

    image ionos plesk 2

  7. Click Use custom name servers.

    image ionos plesk 3

  8. Specify two nameservers (ns1.<domain_name> and ns2.<domain_name>), the Plesk IP address, and then click Save. The fields for IP addresses will appear once you specify the nameservers.

    image ionos plesk 4

You have finished configuring Plesk as the primary DNS server. Your website will be up and running once changes come into effect. Propagation can take up to 48 hours.

Using the DNS Service of Your Registrar

Usually registrars also offer DNS service. To put your website online, you can use the DNS service of your domain registrar to connect your domain name with your website running on Plesk. This DNS configuration has the following advantages:

  • It is easy to set up.
  • Many registrars provide DNS service for free for domains you bought from them.

Note: You can also use a DNS service provider different from your registrar (for example, you bought a domain from GoDaddy but you want to use the DNS service from Enom). In this case, you often need to pay for the DNS service. You usually find the prices in the terms and conditions of your DNS service provider.

Below you will find step-by-step procedures of putting your website online with the most popular top registrars. We will also describe how to configure DNS for mail if you want to use mail in Plesk.

Note: If our documentation does not cover your registrar, you can try to configure DNS automatically via the Domain Connect extension installed in Plesk by default.

To put your website online with Enom

  1. Log in to Enom.

  2. Go to Domains > My Domains.

    image enom 1

  3. Click your domain name.

    image enom 2

  4. Under “Manage Domain”, select “Host Records”.

    image enom 3

  5. Add the following A records:

    Host Name Record Type Address
    @ A (Address) <your server IP>
    www A (Address) <your server IP>
    A (Address) <your server IP>

    To do so, click new row (as many times as necessary), fill in the data, and then click Save.

    image enom 4

    The A records you have added have various hostnames and they do the following:

    • www points your domain with www (www.example.com) to your server IP address.
    • @ points your naked domain without www (just example.com) to your server IP address.
    • * points any subdomain (<anything>.example.com) to your server IP address.

    Depending on your purpose, you may not need all three A records. However, if you are not sure which A records you need, we recommend that you add all three.

    Note: If you want to use mail in Plesk, the A record with the * hostname is mandatory.

    After you add A records, you have finished configuring DNS. Your website will be up and running once changes come into effect. Propagation can take up to 48 hours.

    If you want to use mail in Plesk, proceed with the following steps. If you do not, your DNS configuration is finished.

  6. Click “Edit MX Records”.

    image enom 5

  7. Add the following MX record and then click Save:

    Host Name Address Pref
    @ <your server hostname>, for example, mail.example.com 10

    image enom 6

You have configured DNS for mail. You can now use mail in Plesk.

To put your website online with GoDaddy

  1. Log in to your GoDaddy Domain Control Center.

  2. Next to your domain name, click the image godaddy 1 icon and then click Manage DNS.

    image godaddy 2

  3. Add the following A records:

    Type Host Points to TTL
    A @ <your server IP> 1 Hour
    A www <your server IP> 1 Hour
    A
    <your server IP> 1 Hour

    To do so, click Add, select the “A” type, specify the data, and then click Save. Repeat this as many times as many A records you need to add.

    image godaddy 3

    The A records you have added have various hostnames and they do the following:

    • www points your domain with www (www.example.com) to your server IP address.
    • @ points your naked domain without www (just example.com) to your server IP address.
    • * points any subdomain (<anything>.example.com) to your server IP address.

    Depending on your purpose, you may not need all three A records. However, if you are not sure which A records you need, we recommend that you add all three.

    Note: If you want to use mail in Plesk, the A record with the * hostname is mandatory.

    After you add A records, you have finished configuring DNS. Your website will be up and running once changes come into effect. Propagation can take up to 48 hours.

    If you want to use mail in Plesk, proceed with the following steps. If you do not, your DNS configuration is finished.

  4. Add the following MX record and then click Save:

    Type Host Points to Priority TTL
    MX @ <your server hostname>, for example, mail.example.com 10 1 Hour

    image godaddy 4

You have configured DNS for mail. You can now use mail in Plesk.

To put your website online with NameCheap

  1. Log in to NameCheap.

  2. Go to Domain List in the left pane, locate your domain, and then click Manage next to it.

    image namecheap 1

  3. Go to the “Advanced DNS” tab.

    image namecheap 2

  4. Add the following A records:

    Type Host Value TTL
    A Record @ <your server IP> Automatic
    A Record www <your server IP> Automatic
    A Record
    <your server IP> Automatic

    To do so, in the “HOST RECORDS” section, click Add New Record, select “A Record”, and then specify the data.

    Repeat this as many times as many A records you need to add and then click Save All Changes.

    image namecheap 3

    The A records you have added have various hostnames and they do the following:

    • www points your domain with www (www.example.com) to your server IP address.
    • @ points your naked domain without www (just example.com) to your server IP address.
    • * points any subdomain (<anything>.example.com) to your server IP address.

    Depending on your purpose, you may not need all three A records. However, if you are not sure which A records you need, we recommend that you add all three.

    Note: If you want to use mail in Plesk, the A record with the * hostname is mandatory.

    After you add A records, you have finished configuring DNS. Your website will be up and running once changes come into effect. Propagation can take up to 48 hours.

    If you want to use mail in Plesk, proceed with the following steps. If you do not, your DNS configuration is finished.

  5. Scroll down to the “MAIL SETTINGS” section. In the dropdown list next to it, select “Custom MX”.

    image namecheap 4

  6. Add the following MX record and then click Save All Changes:

    Type Host Value Priority TTL
    MX Record @ <your server hostname>, for example, mail.example.com 10 Automatic

    image namecheap 5

You have configured DNS for mail. You can now use mail in Plesk.

To put your website online with Network Solutions

  1. Log in to Network Solutions.

  2. Click your profile name and then click Manage Account.

    image network solutions 1

  3. Under “My Domain Names”, click “Edit DNS”.

    image network solutions 2

  4. Click Change Where Domain Points.

    image network solutions 3

  5. Select “Advanced DNS” and then click Continue.

    image network solutions 4

  6. In the “IP Address (A Records)” section, click Edit A Records.

  7. Add the following A records and then click Continue:

    Host   TTL Numeric IP
    @ <.your domain name> 7200 <your server IP>
    www <.your domain name> 7200 <your server IP>
    <.your domain name> 7200 <your server IP>
    mail <.your domain name> 7200 <your server IP>

    image network solutions 5

    The A records you have added have various hostnames and they do the following:

    • www points your domain with www (www.example.com) to your server IP address.
    • @ points your naked domain without www (just example.com) to your server IP address.
    • * points any subdomain (<anything>.example.com) to your server IP address.
    • mail points your mail.* subdomain (mail.example.com) to your server IP address.

    Depending on your purpose, you may not need all four A records. However, if you are not sure which A records you need, we recommend that you add all four.

    Note: If you want to use mail in Plesk, the A record with the mail hostname is mandatory.

  8. Click Save Changes and then click “Return to Advanced DNS Summary”.

    image network solutions 6

    You have finished configuring DNS. Your website will be up and running once changes come into effect. Propagation can take up to 48 hours.

    If you want to use mail in Plesk, proceed with the following steps. If you do not, your DNS configuration is finished.

  9. Scroll down to the “Mail Servers (MX Records)” section and click Edit MX Records next to it.

  10. Add the following MX record and then click Save:

    Sub-Domain (Optional)   Priority TTL Mail Server
      <.your domain name> 10 7200 <your server hostname>, for example, mail.example.com
  11. Click Save Changes and then click “Return to Advanced DNS Summary”.

You have configured DNS for mail. You can now use mail in Plesk.

To put your website online with IONOS

  1. Log in to IONOS.

  2. In the “Domains” section of the Control Panel, next to your domain, click the image ionos 1 icon and then select “DNS”.

    image ionos 2

  3. Add the following A records:

    Type Host Name Points to TTL
    A @ <your server IP> 1 hour
    A www <your server IP> 1 hour
    A
    <your server IP> 1 hour

    To do so, click Add Record, select the A type, specify the data, and then click Save. Repeat this step as many times as many A records you need to add.

    image ionos 3

    Note: IONOS adds the A record with the www hostname automatically unless you select not to add it.

    The A records you have added have various hostnames and they do the following:

    • www points your domain with www (www.example.com) to your server IP address.
    • @ points your naked domain without www (just example.com) to your server IP address.
    • * points any subdomain (<anything>.example.com) to your server IP address.

    Depending on your purpose, you may not need all three A records. However, if you are not sure which A records you need, we recommend that you add all three.

    Note: If you want to use mail in Plesk, the A record with the * hostname is mandatory.

    You have finished configuring DNS. Your website will be up and running once changes come into effect. Propagation can take up to 48 hours.

    If you want to use mail in Plesk, proceed with the following steps. If you do not, your DNS configuration is finished.

  4. Add the following MX record:

    Type Host Name Points to Priority TTL
    MX @ <your server hostname>, for example, mail.example.com 10 1 Hour

    To do so, click Add Record, select the MX type, specify the data, and then click Save.

    image ionos 4

You have configured DNS for mail. You can now use mail in Plesk.

Using a Third-Party DNS Service Synced with Plesk

A number of DNS services can integrate with Plesk, for example, DigitalOcean DNS, Amazon Route 53, Azure DNS, and so on. You can use them to put your website online, which has the following advantages:

  • The DNS records are stored in the DNS service but you can manage them directly in Plesk. DNS zones will be automatically synced between Plesk and the DNS service.
  • No need to set up and maintain a slave DNS server. The DNS services mentioned above offer DNS hosting with three or more different nameservers. This will reduce your Plesk server load and improve DNS hosting reliability.

Amazon Route 53

Watch the video tutorial

Amazon Route 53 is a paid DNS service, which offers four nameservers.

You can set up DNS hosting before or after adding domains to Plesk. Either way, both new and existing domains will be automatically synced with the DNS service.

To put your website online with Amazon Route 53:

  1. Log in to your Amazon root user or IAM user account.
  2. Save the access key ID and the secret access key of your account. If you use the IAM user account, make sure to grant the route53:* and route53domains:* permissions to the account.
  3. Log in to Plesk.
  4. Make sure that the DigitalOcean DNS, Slave DNS Manager, and Microsoft Azure DNS extensions are not installed. If they are, remove them to avoid conflict with Amazon Route 53.
  5. Go to Extensions, look for the Amazon Route 53 extension, and then click Get it free to install it.
  6. Next to the installed extension, click Open.
  7. Select the key type that you use: root account or IAM user account.
  8. Paste the access key ID and the secret access key that you got during step 2.
  9. Select the “Manage NS and SOA records” and the “Turn on Amazon Web Service Route 53” checkboxes and then click Log in.
  10. Go to your registrar’s dashboard and change the registrar’s nameservers to those of Amazon Route 53. Find out your Amazon Route 53 nameservers.

You have finished configuring DNS. Your website will be up and running once changes come into effect. They are rolled out gradually: more and more visitors will have access to your website with time. Propagation can take up to 48 hours.

DigitalOcean DNS

Watch the video tutorial

DigitalOcean DNS is a free DNS service, which offers three nameservers.

Note: You cannot create a domain in Plesk if its name matches the name of a website that is already hosted in DigitalOcean DNS.

To put your website online with DigitalOcean DNS:

  1. Log in to Plesk.

  2. Make sure that the DigitalOcean DNS extension is installed. In Plesk on DigitalOcean, the extension is installed by default.

  3. Make sure that the Amazon Route 53, Slave DNS Manager, and Microsoft Azure DNS extensions are not installed. If they are, remove them to avoid conflict with DigitalOcean DNS.

  4. Go to Extensions > the “My Extensions” tab, and click Open under “DigitalOcean DNS”.

  5. Choose how to connect Plesk to your DigitalOcean account. You can do so in two ways:

    • “OAuth2 Authorization” is the easiest way if you have your personal DigitalOcean account and one Plesk server.

      image do 1

      Click “OAuth2 Authorization” and you will be redirected to the DigitalOcean login page. Sign in with your DigitalOcean account, choose your account (if you have more than one), and click Authorize application.

      image do 2

      Then click the link to confirm sending the DigitalOcean authorization data to your Plesk.

      image do 3

    • If you are a member of a corporate DigitalOcean DNS account, use “DigitalOcean API token”. It is also the preferred way if you have multiple Plesk servers. In this case, we recommend that you generate a separate DigitalOcean API token for each server.

      image do 4

      Click “DigitalOcean API token”, sign in with your DigitalOcean account in a new browser tab, generate a DigitalOcean API token, and then copy it. Return to the Plesk tab, paste the token, and then click Save.

      image do 5

    Now new and existing domains in Plesk will be automatically synced with DigitalOcean DNS. The “Active” status of the domains under the “DigitalOcean DNS Zone” column notifies that they are synced automatically.

    image do 6

    Note: Plesk does not sync the following domains with DigitalOcean DNS neither automatically nor manually:

    • That have the “Disabled (formely known as Suspended)” or “Suspended” status.
    • Whose DNS zone is disabled or is of the slave type.
  6. Contact your registrar (the one you bought your domain name from) and change the nameservers to DigitalOcean’s nameservers: ns1.digitalocean.com, ns2.digitalocean.com, and ns3.digitalocean.com. See instructions on how to do so for many popular registrars (GoDaddy, IONOS by 1&1, HostGator, and others).

You have finished configuring DNS. Your website will be up and running once changes come into effect. They are rolled out gradually: more and more visitors will have access to your website with time. Propagation can take up to 48 hours.

Note: You may want to have certain domains not synced with DigitalOcean DNS automatically. For example, important domains whose DNS records you want to manage yourself directly in DigitalOcean DNS. In this case, to prevent Plesk from overriding the domains’ DNS records in DigitalOcean DNS, deactivate automatic sync for these domains. To do so, select one or several domains and then click Deactivate. However, to put these websites online, you will need to create all the necessary DNS records in DigitalOcean DNS yourself.

Azure DNS

Azure DNS is a paid DNS service, which offers four nameservers.

Configuring Azure DNS is more difficult than configuring DNS of other third-party DNS services synced with Plesk.

To put your website online with Azure DNS:

Step 1 - Installing the Azure DNS extension

  1. Log in to Plesk.
  2. Make sure that the Azure DNS extension is installed. In Plesk on Microsoft Azure, the extension is installed by default.
  3. Make sure that the Amazon Route 53, Slave DNS Manager, and DigitalOcean DNS extensions are not installed. If they are, remove them to avoid conflict with Azure DNS.
  4. Go to Extensions > the “My Extensions” tab and click Open under “Azure DNS”.

Step 2 - Creating an Azure subscription (if you do not have one)

  1. Log in to the Azure dashboard using your account.

  2. To set up Azure DNS, you need to have an Azure subscription first. Go to Subscriptions and see if you have one.

    image azure 1

    If you have a subscription, go to Step 3 - Enabling “Microsoft.Network” resource provider. If you do not have one, start creating a subscription by clicking Add.

  3. On the “Pay-As-You-Go” card, click Select offer.

  4. Fill in your profile and payment information, choose a technical support plan (if you need one), select the agreement checkbox and then click Sign up.

You have created a subscription.

image azure 2

Step 3 - Enabling “Microsoft.Network” resource provider

  1. Click the subscription name and then click Resource providers.

    image azure 3

  2. Find the “Microsoft.Network” resource provider in the list and make sure that it has the “Registered” status. If it does not, select “Microsoft.Network” and then click Register.

    image azure 4

When “Microsoft.Network” is shown as “Registered”, go to the next step.

Note: If you have any issues with registering “Microsoft.Network”, refer to this article.

Step 4 - Creating an application

  1. Click the hamburger menu button in the top left corner of the screen and then click Azure Active Directory.

    image azure 5

  2. Click App registrations and then click New registration.

    image azure 6

  3. Specify the application information:

    • A name, for example, “Plesk DNS”.
    • Keep the first option “Accounts in this organizational directory only” selected.
    • Under “Redirect URI (optional)”, keep “Web” selected.
  4. Return to the Plesk tab where the Azure DNS extension is opened and copy the link shown there.

    image azure 7

  5. Return to the Azure tab. Under “Redirect URI (optional)”, paste the link next to “Web”, and then click Register.

    image azure 8

  6. You have created an application. Copy “Application (client) ID” and “Directory (tenant ID)” and paste them into the corresponding fields on the Azure DNS extension page.

    image azure 9

Step 5 - Creating a secret

  1. In the left pane, click Certificates & Secrets and then click New client secret.

    image azure 10

  2. Give the secret a description and click Add.

    image azure 11

  3. Copy the secret value and paste it into the corresponding field on the Azure DNS extension page.

    Note: You will not see the secret value anymore after you leave this Azure page or perform another operation here.

    image azure 12

Step 6 - Creating a resource group

  1. Click the hamburger menu button in the top left corner of the screen, click Resource groups, and then click Create resource group (if you do not have any) or Add (if you have one).

    image azure 13

  2. Give the resource group a name, select your region, click Review + create, and then click Create.

    image azure 14

  3. Once the resource group is created, paste its name into the corresponding field on the Azure DNS extension page.

Step 7 - Adding a role assignment

  1. Click the name of the created resource group, click Access control (IAM), and then click Add > Add role assignment.

    image azure 15

  2. Specify the role assignment settings and then click Save:

    • Under “Role”, select “DNS zone contributor”.
    • Keep “Assign access to” empty.
    • Under “Select” type and select the name of the created application (“Plesk DNS” in our example).

    image azure 16

By now, you have configured everything necessary in the Azure portal and filled in the required fields on the Azure DNS extension page. Now it’s time to launch the integration.

Step 8 (final) - Integrating the Azure DNS extension with the Azure portal

  1. Return to the Plesk tab where the Azure DNS extension is opened and click Authorize.

    image azure 17

  2. Log in to your Microsoft account.

  3. Click Accept to grant the Azure DNS extension the permission to integrate with the Azure portal.

    image azure 18

  4. Select the subscription that you created (or had right from the start) and then click OK.

    image azure 19

  5. Select the domain that you want to put online and click Activate.

    image azure 20

  6. Wait a while until Azure DNS is activated.

    image azure 21

  7. Contact your registrar (the one you bought your domain name from) and change the nameservers to Azure nameservers. To see them, go to the Azure DNS extension page, select the domain name and then click Zone NS records.

Congratulations! You have finished configuring DNS. Your website will be up and running once changes come into effect. They are rolled out gradually: more and more visitors will have access to your website with time. Propagation can take up to 48 hours.