DNS-O-Matic

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

Re: DNS-O-Matic

Post by nightcustard »

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!
Top
billion_fan
Posts: 5417
Joined: Tue Jul 19, 2011 4:30 pm

Re: DNS-O-Matic

Post by billion_fan »

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
Top
billion_fan
Posts: 5417
Joined: Tue Jul 19, 2011 4:30 pm

Re: DNS-O-Matic

Post by billion_fan »

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
Top
nightcustard
Posts: 68
Joined: Sat Nov 03, 2012 2:50 pm

Re: DNS-O-Matic

Post by nightcustard »

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 ;)
Top
nightcustard
Posts: 68
Joined: Sat Nov 03, 2012 2:50 pm

Re: DNS-O-Matic

Post by nightcustard »

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
Top
ittroll
Posts: 22
Joined: Sun Jun 09, 2019 9:30 am

Re: DNS-O-Matic

Post by ittroll »

This is failing again for me.

Code: Select all

May 29 15:27:08 user info syslog: ddnsd: all.dnsomatic.com (ptm0.2) IP has changed from (null) to xxx.xxx.xxx.xxx
May 29 15:27:08 user info syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.
I tried to download Zcomax8900AX2400_2.52.d51t2 listed above but it says it is an illegal image. I hunted around the forum and found Zcomax8900AX-R2_2.52.d8 and Zcomax8900AX-R2_2.52.d10 in various posts. d10 seems to be the latest but still has the same issue.

If I try an update with the same settings via a web browser it is successful.
https://updates.dnsomatic.com/nic/updat ... ckmx=NOCHG

I suspect something like a deprecated protocol/cypher.
Top
ittroll
Posts: 22
Joined: Sun Jun 09, 2019 9:30 am

Re: DNS-O-Matic

Post by ittroll »

billion_fan wrote: ↑Mon Oct 18, 2021 11:32 am Try the attached firmware link (hopefully this should resolve the issue)
Are you able to help with this issue before the forum closes/melts down?
Is 2.52d10 the latest firmware available and does that include the fix for DNS-O-Matic?
Top
billion_fan
Posts: 5417
Joined: Tue Jul 19, 2011 4:30 pm

Re: DNS-O-Matic

Post by billion_fan »

ittroll wrote: ↑Tue Jun 10, 2025 10:38 pm
billion_fan wrote: ↑Mon Oct 18, 2021 11:32 am Try the attached firmware link (hopefully this should resolve the issue)
Are you able to help with this issue before the forum closes/melts down?
Is 2.52d10 the latest firmware available and does that include the fix for DNS-O-Matic?
2.52.d10 for the 8900AX-1600R2 is the last firmware release

Unfortunately the 7800/8800/8900 series is now discontinued, including software updates.
Top
ittroll
Posts: 22
Joined: Sun Jun 09, 2019 9:30 am

Re: DNS-O-Matic

Post by ittroll »

OK, thanks for the reply and your support over the years.
Top
Post Reply

Return to “BiPAC 8900 series”