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

brand changed

Browse Source
This commit is contained in:
govardhan
2025-07-04 09:34:25 +05:30
parent 1ee37aea8b
commit faadd4e38d
129 changed files with 1069 additions and 1068 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md
View File

@ -16,9 +16,9 @@ DNS as a Service (DNSaaS) provides functionality of managing configuration of us
| SSHFP | SSH Public Key Fingerprint |
| TXT | Text record |
DNS configuration management is available via OpenStack web dashboard (Horizon), OpenStack command line interface as well as via the API.
DNS configuration management is available via 3Engines web dashboard (Horizon), 3Engines command line interface as well as via the API.
DNS records management is performed on the level of an OpenStack project.
DNS records management is performed on the level of an 3Engines 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.
@ -31,7 +31,7 @@ What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this
> * Adding new record for the domain
> * Adding records for subdomains
> * Managing records
> * Limitations in OpenStack DNSaaS
> * Limitations in 3Engines DNSaaS
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
@ -40,7 +40,7 @@ No. 1 **Account**
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://horizon.3Engines.com>.
No. 2 **Must have access to a project in 3Engines Cloud OpenStack account**
No. 2 **Must have access to a project in 3Engines Cloud 3Engines account**
If you are a tenant manager, you will be able to either use the existing basic project or create new projects for yourself or your users.
@ -53,7 +53,7 @@ We assume you already have a
> * basic knowledge of Domain Name Service principles as well as
> * understanding of the purpose of DNS records.
If not, please see [DNS article on Wikipedia](https://en.wikipedia.org/wiki/Domain_Name_System) or [OpenStack DNSaaS command line reference](https://docs.openstack.org/python-designateclient/latest/user/shell-v2.html.md)
If not, please see [DNS article on Wikipedia](https://en.wikipedia.org/wiki/Domain_Name_System) or [3Engines DNSaaS command line reference](https://docs.3Engines.org/python-designateclient/latest/user/shell-v2.html.md)
No. 4 **Must have domain purchased from a registrar**
@ -107,7 +107,7 @@ Step 2 Zone configuration[🔗](#step-2-zone-configuration "Permalink to this he
Zone configuration is defining parameters for the main domain name you have purchased.
To manage domain *exampledomain.com* in OpenStack, login to OpenStack dashboard, choose the right project if different than default, go to **Project** → **DNS** → **Zones**, click **Create Zone** and fill in the required fields:
To manage domain *exampledomain.com* in 3Engines, login to 3Engines dashboard, choose the right project if different than default, go to **Project** → **DNS** → **Zones**, click **Create Zone** and fill in the required fields:
![dns1.png](../_images/dns1.png)
@ -117,9 +117,9 @@ Here is what the parameters mean:
> * **Description**: free text description
> * **Email Address**: an administrative e-mail address associated with the domain
> * **TTL**: *Time To Live* in seconds - a period of time between refreshing cache in DNS servers. Please note that the longer time, the faster will be name recognition for your domain by external DNS servers but also if you introduce changes, they will propagate slower. The default value of 3600 seconds is a reasonable compromise.
> * **Type**: You may choose if OpenStack name servers will be primary or secondary for your domain. Default: Primary. In case you want to setup secondary name servers, you just define IP addresses or master DNS servers for the domain.
> * **Type**: You may choose if 3Engines name servers will be primary or secondary for your domain. Default: Primary. In case you want to setup secondary name servers, you just define IP addresses or master DNS servers for the domain.
After submitting, your domain should be served by OpenStack.
After submitting, your domain should be served by 3Engines.
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")
-------------------------------------------------------------------------------------------------------------------------------------------------------
@ -228,7 +228,7 @@ www.exampledomain.com. 3600 IN A 64.225.133.254
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:
Anytime you want to review, edit or delete records in your domain, visit 3Engines dashboard, **Project** → **DNS** → **Zones**. After clicking the domain name of your interest, choose **Record Sets** tab and see the list of all records:
![show_example_domain_record_sets.png](../_images/show_example_domain_record_sets.png)
@ -237,18 +237,18 @@ From this screen you can update or delete records.
Limitations[🔗](#limitations "Permalink to this headline")
---------------------------------------------------------
There are the following limitations in OpenStack DNSaaS:
There are the following limitations in 3Engines DNSaaS:
> * You cannot manage NS records for your domain. Therefore
>
> > + you cannot add additional secondary name servers
> > + 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 3Engines Cloud IP pools are managed on DNS servers other than OpenStack DNSaaS.
> * Even though you are able to configure reverse DNS for your domain, this configuration will have no effect since reverse DNS for 3Engines Cloud IP pools are managed on DNS servers other than 3Engines DNSaaS.
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:
Once an 3Engines 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:
You already have an existing VM
: Follow the procedure in article [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md) to assign a new floating IP to it.