IP cloud DDNS doesn't work after upgrade RouterOS

hatta0713 · Sat Sep 14, 2019 1:14 am

After upgraded RouterOS to 6.44.5, IP cloud DDNS doen't work.

> /system routerboard print 
       routerboard: yes
        board-name: hEX PoE
             model: 960PGS
     serial-number: 8A4xxxxxxxxx
     firmware-type: qca9550L
  factory-firmware: 3.41
  current-firmware: 6.44.5
  upgrade-firmware: 6.44.5

 > /ip cloud print 
          ddns-enabled: yes
  ddns-update-interval: none
           update-time: yes
              dns-name: 8a4xxxxxxx.sn.mynetname.net
                status: updating...

> /ping cloud2.mikrotik.com
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                       
    0 159.148.172.251                            56  44 299ms
    1 159.148.172.251                            56  44 295ms
    2 159.148.172.251                            56  44 294ms
    3 159.148.172.251                            56  44 295ms
    sent=4 received=4 packet-loss=0% min-rtt=294ms avg-rtt=295ms max-rtt=299ms

/ping 2a02:610:7501:1000::201
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                       
    0 2a02:610:7501:1000::201                    56  45 294ms echo reply                                                                                   
    1 2a02:610:7501:1000::201                    56  45 291ms echo reply                                                                                   
    2 2a02:610:7501:1000::201                    56  45 292ms echo reply                                                                                   
    3 2a02:610:7501:1000::201                    56  45 291ms echo reply                                                                                   
    4 2a02:610:7501:1000::201                    56  45 291ms echo reply                                                                                   
    sent=5 received=5 packet-loss=0% min-rtt=291ms avg-rtt=291ms max-rtt=294ms

I tried,
downgrad to 6.42.12 => Works fine
downgrad to 6.43.16 => Doesn't work

It is urgent if anyone can help

pietroscherer · Sun Sep 15, 2019 6:30 am

Did you try disabling/enabling IP Cloud after upgrade?

 /ip cloud set ddns-enabled=no

Code: Select all

 /ip cloud set ddns-enabled=yes

Code: Select all

Force update can help you as well:

 /ip cloud force-update

* Look this topic:

viewtopic.php?f=2&t=135603&p=743056&hil ... ns#p667827

prawira · Sun Sep 15, 2019 8:53 am

hi,

i have similar problem with my ccr1009. ip cloud running fine with 6.42.12 but it stop running when upgraded to 6.44.5. the mentioned device return to 6.42.12 at the moment.
disable and enable ip cloud does not solve the problem

Paul

hatta0713 · Sun Sep 15, 2019 9:22 am

pietroscherer,

I tried.

/ip cloud set ddns-enabled=no
/ip cloud set ddns-enabled=yes
/ip cloud force-update

but it doesn't work fine for me.

pietroscherer · Mon Sep 16, 2019 3:03 am

Hey guys,

I tested now on my RB951Ui-2nD and it's works fine. I'm running 6.45.6.
Actually, I even disabled/enabled the service and I could see stop/start working again.

I recommend you send an e-mail to support@mikrotik.com, with a supout.rif.

https://wiki.mikrotik.com/wiki/MikroTik ... structions

Regards,

hatta0713 · Mon Sep 16, 2019 3:25 am

Hi pietroscherer,

Thank you for your suggestion.
I already sent support.rif.

I haven't tried 6.45.6 yet, because I always use long-term channel.
Are there difference of IP cloud between 6.44.5 and 6.45.6 ?

hEX PoE and hEX S are running in our environment.

743 of 773 hEX PoE(960PGS) work fine. 30 don't work.
948 od 948 hEX S(RB760iGS) work fine.

Best regards

pietroscherer · Mon Sep 16, 2019 5:30 am

Hi pietroscherer,

Thank you for your suggestion.
I already sent support.rif.

I haven't tried 6.45.6 yet, because I always use long-term channel.
Are there difference of IP cloud between 6.44.5 and 6.45.6 ?

hEX PoE and hEX S are running in our environment.

743 of 773 hEX PoE(960PGS) work fine. 30 don't work.
948 od 948 hEX S(RB760iGS) work fine.

Best regards

What a bunch of Boards

There are a few changes on the changelog, but nothing related with “non working” IP Cloud.

https://mikrotik.com/download/changelogs

hatta0713 · Mon Sep 16, 2019 12:36 pm

Hi pietroscherer,

I updated to 6.45.6.
But it doesn't works for me.
Also /system backup cloud failed with "Connection error".

I check connectivity to cloud2.mikrotik.com

$ host cloud2.mikrotik.com
cloud2.mikrotik.com has address 159.148.172.251
cloud2.mikrotik.com has address 159.148.147.201
cloud2.mikrotik.com has IPv6 address 2a02:610:7501:1000::201
cloud2.mikrotik.com has IPv6 address 2a02:610:7501:4000::251

