- What is CREODIAS?
- Computing & Cloud
- Data & Processing
- Pricing Plans
- Fight with COVID-19
- Examples of usage
- Satellite-based Urban Heat Island Mapping on CREODIAS
- Old but gold - historical EO data immediately available and widely used on CREODIAS
- CREODIAS for emergency fire management
- AgroTech project as an example of how CREODIAS can be used for food and environmental research
- Monitoring Air Quality of Germany in Pre vs During COVID Lockdown Period
- Common Agricultural Policy monitoring with Earth Observation
- Applications of CREODIAS data
- Meteorological data usage on the CREODIAS platform
- Building added value under Horizon Europe with CREODIAS
- CREODIAS: Introduction to SAR Sentinel-1 data
- Land subsidence and landslides monitoring based on satellite data
- Satellite imagery in support of the Common Agriculture Policy (CAP) and crop statistics
- Useful tools for data processing, available on CREODIAS platform
- CREODIAS for hydrological drought modelling
- CREODIAS for managing Urban Heat Islands
- CREODIAS for Digitising Green Spaces
- CREODIAS for Air Quality
- Advanced data processors on CREODIAS
- CREODIAS for your application
- Solutions for agriculture with CREODIAS
- Earth Observation data for Emergency response
- Security Applications with Satellite Data
- Climate Monitoring with Satellite Data
- Water Analysis on CREODIAS
- CREODIAS for land and agriculture monitoring
- Solutions for atmospheric analysis
- Example of tool usage
- Processing EO Data and Serving www services
- Processing and Storing EO
- Embedding OGC WMS Services into Your website
- GPU Use Case
- Using the EO Browser
- EO Data Finder API Manual
- Use of SNAP and QGIS on a CREODIAS Virtual Machine
- Use of WMS Configurator
- DNS as a Service - user documentation
- Use of Sinergise Sentinel Hub on the CREODIAS EO Data Hub
- Load Balancer as a Service
- Jupyter Hub
- Use of CREODIAS Finder for ordering data
- ESRI ArcGIS on CREODIAS
- Use of CEMS data through CREODIAS
- Searching, processing and analysis of Sentinel-5P data on CREODIAS
- ASAR data available on CREODIAS
- Public Reporting Dashboards
- Sentinel Hub Documentation
- Integration Guides
- OGC API
- Custom Processing Scripts
- Legal Matters
- Partner Services
- About Us
Your Processing Environment
DNS as a Service - user documentation
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:
|AAAA||IPv6 address record|
|CNAME||Canonical name record|
|MX||Mail exchange record|
|SPR||Sender Policy Framework|
|SSHFP||SSH Public Key Fingerprint|
DNS configuration management is available via OpenStack web dashboard (Horizon), OpenStack command line interface as well as via API.
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.
- We assume you already have a basic knowledge of Domain Name Service principles, understanding purpose of DNS records and of course have a project in one of CloudFerro cloud environments.
- You also must own a domain purchased from any registrar (domain reseller). Obtaining a domain from registrars is not covered by this article.
- If you want to use command line interface to manage domains configuration, you must be are able to authorize OpenStack CLI (see: How to install OpenStack client).
Domain delegation in registrar's system
The configuration of domain name in your registrar's system must point NS records to CloudFerro name servers. It can be achieved in two ways:
Option 1 - use CloudFerro name servers (recommended)
Configure NS records for your domain to the following CloudFerro name servers:
|primary name server||cf2-ns1.cloudferro.net||184.108.40.206|
|secondary name server||cf2-ns2.cloudferro.net||220.127.116.11|
|secondary name server||cf2-ns3.cloudferro.net||18.104.22.168|
You may check proper configuration of your
savit@eosav:~$ dig +noall +answer +additional -t ns exampledomain.com exampledomain.com. 3235 IN NS cf2-ns2.cloudferro.net. exampledomain.com. 3235 IN NS cf2-ns3.cloudferro.net. exampledomain.com. 3235 IN NS cf2-ns1.cloudferro.net. cf2-ns1.cloudferro.net. 2746 IN A 22.214.171.124 cf2-ns2.cloudferro.net. 78502 IN A 126.96.36.199 cf2-ns3.cloudferro.net. 78502 IN A 188.8.131.52
Option 2 - setup your own glue records (not recommended)
This configuration option may be not supported by some registrars.
Configure glue records for your domain, so that they point to the following IP addresses:
|primary name server||ns1.exampledomain.com||184.108.40.206|
|secondary name server||ns2.exampledomain.com||220.127.116.11|
|secondary name server||ns3.exampledomain.com||18.104.22.168|
savit@eosav:~$ dig +noall +answer +additional -t ns exampledomain.com exampledomain.com. 3235 IN NS ns1.exampledomain.com. exampledomain.com. 3235 IN NS ns2.exampledomain.com. exampledomain.com. 3235 IN NS ns3.exampledomain.com. ns1.exampledomain.com. 2746 IN A 22.214.171.124 ns2.exampledomain.com. 78502 IN A 126.96.36.199 ns3.exampledomain.com. 78502 IN A 188.8.131.52
In order 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 the required fields:
- Name: your domain name
- 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 serves. 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 od master DNS servers for the domain.
After submitting, your domain should be served by OpenStack.
Quick check with
savit@eosav:~$ dig -t any +noall +answer exampledomain.com @cf2-ns1.cloudferro.net exampledomain.com. 3600 IN SOA cf2-ns2.cloudferro.net. astellasawicki.cloudferro.com. 1554373787 3565 600 86400 3600 exampledomain.com. 3600 IN NS cf2-ns3.cloudferro.net. exampledomain.com. 3600 IN NS cf2-ns1.cloudferro.net. exampledomain.com. 3600 IN NS cf2-ns2.cloudferro.net.
To add a new record to domain, click Create Record Set next to domain name and fill the required fields. For example, to configure an address of web server in
exampledomain.com , so that
www.exampledomain.com is resolved to 184.108.40.206 which is a Floating IP address of your server, we should fill the form as follows:
- Type: Type of record (for example A, MX, etc.)
- Name: name of the record (for example www.exampledomain.com, mail.exampledomain.com, ...)
- Description: free text description
- TTL: Time To Live in seconds - a period of time between refreshing cache in DNS serves.
- Records: Desired record value (there may be more than one - one per line):
- for records of Type A put IP address
- for records of Type MX put name of a mail server which hosts e-mails for the domain
- for records of Type CNAME put original name which is to be aliased
Submit the form and check if your configuration works:
savit@eosav:~$ dig -t any +noall +answer www.exampledomain.com @cf2-ns1.cloudferro.net www.exampledomain.com. 3600 IN A 220.127.116.11
Each time a name of domain or a server is added or edited, please remember to add dot '.' at the end of the entry.
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:
From this screen you can update or delete records.
There are the following limitations in OpenStack DNSaaS:
- You cannot manage NS records for your domain therfore:
- 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 CloudFerro IP pools are managed on other DNS servers than OpenStack DNSaaS.
- DNS article on Wikipedia: https://en.wikipedia.org/wiki/Domain_Name_System
- OpenStack DNSaaS command line reference: https://docs.openstack.org/python-designateclient/latest/user/shell-v2.html