admin/3engines_doc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

link icon replaced

Browse Source
This commit is contained in:
govardhan
2025-06-19 14:09:10 +05:30
parent 60adbde60c
commit 172f8e2b34
158 changed files with 996 additions and 996 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/cloud/DNS-as-a-Service-on-CloudFerro-Cloud-Hosting.html.md
View File

@ -1,4 +1,4 @@
DNS as a Service on CloudFerro Cloud Hosting[](#dns-as-a-service-on-brand-name-cloud-name-hosting "Permalink to this headline")
DNS as a Service on CloudFerro Cloud Hosting[🔗](#dns-as-a-service-on-brand-name-cloud-name-hosting "Permalink to this headline")
================================================================================================================================
DNS as a Service (DNSaaS) provides functionality of managing configuration of user’s domains. Managing configuration means that the user is capable of creating, updating and deleting the following DNS records:
@ -22,7 +22,7 @@ DNS records management is performed on the level of an OpenStack project.
Since DNSaaS purpose is to deal with external domain names, the internal name resolution (name resolution for private IP addresses within user’s projects) is not covered by this documentation.
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Domain delegation in registrar’s system
@ -33,7 +33,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
> * Managing records
> * Limitations in OpenStack DNSaaS
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**
@ -71,7 +71,7 @@ Or, you might connect from a Linux based computer to the cloud:
In both cases, the article will contain a section to connect floating IP to the newly created VM. The generated IP address will vary, but for the sake of concreteness we shall assume that it is **64.225.133.254**. You will enter that value later in this article, to create record set for the site or service you are making.
Step 1 Delegate domain to your registrar’s system[](#step-1-delegate-domain-to-your-registrar-s-system "Permalink to this headline")
Step 1 Delegate domain to your registrar’s system[🔗](#step-1-delegate-domain-to-your-registrar-s-system "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------------------
The configuration of domain name in your registrar’s system must point to the NS records of CloudFerro name servers. It can be achieved in two ways:
@ -102,7 +102,7 @@ Configure glue records for your domain, so that they point to the following IP a
| secondary name server | ns2.exampledomain.com | 91.212.141.102 |
| secondary name server | ns3.exampledomain.com | 91.212.141.86 |
Step 2 Zone configuration[](#step-2-zone-configuration "Permalink to this headline")
Step 2 Zone configuration[🔗](#step-2-zone-configuration "Permalink to this headline")
-------------------------------------------------------------------------------------
Zone configuration is defining parameters for the main domain name you have purchased.
@ -121,7 +121,7 @@ Here is what the parameters mean:
After submitting, your domain should be served by OpenStack.
Step 3 Checking the presence of the domain on the Internet[](#step-3-checking-the-presence-of-the-domain-on-the-internet "Permalink to this headline")
Step 3 Checking the presence of the domain on the Internet[🔗](#step-3-checking-the-presence-of-the-domain-on-the-internet "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------------------------------------
It usually takes from 24 up to 48 hours for the domain name to propagate through the Internet so it will **not** be available right away. Rarely, domain name starts resolving in matters of minutes and hours instead of days, so it pays to try the domain address in your browser an hour or two after configuring the zone for the domain.
@ -170,7 +170,7 @@ curl exampledomain.com
Specify **A** to see the propagation of the domain itself and specify **NS** to see the propagation of nameservers across the Internet.
Step 4 Adding new record for the domain[](#step-4-adding-new-record-for-the-domain "Permalink to this headline")
Step 4 Adding new record for the domain[🔗](#step-4-adding-new-record-for-the-domain "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------
To add a new record to the domain, click on **Create Record Set** next to the domain name and fill in the required fields. The most important entry is to connect the domain name to the IP address you have. To configure an address of web server in **exampledomain.com**, so that it is resolved to **64.225.133.254** which is a Floating IP address of your server, fill the form as follows:
@ -206,7 +206,7 @@ Note
Each time a name of domain or a server is added or edited, add dot ‘.’ at the end of the entry.
For example: **exampledomain.com.** or **mail.exampledomain.com.**.
Step 5 Adding records for subdomains[](#step-5-adding-records-for-subdomains "Permalink to this headline")
Step 5 Adding records for subdomains[🔗](#step-5-adding-records-for-subdomains "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------
Defining subdomains is similar except that, normally, the subdomain would propagate within minutes instead of days.
@ -225,7 +225,7 @@ www.exampledomain.com. 3600 IN A 64.225.133.254
```
Step 6 Managing records[](#step-6-managing-records "Permalink to this headline")
Step 6 Managing records[🔗](#step-6-managing-records "Permalink to this headline")
---------------------------------------------------------------------------------
Anytime you want to review, edit or delete records in your domain, visit OpenStack dashboard, **Project** → **DNS** → **Zones**. After clicking the domain name of your interest, choose **Record Sets** tab and see the list of all records:
@ -234,7 +234,7 @@ Anytime you want to review, edit or delete records in your domain, visit OpenSta
From this screen you can update or delete records.
Limitations[](#limitations "Permalink to this headline")
Limitations[🔗](#limitations "Permalink to this headline")
---------------------------------------------------------
There are the following limitations in OpenStack DNSaaS:
@ -245,7 +245,7 @@ There are the following limitations in OpenStack DNSaaS:
> > + you are unable to delegate subdomains to external servers
> * Even though you are able to configure reverse DNS for your domain, this configuration will have no effect since reverse DNS for CloudFerro Cloud IP pools are managed on DNS servers other than OpenStack DNSaaS.
What To Do Next[](#what-to-do-next "Permalink to this headline")
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
-----------------------------------------------------------------
Once an OpenStack object has floating IP address, you can use the DNS service to propagate a domain name and, thus, create a service or a site. There are several situations in which you can create a floating IP address: