Set the service to the value in parenthesis. Currently, the script is setup to use Google Domains (google), DuckDNS (duckdns), DynDNS (dyndns), and NO-IP (noip).
KEMETIC DOCKER IP UPDATE
INTERVAL: How often the script should call the update services in minutes. UPDATEIPV6: If this is set to 1, then the script will detect the external IPv6 address of the service on which the container is running. IP: if DETECTIP is not set, you can specify an IP address. ĭETECTIP: If this is set to 1, then the script will detect the external IP of the service on which the container is running, such as the external IP of your DSL or cable modem. HOSTNAME: The host name that you are updating. PASSWORD: the password or token for the service. The envitonmental variables are as follows: To build the Docker image, simply run Docker buildĭocker run -it -rm -name no-ip1 -e USER=username -e PASSWORD=yourpassword -e SERVICE=duckdns -e HOSTNAME= -e DETECTIP=1 -e INTERVAL=1 blaize/docker-dynamic-dns I modified the script to accept environmental variables as input instead of passing them on the command line and also added two services for DynDNS and DuckDNS in addition to NO-IP. Having gotten in to Docker in recent years, I wanted to migrate my existing NO-IP script to a Docker.
So even if one is using a Dynamic DNS, traffic can still be secured using HTTPS. ) can be bound to a dynamic DNS name in a DNS record via a CNAME. One of the real advantages of Dynamic DNS nowadays is that HTTPS can now be bound to a domain name instead of an IP. DynDNS developed an HTTP-based protocol for updating DNS records on Dynamic DNS services that has been copied for a number of platforms. Traditional DNS services, however, relied on IP addresses staying the same.
Generally speaking, internet service providers (ISP's) will reassign an IP address to a subscriber after some period of time or if the user reconnects his or her connection. Dynamic DNS services have been around since the early days of the internet.
0 kommentar(er)
