Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
dotdyntld [2018-11-21T01:47:25Z]
fusl removed
— (current)
Line 1: Line 1:
-.dyn main page:  [[dot/​dyn]] ​ https://​wiki.opennic.org/​opennic/​dot/​dyn 
  
- 
-The link in the box on http://​be.libre (domain management) returns your current IP which is then set as the A-record for your *.dyn domain. 
- 
-.dyn does not support ​ RFC-2136 ​  but instead uses some URL-scheme: a single bash line will update the address: 
- 
-  python3 -c '​import urllib.request ; err=urllib.request.urlopen("​http://​api.opennicproject.org/​ddns/​web.dyn?​user=XXX&​auth=YYY"​).read().decode("​utf8"​)'​ 
-  
-with XXX replaced with user  YYY with the real secret 
- 
- 
- 
-Other features which RFC-2136 offers are impossible on a *.dyn domain. 
- 
- 
- 
-.dyn is controlled by the nameserver ​ **161.97.219.84** ​ called ​ **ns2.opennic.glue** ​ 
- 
- 
-So if you run a webserver like Apache on your local machine, the .dyn domain should be served without much fuss. 
- 
-Update your IP with copy + paste of the API link. This works essentially like a regular dynamic-address DNS-tool. 
-So save the link as a bookmark for manual surfing - or better - call the URL via **curl** automatically upon address change or using some other automated scheme. ​ 
- 
- 
-The A-record returns a 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host, but it is also used for DNSBLs, storing subnet masks in RFC 1101, etc.. 
- 
-http://​api.opennicproject.org/​ddns/​web.dyn?​user=SOMEuser&​auth=kjngrkj 
- 
-This is an API call available for the  *.dyn  Toplevel-domains such as    http://​web.dyn 
-reload the domain administration page at  http://​be.libre ​  to see the fresh entry. The A-record gets updated upon hitting button "​**UPDATE**"​ .      
- 
-"Load this URI to register your IP" - helpful if your address changes after every router reset.