DNS-O-Matic

[pstonethompson]

I am having the same issue described at Three reboots in 24 hours with a BiPAC 8900AX2400 running firmware 2.52.d46. The last successful update received by DNS-O-Matic was on the second of March, with no changes to the router or credentials to have caused it. I am getting continuous failed update attempts in the logs. It appears that either this filling the logs or possibly some kind of memory leak (possibly with the HTTP client?) is causing the router to reboot a few times a day.

Re-entering the credentials did not make any difference, still constant failed updates.

I have for now removed the dynamic DNS service.

[billion_fan]

I am having the same issue described at Three reboots in 24 hours with a BiPAC 8900AX2400 running firmware 2.52.d46. The last successful update received by DNS-O-Matic was on the second of March, with no changes to the router or credentials to have caused it. I am getting continuous failed update attempts in the logs. It appears that either this filling the logs or possibly some kind of memory leak (possibly with the HTTP client?) is causing the router to reboot a few times a day.

Re-entering the credentials did not make any difference, still constant failed updates.

I have for now removed the dynamic DNS service.

I'll request the firmware fix for the 8900 series

[billion_fan]

I am having the same issue described at Three reboots in 24 hours with a BiPAC 8900AX2400 running firmware 2.52.d46. The last successful update received by DNS-O-Matic was on the second of March, with no changes to the router or credentials to have caused it. I am getting continuous failed update attempts in the logs. It appears that either this filling the logs or possibly some kind of memory leak (possibly with the HTTP client?) is causing the router to reboot a few times a day.

Re-entering the credentials did not make any difference, still constant failed updates.

I have for now removed the dynamic DNS service.

I'll request the firmware fix for the 8900 series

Attached are newer firmware versions for the Bipac 8900AX-2400 and Bipac 8900AX-1600R2 which resolves connectivity issues with DNS-O-Matic

[ittroll]

Attached are newer firmware versions for the Bipac 8900AX-2400 and Bipac 8900AX-1600R2 which resolves connectivity issues with DNS-O-Matic

I tried Zcomax8900AX-R2_2.52.d4_ddns2.afw on my 8900AX-1600R2 but I get failures.

Code: Select all

Mar 23 22:01:17 user info syslog: ddnsd: all.dnsomatic.com (ptm0.2) IP has changed from (null) to 12.34.56.78
Mar 23 22:01:17 user info syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

I rolled back to the previous Zcomax8900AX-R2_2.52.d4.afw release but that gives the same error.

As far as I can tell the update URL hasn't changed. I can successfully authenticate and update via a browser by using:

Code: Select all

https://updates.dnsomatic.com:443/nic/update?hostname=all.dnsomatic.com

I noticed the API docs talk about the importance of using a well-formed User-Agent string. Which of course a browser will do.
https://www.dnsomatic.com/docs/api

It would be more helpful if the syslog logged the full return code from the DNS-O-Matic API.

[billion_fan]

Attached are newer firmware versions for the Bipac 8900AX-2400 and Bipac 8900AX-1600R2 which resolves connectivity issues with DNS-O-Matic

I tried Zcomax8900AX-R2_2.52.d4_ddns2.afw on my 8900AX-1600R2 but I get failures.

Code: Select all

Mar 23 22:01:17 user info syslog: ddnsd: all.dnsomatic.com (ptm0.2) IP has changed from (null) to 12.34.56.78
Mar 23 22:01:17 user info syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

I rolled back to the previous Zcomax8900AX-R2_2.52.d4.afw release but that gives the same error.

As far as I can tell the update URL hasn't changed. I can successfully authenticate and update via a browser by using:

Code: Select all

https://updates.dnsomatic.com:443/nic/update?hostname=all.dnsomatic.com

I noticed the API docs talk about the importance of using a well-formed User-Agent string. Which of course a browser will do.
https://www.dnsomatic.com/docs/api

It would be more helpful if the syslog logged the full return code from the DNS-O-Matic API.

Newer firmware's have been added above

[ittroll]

Newer firmware's have been added above

Ah, I missed that these had been reposted. I think because you edited an old post and so no post notification was sent.

DNS updates are indeed working again on 8900AX-1600R2. Many thanks to you and the engineering team.

[nightcustard]

Hi BF - I'm running firmware 2.52.d50 on an 8900AXL2400 and have recently started using DNS-O-Matic to update my Dynamic DNS service provider (DuckDNS).

Checking the router log, I appear to be getting DNS-O-Matic update errors starting seven days after I restart the router.

I set DNS-O-Matic up for the first time on Sep 12 and it started updating successfully:

Log entry: Sep 12 06:58:10 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully.

Update errors started seven days later:

Sep 19 11:42:30 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

These persisted until September 22nd when I spotted the errors and restarted the router:

