Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Dynamic DNS"

From EGIWiki
Jump to navigation Jump to search
Line 29: Line 29:
= Used technologies =
= Used technologies =


BIND9 server with configuration for updating DNS names via RFC 2136
* BIND9 server with configuration for updating DNS names via RFC 2136
nsupdate.info software for registering and managing DNS names/domains
* nsupdate.info software for registering and managing DNS names/domains


= Current status =
= Current status =


A testing domain fedcloud.eu has been registered for testing and development (without touching production domains like egi.eu)
* A testing domain fedcloud.eu has been registered for testing and development (without touching production domains like egi.eu)
DNS servers are installed and configured for fedcloud.eu domain
* DNS servers are installed and configured for fedcloud.eu domain
Portal is installed on configured
* Portal is installed on configured
Users can register themselves and log in portal, can register DNS names within fedcloud.eu domain and assign to VMs
* Users can register themselves and log in portal, can register DNS names within fedcloud.eu domain and assign to VMs
Integrate to EGI CheckIn service
* Integrate to EGI CheckIn service


= Ongoing work =
= Ongoing work =


Clean up codes
* Clean up codes
Justify setting and user interface
* Justify setting and user interface
Defining policies
* Defining policies
Preparation for alpha/beta testing
* Preparation for alpha/beta testing


= Next steps =
= Next steps =


Support for command-line clients for registering domains
* Support for command-line clients for registering domains


= Long term work =
= Long term work =


Support for reverse DNS resolution
* Support for reverse DNS resolution

Revision as of 09:21, 28 February 2017

EGI-Engage project: Main page WP1(NA1) WP3(JRA1) WP5(SA1) PMB Deliverables and Milestones Quality Plan Risk Plan Data Plan
Roles and
responsibilities
WP2(NA2) WP4(JRA2) WP6(SA2) AMB Software and services Metrics Project Office Procedures



Objective

Supports for DNS names for VMs in EGI Federated cloud are recently required by many VOs. The aim of this task is to provide Dynamic DNS support for VMs in EGI Federated Clouds. Users can register their chosen meaningful and memorable DNS host names in given domains (e.g. my-server.vo-name.egi.eu) and assign to public IPs of their servers hosted in EGI Federated Cloud. By using Dynamic DNS, users can host services in EGI Federated Cloud with their meaningful server names, can freely move VMs from sites to sites without modifying server/client configurations (federated approach), can request valid server certificates in advance (critical for security)and many other advantages.


Participants

Viet Tran (IISAS) viet.tran _at_ savba.sk


Requirements

  • Basic functionalities
    • Web-based GUI interfaces for registering DNS hostnames for EGI users
    • DNS server with Dynamic DNS support for forward DNS resolution
    • Command-line clients for assigning registered hostnames to IPs
  • Advanced functionalities
    • Using EGI Checkin services
    • Command-line client for registering DNS names
  • Not compulsory but desired functionalities
    • Support for reverse DNS

Used technologies

  • BIND9 server with configuration for updating DNS names via RFC 2136
  • nsupdate.info software for registering and managing DNS names/domains

Current status

  • A testing domain fedcloud.eu has been registered for testing and development (without touching production domains like egi.eu)
  • DNS servers are installed and configured for fedcloud.eu domain
  • Portal is installed on configured
  • Users can register themselves and log in portal, can register DNS names within fedcloud.eu domain and assign to VMs
  • Integrate to EGI CheckIn service

Ongoing work

  • Clean up codes
  • Justify setting and user interface
  • Defining policies
  • Preparation for alpha/beta testing

Next steps

  • Support for command-line clients for registering domains

Long term work

  • Support for reverse DNS resolution