Open taem opened 5 years ago
Huh, weird ... just tested with FreeDNS + GnuTLS and that works. Sorry, no clue really what it could be, maybe some server/client crypto setting that's different?
inadyn[18430]: Sending IP# update to DDNS server, initiating HTTPS ...
inadyn[18430]: Sending IP# update to DDNS server, connecting to freedns.afraid.org([50.23.197.94]:443)
inadyn[18430]: Certificate OK
inadyn[18430]: SSL server cert subject: OU=Domain Control Validated,OU=EssentialSSL,CN=freedns.afraid.org
inadyn[18430]: SSL server cert issuer: C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA
inadyn[18430]: Fetching account API key, initiating HTTPS ...
inadyn[18430]: Fetching account API key, connecting to freedns.afraid.org([204.140.20.21]:443)
inadyn[18430]: Certificate OK
inadyn[18430]: SSL server cert subject: OU=Domain Control Validated,OU=EssentialSSL,CN=freedns.afraid.org
inadyn[18430]: SSL server cert issuer: C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA
inadyn[18430]: Successfully sent HTTPS request!
inadyn[18430]: Successfully received HTTPS response (294 bytes)!
inadyn[18430]: Received API key(s), rc=0:
troglobit.homenet.org|155.4.AAA.BBB|https://freedns.afraid.org/dynamic/update.php?foo=
inadyn[18430]: Sending alias table update to DDNS server: GET /dynamic/update.php?foo=&address=85.24.CCC.DDD HTTP/1.0
Host: freedns.afraid.org
User-Agent: inadyn/2.5 https://github.com/troglobit/inadyn/issues
inadyn[18430]: Successfully sent HTTPS request!
inadyn[18430]: Successfully received HTTPS response (384 bytes)!
inadyn[18430]: DDNS server response: HTTP/1.1 200 OK
Server: nginx
Date: Thu, 06 Jun 2019 08:47:51 GMT
Content-Type: text/plain; charset=utf-8
Connection: close
Vary: Accept-Encoding
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
Expires: Mon, 26 Jul 1997 05:00:00 GMT
X-Cache: MISS
Updated troglobit.homenet.org to 85.24.CCC.DDD in 0.037 seconds
inadyn[18430]: Successful alias table update for troglobit.homenet.org => new IP# 85.24.CCC.DDD
inadyn[18430]: Updating cache for troglobit.homenet.org
Ok, will continue debugging :)
Good luck man!
@taem Did you ever figure this one out? I fixed a couple of issues with the plugin back in July, found by Coverity Scan, in 687253e ... maybe that was the root cause?
So, v2.6 has been released https://github.com/troglobit/inadyn/releases/tag/v2.6, there are pre-built packages available, both Debian/Ubuntu packages and Docker images. Hopefully enough to help test this bug.
Hi Joachim,Ok, thanks. Need to try it.--Sent from Yandex.Mail for mobile22.02.2020, 23:11, "Joachim Nilsson" notifications@github.com:So, v2.6 has been released https://github.com/troglobit/inadyn/releases/tag/v2.6, there are pre-built packages available, both Debian/Ubuntu packages and Docker images. Hopefully enough to help test this bug.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
Hi Joachim,
Got GnuTLS issue with Yandex DNS.
Config:
Command:
$ ./src/inadyn --cache-dir=/tmp/inadyn --pidfile=/tmp/inadyn.pid -n -l debug
output:
Request to get DNS records is completed successfully, but request to update the record is not. OpenSSL version of the inadyn works as expected.
DNS record update using gnutls-cli works as expected also:
GnuTLS version:
I did some tcpdump session and it shows a lot of TCP retransmission packets. Any thoughts?
Thanks.