Sep 22 18:16:28 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully

Seven days later, on September 29th, I started getting update failures again:

Sep 29 20:19:43 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

These persisted until September 30th when I spotted the errors and again reset the router:

Sep 30 22:21:58 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully

I've checked my account with DNS-O-Matic, which appears to be functioning normally. The router's log unfortunately doesn't give any further details about the failures, so I'm a bit nonplussed about what's causing this odd behaviour.

The 'Dynamic DNS' setup page has the following settings:

Dynamic DNS Server: updates.dnsomatic.com
Host name: all.dnsomatic.com
Period: 10 minutes

Do you have any suggestions?

Cheers, Mike

[billion_fan]

Hi BF - I'm running firmware 2.52.d50 on an 8900AXL2400 and have recently started using DNS-O-Matic to update my Dynamic DNS service provider (DuckDNS).

Checking the router log, I appear to be getting DNS-O-Matic update errors starting seven days after I restart the router.

I set DNS-O-Matic up for the first time on Sep 12 and it started updating successfully:

Log entry: Sep 12 06:58:10 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully.

Update errors started seven days later:

Sep 19 11:42:30 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

These persisted until September 22nd when I spotted the errors and restarted the router:

Sep 22 18:16:28 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully

Seven days later, on September 29th, I started getting update failures again:

Sep 29 20:19:43 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

These persisted until September 30th when I spotted the errors and again reset the router:

Sep 30 22:21:58 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully

I've checked my account with DNS-O-Matic, which appears to be functioning normally. The router's log unfortunately doesn't give any further details about the failures, so I'm a bit nonplussed about what's causing this odd behaviour.

The 'Dynamic DNS' setup page has the following settings:

Dynamic DNS Server: updates.dnsomatic.com
Host name: all.dnsomatic.com
Period: 10 minutes

Do you have any suggestions?

Cheers, Mike

Let me check with our engineers and get back to you

[billion_fan]

Hi BF - I'm running firmware 2.52.d50 on an 8900AXL2400 and have recently started using DNS-O-Matic to update my Dynamic DNS service provider (DuckDNS).

Checking the router log, I appear to be getting DNS-O-Matic update errors starting seven days after I restart the router.

I set DNS-O-Matic up for the first time on Sep 12 and it started updating successfully:

Log entry: Sep 12 06:58:10 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully.

Update errors started seven days later:

Sep 19 11:42:30 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

These persisted until September 22nd when I spotted the errors and restarted the router:

Sep 22 18:16:28 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully

Seven days later, on September 29th, I started getting update failures again:

Sep 29 20:19:43 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

These persisted until September 30th when I spotted the errors and again reset the router:

Sep 30 22:21:58 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully

I've checked my account with DNS-O-Matic, which appears to be functioning normally. The router's log unfortunately doesn't give any further details about the failures, so I'm a bit nonplussed about what's causing this odd behaviour.

The 'Dynamic DNS' setup page has the following settings:

Dynamic DNS Server: updates.dnsomatic.com
Host name: all.dnsomatic.com
Period: 10 minutes

Do you have any suggestions?

Cheers, Mike

Attached is a link to firmware 2.52.d51t1, please let me know if this resolves the DNS-0-Matic update issue after 7 days,

[nightcustard]

Hi BF - I'm running firmware 2.52.d50 on an 8900AXL2400 and have recently started using DNS-O-Matic to update my Dynamic DNS service provider (DuckDNS).

Checking the router log, I appear to be getting DNS-O-Matic update errors starting seven days after I restart the router.

I set DNS-O-Matic up for the first time on Sep 12 and it started updating successfully:

Log entry: Sep 12 06:58:10 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully.

Update errors started seven days later:

Sep 19 11:42:30 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

These persisted until September 22nd when I spotted the errors and restarted the router:

Sep 22 18:16:28 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully

Seven days later, on September 29th, I started getting update failures again:

Sep 29 20:19:43 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request failed. Please check the setting.

These persisted until September 30th when I spotted the errors and again reset the router:

Sep 30 22:21:58 192.168.27.1 syslog: ddnsd: update all.dnsomatic.com request successfully

I've checked my account with DNS-O-Matic, which appears to be functioning normally. The router's log unfortunately doesn't give any further details about the failures, so I'm a bit nonplussed about what's causing this odd behaviour.

The 'Dynamic DNS' setup page has the following settings:

Dynamic DNS Server: updates.dnsomatic.com
Host name: all.dnsomatic.com
Period: 10 minutes

Do you have any suggestions?

Cheers, Mike

Attached is a link to firmware 2.52.d51t1, please let me know if this resolves the DNS-0-Matic update issue after 7 days,

Thanks BF - firmware loaded - will post again in eight days or so

Cheers, Mike