Migrating From Other Providers to ManageEngine CloudDNS

Migrating From Other Providers to ManageEngine CloudDNS

Cloudflare

Generating Auth-Code:

  1. Login into your Cloudflare account and on dashboard click on user icon and select 'My Profile'.
  2. Navigate to 'API Tokens' and click on  'View' button of 'Global API Key'.
  3. Enter your password and complete the verification and the 'Auth-Code' will be displayed, copy the code.
  4. Once you copied the Auth-code from Cloudflare , Login into ME Cloud DNS and navigate to Configuration -> Migrations . Select Cloudflare and enter your Cloudflare's user email and the auth-code copied and the domain's name need to be migrated. Now Click
    Migrate.


Google Cloud DNS

Generating JSON Key

  1. Login into your google cloud account and Navigate to 'IAM & Admin' -> 'Service Accounts
  2. You need a service account to generate JSON Key .Click on 'CREATE SERVICE ACCOUNT'

  3. Enter the required details and create a service account
  4. On creating a service account, Navigate to 'API & Services' -> 'Credentials'
  5. Click on your service account and navigate to 'KEYS' tab. Now click on 'ADD KEY' and select 'Create New Key'. Select Key type as JSON and click Create. The JSON Key will be downloaded.
  6. Once you have Downloaded the JSON Key from Google Cloud , Login into ME Cloud DNS and navigate to Configuration -> Migrations . Select Google CloudDNS and enter the Zone Name (as in google) and DNS Zone Name (i.e FQDN) and paste the JSON key in Credentials and now click Migrate.


AWS Route 53

Generating Access Key, Key ID and Zone ID

  1. Login into your AWS account and click on 'user icon' and select 'Security Credentials'
  2. Now to generate Access Key and Key ID click on 'Create access key'
  3. Once Generated, Copy the Key ID and Access Key. But once you close the popup, you will not be able to retrieve that access key again.
  4. Now navigate to Route53 -> Hosted Zones page and copy the Zone ID for the domain to be migrated.


  5. Once you have the required credentials from AWS , log into ME Cloud DNS and navigate to Configuration -> Migrations . Select AWS Route53 and enter the Zone ID ,Key ID and Access Key  and now Click Migrate.

Azure

Getting required credentials

  1. Login into your Azure account and to get Subscription ID, click 'Subscription ID' and copy the 'Subscription ID' from the table.
  2. For Tenant ID, navigate to Microsoft Entra ID-> Overview previously known as 'Azure Active Directory' and copy the 'Tenent ID'







  3. To generate Client ID and Secret ,navigate to 'Azure Active Directory' -> 'App registrators' , If an app had been registered click on it or register a new application. Application (Client) ID in table is the Client ID required to migrate.





  4. Now for Client Secret, navigate to 'Certificates and secrets' and click on 'Client secrets' tab and click on 'New client secret'.






  5. Once secret is created, Copy the Key in 'Value' column which is the required Client Secret. Once you exit this screen in the Azure interface, you will not be able to retrieve that key again.





  6. Now you will have to configure the correct permissions on Azure App created. To do this navigate back to the "Home" page in your Azure account and click on "Subscriptions". Then select your subscription and navigate to 'IAM & Services'.


  7. Now click 'Add' and select 'Role Assignment'. select "Contributor" as role. Then type in the name of your "App" in the "Select" field and save.






  8. Once you have the required credentials from Azure, log into ME Cloud DNS and navigate to Configuration -> Migrations . Select Azure and enter the Domain Name, Resource group name (enter in lower case) ,Subscription ID, Tenent ID, Client Id  and Client Secret  and now click Migrate.






Reach out to support@meclouddns.com for any product-related queries.



                New to ADManager Plus?

                  New to ADSelfService Plus?

                    • Related Articles

                    • Zone Transfers in ManageEngine CloudDNS

                      Configuring ManageEngine CloudDNS as a primary DNS provider If your organization works with multiple DNS providers you can deploy CloudDNS as the primary provider, in parallel with other third-party primary or secondary DNS providers. Under this ...
                    • DNS monitoring in ManageEngine CloudDNS

                      DNS monitoring in ManageEngine CloudDNS DNS monitoring in CloudDNS is crucial to ensure the health and performance of your DNS infrastructure. By configuring DNS monitors in CloudDNS, you can keep a constant eye on your DNS servers and records. It is ...
                    • Zone Versioning in ManageEngine CloudDNS

                      Zone Versioning in ManageEngine CloudDNS With both Primary GeoDNS and Primary AXFR type of domains CloudDNS enables you store around ten previous versions of your mission- critical zone files. You can rollback to your previous configurations anytime ...
                    • Creating Filters in ManageEngine CloudDNS

                      Filters in ManageEngine CloudDNS Filters in CloudDNS are essential tools for optimizing and securing network traffic, ensuring users get the best possible experience, and providing businesses with the ability to enforce their operational policies ...
                    • DNS records setup in ManageEngine CloudDNS

                      How to create and update DNS records? What is a DNS record? The DNS records (also known as zone files or resource records) are the constituent files of a Zone or a Domain that carry the essential instructions that help the DNS resolver quickly ...