DDNS failed.....

[tekguru]

I'm seeing an issue today whereby the DDNS settings on the DS918+ are blank (instead of the external IP being shown) and the NAS is reporting there is no external connectivity. On checking the Synology account for the connection that reports all is normal.

I've rebooted the NAS and it looking at the Synology account it now shows that DDNS is offline. Hostname and IP blanked out...

Any ideas folks?

 

[Coop777]

Synology should work with you on understanding what’s going on now that you’ve been able to corner them. Most likely they’ll request remote access and I don’t like that.

Yep, won't do it.

 

[tekguru]

I wish I didn't have to but if it helps resolve the darned problem.....

Nothing that private on the NAS......

 

[Bogey]

The old school IT in me says what changed before it broke. If after DSM 7 upgrade the problem started, I'd fault DSM and given the weirdness with all DSM "upgrades" lately wouldn't surprise me a bit. Proving it becomes the obvious challenge...

I’m experiencing DDNS problems too. I have bith synology.me and a custom Cloudflare script. Both have problems connecting….since upgrading to DSM7.
My router is Asus, behind a Fritz 7490 modem/router. So no similarities with the previous mentioned configurations. I haven’t tested a VM yet, but I suspect DSM7 is the culprit.

 

[tekguru]

That is good news (in a way) as it verifies the issue. Please raise a ticket with Synology and reference my ticket. We need to keep on hitting them with this issue to get them to fix it.

 

[Bogey]

What’s really weird is after disabling both DDNS entries and reenabling one after the other, they’re now both up again

 

[tekguru]

Yep any 'playing' with the settings or changing which LAN is the primary can get it to re-enable.

Anyway I've just updated my ticket - telling them what you've said and pointing them at this thread.

 

[fredbert]

Almost sounds like a run and forget (i.e. not triggered) script/exe that isn't fault tolerant.

 

[tekguru]

Annoying though that it wasn't an issue in DSM6.

 

[Bogey]

That is good news (in a way) as it verifies the issue. Please raise a ticket with Synology and reference my ticket. We need to keep on hitting them with this issue to get them to fix it.

Done

 

[tekguru]

Done

Brilliant, can you let me know the ticket number so I can also reference it to them?

 

[cslekniws]

Yep I'm pretty convinced it is some sort of weird conflict between DSM7 and the Orbi. The Orbi had been running flawlessly from December right until I did the DSM7 upgrade. Then the problems occurred.
Synology says it is the Orbi. Netgear say there should not be any problems with the Orbi and the latest firmware was issued to fix DDNS issues.

@dorsi did you raise a support ticket with Synology at all?

I wish there was somebody on here running DSM6 with an Orbi running the latest firmware who could state they have no problems at all.

@Seaprobe is it an Orbi you're using too?

I wish Synology would own up to the issue.

I did @tekguru . DSM 6.x with my Orbi in router mode. No problem. Only dsm7 with Orbi in router mode gave de DDNS problem.

 

[tekguru]

Thanks for that can you advise your ticket number please so I can throw that at Synology as well? The more tickets we can pile up I think the quicker we can get it fixed.
I had hoped changing LAN port had stabalised it for me as I had hit nearly 2 days without problems but it has just dropped again. Sigh.

 

[cslekniws]

Thanks for that can you advise your ticket number please so I can throw that at Synology as well? The more tickets we can pile up I think the quicker we can get it fixed.
I had hoped changing LAN port had stabalised it for me as I had hit nearly 2 days without problems but it has just dropped again. Sigh.

My ticket is #2889337

 

[tekguru]

Thanks I’ve referenced your ticket in mine so that is three of us hopefully hitting then with the issue. Can you guys report back in this thread what they tell you to do etc?

 

[Bogey]

Thanks I’ve referenced your ticket in mine so that is three of us hopefully hitting then with the issue. Can you guys report back in this thread what they tell you to do etc?

Synology responded:

We had similar feedback with DSM 7 update and custom ddns provider, staying stuck on loading. The behavior changed when curl the URL of the customize DDNS provider

Could you tell me what is the query utl in used ? As I do not have the exact query for cloudflare, here are some exemple for fix with other case we had :

For instance, change the query URL from

https://__USERNAME__:[email protected]?hostname=__HOSTNAME__&myip=__MYIP__

change to

https://api.cp.easydns.com/dyn/generic.php?hostname=__HOSTNAME__&myip=__MYIP__ (remove the parameter of __USERNAME__:__PASSWORD__@)

In 2893880, Please change the query URL from

https://__USERNAME__:[email protected]/v3/update?hostname=__HOSTNAME__&myip=__MYIP__

change to

https://ddns.nbtech.biz/v3/update?hostname=__HOSTNAME__&myip=__MYIP__ (remove the parameter of __USERNAME__:__PASSWORD__@)

So if you have the parameter __USERNAME__:__PASSWORD__@ in the query, try without it.

Waiting for your feedback,

I don’t know how this would help. It’s not really relevant to our issue, is it?

 

[tekguru]

Looks like they are doing all they can for both of us not to acknowledge the issue. Can you switch to using the Synology DDNS system and prove to them that is failing too?
Have they asked you to do tests and passed the data back to them?
I kept on insisting they fed back the issues to the developers. On mine they have turned on advanced logging and supposedly investigating the times I have told them the issues have occurred.

 

[Bogey]

When I raised the ticket I wrote that am using two DDNS entries: synology.me and Cloudflare. They only addressed Cloudflare, nothing about synology.me (and that was the one that failed).
No tests or data has been requested by them (nor sent by me).

 

[fredbert]

They only addressed Cloudflare, nothing about synology.me (and that was the one that failed).

Did you reply that you also are looking for a resolution to the synology.me DDNS issue too? Worth pointing out that this is important.

 

[tekguru]

Useless they are. Stress to them it is their DDNS which is the issue. I had the tell them in very simplistic language what the issue is. Maybe the language barrier.

 

[Bogey]

I replied to them:

The custom script can be found here:
GitHub - mrikirill/SynologyDDNSCloudflareMultidomain: Synology DDNS Cloudflare service provider with multidomains and subdomains

But Cloudflare isn’t the issue. That script is and has been working for quite some time, while actively monitored.
It’s synology.me DDNS that is the problem.