> /ping 159.148.172.251
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                       
    0 159.148.172.251                            56  44 283ms
    1 159.148.172.251                            56  44 279ms
    sent=2 received=2 packet-loss=0% min-rtt=279ms avg-rtt=281ms max-rtt=283ms 

> /ping 159.148.147.201
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                       
    0 159.148.147.201                            56  44 294ms
    1 159.148.147.201                            56  44 292ms
    sent=2 received=2 packet-loss=0% min-rtt=292ms avg-rtt=293ms max-rtt=294ms 

> /ping 2a02:610:7501:1000::201
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                       
    0 2a02:610:7501:1000::201                    56  43 244ms echo reply                                                                                   
    1 2a02:610:7501:1000::201                    56  43 241ms echo reply                                                                                   
    sent=2 received=2 packet-loss=0% min-rtt=241ms avg-rtt=242ms max-rtt=244ms 

> /ping 2a02:610:7501:4000::251
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                       
    0 2a02:610:7501:4000::251                    56  43 245ms echo reply                                                                                   
    1 2a02:610:7501:4000::251                    56  43 242ms echo reply                                                                                   
    2 2a02:610:7501:4000::251                    56  43 242ms echo reply                                                                                   
    sent=3 received=3 packet-loss=0% min-rtt=242ms avg-rtt=243ms max-rtt=245ms

Best regards,

hatta0713 · Wed Sep 25, 2019 5:25 am

Any Ideas ?

yosanpro · Wed Dec 11, 2019 3:21 pm

Hi,

I have similar problem, although in my case it's mostly because I changed my RouterBoard.

I used RB951Ui-2HnD before, and because I need better performance, I upgraded it to RB450Gx4. To avoid hassle, I backed up my old RouterBoard, and then restored it to my new RouterBoard, but the problem is the IP Cloud dns-name stuck to old router's address, and it won't even update to new address with the appropriate serial number. I tried to disable and re-enable ddns and forced updated to no avail.

Is there any way to re-activate ip cloud using the new router s/n?

Thanks

yosanpro · Wed Dec 11, 2019 4:33 pm

Hi,

I have similar problem, although in my case it's mostly because I changed my RouterBoard.

I used RB951Ui-2HnD before, and because I need better performance, I upgraded it to RB450Gx4. To avoid hassle, I backed up my old RouterBoard, and then restored it to my new RouterBoard, but the problem is the IP Cloud dns-name stuck to old router's address, and it won't even update to new address with the appropriate serial number. I tried to disable and re-enable ddns and forced updated to no avail.

Is there any way to re-activate ip cloud using the new router s/n?

Thanks

Solved, I don't know how, but when my router got public address, the ddns just activated. Previously I only got private address, I don't know if that's the problem or not though.

bhickey · Sat Dec 14, 2019 6:52 pm

Same problem here today with a hEX RB750Gr3 after upgrading from 6.42.9 to 6.44.6. No combination of disable/enable of 'DDNS Enabled' & Force Update or reboots makes any difference. It worked fine until the upgrade.

The xxxxxxxx.sn.mynetname.net DNS name still points to the old IP address despite the actual external address changing at every reboot.

bhickey · Sun Dec 15, 2019 11:23 pm

Downgrading to 6.42.12 fixed the problem so we'll stay at that version for now until there's any update on a fix for this.

Zacharias · Sat Dec 28, 2019 2:16 pm

Same here ( almost )... after an upgrade to the latest 6.46.1 ( ROS and firmware as well ) no serial name appears under ip cloud... just empty...
Reset to no defaults did not help, enabling-disabling the cloud also did nothing...
It is stuck to ...updating... and the DNS field has no value at all...Time will not update as well through ip cloud...
Last time i had such a problem was when mikrotik moved to the new cloud servers, but this time something else happens...
Device is a 951 ui 2hnd...
For those who will ask, communication to cloud.mikrotik.com and cloud2.mikrotik.com is perfect, the router shows no other problems, it does what it is configured to do and a CAP AC i have behind this router updates its cloud with no problem...

Edit: After a couple of hours it just appeared... who knows...

gotsprings · Sun Dec 29, 2019 5:03 pm

Saw the same thing coming from BELOW 6.40.8 to above.
I could ping cloud2 and everything. I messaged support but due to time differences and it being a production environment... unit came out.

Got a reply a few days later... but field tech threw the unit away... it was a CRS125 from his truck that was missing a power Supply... So i didn't follow up on what happened with Mikrotik.

But in the event of this happening again... I will resort back to my old dyndns updater and keep it running so Mikrotik can look at it.

Zacharias · Sun Dec 29, 2019 7:12 pm

I use the Cloud DNS of mikrotik a lot.. especially in PTP VPNs without any problems...
This is only the second time i faced a problem without an obvious reason to me...

IP cloud DDNS doesn't work after upgrade RouterOS

IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Re: IP cloud DDNS doesn't work after upgrade RouterOS

Who is online