Eu encontrei a resposta e me sinto muito bobo, não percebendo isso antes.
daemon=60 # check every 60 seconds
syslog=yes # log update msgs to syslog
mail=root # mail all msgs to root
mail-failure=root # mail failed update msgs to root
pid=/var/run/ddclient.pid # record PID in file.
ssl=yes # use ssl-support. Works with
# ssl-library
use=web, web=https://myip.dnsdynamic.org # get ip from server.
server=www.dnsdynamic.org # default server
login=USERNAME # default login
password=PASSWORD # default password
server=www.dnsdynamic.org, \
protocol=dyndns2 \
YOUR DOMAIN GOES HERE
O acima irá forçar o SSL e irá se conectar através de SSL. Existem duas alterações que fiz.
A linha use=web, web=myip.dnsdynamic.com
deve ser use=web, web=https://myip.dnsdynamic.org
. Alterar de .com
para .org
interrompe falhas de conexão. Adicionar https://
antes da cadeia de conexão permite que ela se conecte por SSL.
A saída de use=web, web=myip.dnsdynamic.org
mostra:
use=web, web=loopia address is IPADDRESSISHERE
CONNECT: myip.dnsdynamic.org
CONNECTED: using HTTP
SENDING: GET / HTTP/1.0
SENDING: Host: myip.dnsdynamic.org
SENDING: User-Agent: ddclient/3.8.2
SENDING: Connection: close
A saída de use=web, web=https://myip.dnsdynamic.org
mostra:
use=web, web=loopia address is IPADDRESSISHERE
CONNECT: myip.dnsdynamic.org
The verification of cert '/C=US/O=GeoTrust Inc./CN=RapidSSL SHA256 CA/CN=www.dnsdynamic.org'
failed against the host 'myip.dnsdynamic.org' with the default verification scheme.
THIS MIGHT BE A MAN-IN-THE-MIDDLE ATTACK !!!!
To stop this warning you might need to set SSL_verifycn_name to
the name of the host you expect in the certificate.
CONNECTED: using SSL
SENDING: GET / HTTP/1.0
SENDING: Host: myip.dnsdynamic.org
SENDING: User-Agent: ddclient/3.8.2
SENDING: Connection: close
Ainda não sei por que forçar ssl=yes
não faz com que ele use HTTPS automaticamente, mas está se conectando por SSL agora e o comando visto por @George me ajuda a verificar se: sudo ddclient -verbose -debug -noquiet -query