Dynamic DNS tutorial
|EGI-Engage project:||Main page||WP1(NA1)||WP3(JRA1)||WP5(SA1)||PMB||Deliverables and Milestones||Quality Plan||Risk Plan||Data Plan|
|WP2(NA2)||WP4(JRA2)||WP6(SA2)||AMB||Software and services||Metrics||Project Office||Procedures|
Dynamic DNS service provides unified, federation-wide 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.fedcloud.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 service 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.
A short presentation of the Dynamic DNS service is available here
How to use EGI FedCloud Dynamic DNS service
Using EGI FedCloud Dynamic DNS service is very simple and intuitive via GUI portal. Just go to https://nsupdate.fedcloud.eu and follow the menu in the portal. Concretely:
- Dynamic DNS service uses EGI CheckIn for authentication. If you have not EGI account yet, please register via https://sso.egi.eu/admin/
- Log into Dynamic DNS service portal using EGI account via menu "Login" and click on "egi" button
- Use "Overview" menu and click on "Add host" to register a new hostname in an available domain. Choose a hostname in an available domain and click on "Create"
- Follow the instruction after host creation for IP assignment/update. Note the host secret and the update URL (in form "https://HOSTNAME:SECRET@nsupdate.fedcloud.eu/nic/update") and save them for later use
- Run "curl https://HOSTNAME:SECRET@nsupdate.fedcloud.eu/nic/update" in your VM to assign the hostname to a running VM
- or add "curl https://HOSTNAME:SECRET@nsupdate.fedcloud.eu/nic/update" into cloud_init file to assign hostname automatically at start.
- You can edit/update/delete your registered hostnames in the "Overview" menu and click on the hostname
Please feel free to use and send your feedbacks/suggestions/comments to email@example.com
- For updating IP address, only hostname and its secret are needed. No user information is stored on VM in any form for updating IP.
- NS-update server uses HTTPS protocol, hostname/secret are encrypted as data and not visible during transfer so it is secure to use the update URL
- Hostnames/IP addresses are not expired so no need to refresh IP addresses if no changes, it is enough to run once. You can add the following command “curl https://HOSTNAME:SECRET@nsupdate.fedcloud.eu/nic/update” to cloud-init to assign hostname automatically at VM start
- If you get an error message when logging into NS-update server via EGI CheckIn, your browser may have expired token from EGI CheckIn. Try open this link https://aai-dev.egi.eu/oidc/saml/login in your browser to refresh the token or restart your browser
- DNS server set Time-to-Live (max time for caching DNS records) to 1 min for dynamic DNS, but MS Windows seems to not respect that. You can clear DNS cache in Windows with “ipconfig /flushdns” command with Administrator account
- NS-update portal does not store host secret in recoverable form. If you forget the secret of your hostname, simply generate new one via "Show configuration" button in the host edit page. The old secret will be invalid.
GET /nic/update?hostname=yourhostname&myip=ipaddress Host: nsupdate.fedcloud.eu Authorization: Basic base64-encoded-auth-string User-Agent:
base64-encoded-auth-string: base64 encoding of username:password username: your host name password: your host secret hostname in the parameter string can be omitted or must be the same as username myip in the parameter string if omitted, the IP address of the client in the GET request will be used
Using hostname/secret as username/password can significantly increase security as no user credential is needed for updating IP address for VMs