DNS-O-Matic

Discussions for BiPAC 8900 series: 8900AX-1600, 8900AX-2400, 8900X
nightcustard
Posts: 57
Joined: Sat Nov 03, 2012 2:50 pm

Re: DNS-O-Matic

Post by nightcustard » Fri Oct 15, 2021 9:35 pm

Hi again.

7 days later and unfortunately ddns has failed again...

Loaded 2.52.d51t1 firmware on October 8th at 16:46, ddns updated OK:
Oct 8 16:46:27 192.168.27.1 syslog: ddnsd: all.dnsomatic.com (ptm0.1) IP has changed from (null) to (redacted)
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 1: (protocol="HTTP/1.0", status=200 message="OK")
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "date: Fri, 08 Oct 2021 15:46:27 GMT"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "server: opendns"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "content-length: 16"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "content-type: text/html; charset=UTF-8"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-envoy-upstream-service-time: 195"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-xss-protection: 1; mode=block"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-ingress-point: lon"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "connection: close"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read ""
Oct 8 16:46:28 192.168.27.1 syslog: hdrs->status_code=200
Oct 8 16:46:28 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully


All was OK until today at 18:37:
Oct 15 18:37:09 192.168.27.1 syslog: ddnsd: all.dnsomatic.com (ptm0.1) IP has changed from (redacted) to (redacted)
Oct 15 18:37:09 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

Note the redacted IP addresses are identical.

Any further help gratefully received!

billion_fan
Posts: 5266
Joined: Tue Jul 19, 2011 4:30 pm

Re: DNS-O-Matic

Post by billion_fan » Mon Oct 18, 2021 9:34 am

nightcustard wrote:
Fri Oct 15, 2021 9:35 pm
Hi again.

7 days later and unfortunately ddns has failed again...

Loaded 2.52.d51t1 firmware on October 8th at 16:46, ddns updated OK:
Oct 8 16:46:27 192.168.27.1 syslog: ddnsd: all.dnsomatic.com (ptm0.1) IP has changed from (null) to (redacted)
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 1: (protocol="HTTP/1.0", status=200 message="OK")
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "date: Fri, 08 Oct 2021 15:46:27 GMT"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "server: opendns"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "content-length: 16"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "content-type: text/html; charset=UTF-8"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-envoy-upstream-service-time: 195"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-xss-protection: 1; mode=block"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-ingress-point: lon"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "connection: close"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read ""
Oct 8 16:46:28 192.168.27.1 syslog: hdrs->status_code=200
Oct 8 16:46:28 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully


All was OK until today at 18:37:
Oct 15 18:37:09 192.168.27.1 syslog: ddnsd: all.dnsomatic.com (ptm0.1) IP has changed from (redacted) to (redacted)
Oct 15 18:37:09 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

Note the redacted IP addresses are identical.

Any further help gratefully received!
I'll update our engineers and get back to you

billion_fan
Posts: 5266
Joined: Tue Jul 19, 2011 4:30 pm

Re: DNS-O-Matic

Post by billion_fan » Mon Oct 18, 2021 11:32 am

nightcustard wrote:
Fri Oct 15, 2021 9:35 pm
Hi again.

7 days later and unfortunately ddns has failed again...

Loaded 2.52.d51t1 firmware on October 8th at 16:46, ddns updated OK:
Oct 8 16:46:27 192.168.27.1 syslog: ddnsd: all.dnsomatic.com (ptm0.1) IP has changed from (null) to (redacted)
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 1: (protocol="HTTP/1.0", status=200 message="OK")
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "date: Fri, 08 Oct 2021 15:46:27 GMT"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "server: opendns"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "content-length: 16"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "content-type: text/html; charset=UTF-8"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-envoy-upstream-service-time: 195"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-xss-protection: 1; mode=block"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-ingress-point: lon"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "connection: close"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read ""
Oct 8 16:46:28 192.168.27.1 syslog: hdrs->status_code=200
Oct 8 16:46:28 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully


All was OK until today at 18:37:
Oct 15 18:37:09 192.168.27.1 syslog: ddnsd: all.dnsomatic.com (ptm0.1) IP has changed from (redacted) to (redacted)
Oct 15 18:37:09 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

Note the redacted IP addresses are identical.

Any further help gratefully received!
Try the attached firmware link (hopefully this should resolve the issue)

http://gofile.me/3XbRY/qfz5dY968

nightcustard
Posts: 57
Joined: Sat Nov 03, 2012 2:50 pm

Re: DNS-O-Matic

Post by nightcustard » Mon Oct 18, 2021 8:50 pm

billion_fan wrote:
Mon Oct 18, 2021 11:32 am
nightcustard wrote:
Fri Oct 15, 2021 9:35 pm
Hi again.

7 days later and unfortunately ddns has failed again...

Loaded 2.52.d51t1 firmware on October 8th at 16:46, ddns updated OK:
Oct 8 16:46:27 192.168.27.1 syslog: ddnsd: all.dnsomatic.com (ptm0.1) IP has changed from (null) to (redacted)
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 1: (protocol="HTTP/1.0", status=200 message="OK")
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "date: Fri, 08 Oct 2021 15:46:27 GMT"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "server: opendns"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "content-length: 16"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "content-type: text/html; charset=UTF-8"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-envoy-upstream-service-time: 195"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-xss-protection: 1; mode=block"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "x-ingress-point: lon"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read "connection: close"
Oct 8 16:46:28 192.168.27.1 syslog: proto_ParseResponse, step 2: read ""
Oct 8 16:46:28 192.168.27.1 syslog: hdrs->status_code=200
Oct 8 16:46:28 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully


All was OK until today at 18:37:
Oct 15 18:37:09 192.168.27.1 syslog: ddnsd: all.dnsomatic.com (ptm0.1) IP has changed from (redacted) to (redacted)
Oct 15 18:37:09 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

Note the redacted IP addresses are identical.

Any further help gratefully received!
Try the attached firmware link (hopefully this should resolve the issue)

http://gofile.me/3XbRY/qfz5dY968
Thanks BF - I'll report back in eight days ;)

nightcustard
Posts: 57
Joined: Sat Nov 03, 2012 2:50 pm

Re: DNS-O-Matic

Post by nightcustard » Wed Nov 03, 2021 7:34 pm

Glad to report firmware 2.52.d51t2 appears to have solved the problem - I'm still getting DNS-O-Matic updates after nine days :D

Many thanks!

Mike

Post Reply