Synology nas. DDNS works locally but not remotely

[Baldbloke]

Hi folks,

I'm hoping you can help a noob here... I've tried lots of googling and testing before I came here. Still stuck.

On my Synology nas I have enabled Quickconnect. It works fine both locally and remotely. No problem with Share links. I send them to my mate and he can connect to the shared file page and download fine. All great and well but it is slow. I understand that is just the nature of Quickconnect. So it's doing as expected.

I've read that DDNS can be much faster than Quickconnect.
I've created a DDNS profile on the Synology. Status is normal. I've checked NSLookup. It resolves the hostname fine. So far so good.

I can connect with the DDNS locally (My pc and Synology on the same router)

However when my mate uses the new DDNS sharelink (obviously remotely) he gets an error message saying server is not responding or words to that effect. It does not load the share page.

I've done some tweaking and testing on the Synology to no useful effect. To simulate remote connection I have disabled wifi on my mobile phone to ensure it doesn't default to a local connection. I can not connect to the nas with the sharelink remotely.
If I then enable wifi on my phone it all works fine with the sharelink. Presumably that is a local connection when wifi enabled.

I've tried lots of stuff to get remote DDNS sharelinks working. I'm now going round in circles chasing my tail. Any tips for me please?
Can anyone tell me where I'm going wrong?

Thank you

 

[ChrisD.]

Have you port forwarded from your router?

QuickConnect isn't slow, I can download from my mate at line rate, what is your upload speed?

 

[Baldbloke]

Hi ChrisD.
I've portforwarded several ports in an effort to get it working. Probably more than necessary. Ports 80, 443, 5000, 5001. My router does not autoconfigure via the nas. I've done it manually. Perhaps I've not done the portforwarding properly. Very little info on the net for my router, Technicolor dga 0122.

i haven't actually measured speeds. but, a 500mb file takes around 10 minutes with Quickconnect locally verses five or six seconds with DDNS.

My internet provider speed is around 35mb down and 7mb up.

Ok, you got me thinking. If my DDNS is going to be limited by the isp bandwidth for remote connections then I wonder if it is worth the trouble to fix my ddns issue. But then again, it's just plain annoying me now. I gotta get it working just because I don't want it to beat me

Many thanks.

Edit. Good question about the portforwards. Just checked on a site called portchecktool. It can't see my ports. I'll work on what I've done wrong there.

 

[ChrisD.]

A 500 MB files takes 10 minutes with 7 Mbps upload. You can’t make that go faster. You must be testing it locally by mistake.

 

[Baldbloke]

A 500 MB files takes 10 minutes with 7 Mbps upload. You can’t make that go faster. You must be testing it locally by mistake.

Yup. I bet I'm making LOTS of mistakes. Heads spinning with acronyms and confusion as to what's working local and what's working remote. My mate is just going to have to stick with Quickconnect links. I was finding it fun and interesting at first trying to get ddns working but it's getting to be a pain in the rear now.
I'm not giving up trying to get the ddns working. Though I think I'll take a break for an hour or two. Give my brain a rest. But like you say, Quickconnect should be fine.

Meantime I'll have a look to see why portchecker can't see my ports. It "looks" as though I've done it right. But clearly there is an issue.

Many thanks ChrisD

 

[Steveocee]

If you're using DDNS from within your network, it's a local file transfer. Quickconnect is going via QC sevrers so is going out to the web and back.

You are experiencing your router doing a hairpin NAT where it send the data to the internet but the router realises the destination is within your LAN so routes locally.

 

[Baldbloke]

If you're using DDNS from within your network, it's a local file transfer. Quickconnect is going via QC sevrers so is going out to the web and back.

You are experiencing your router doing a hairpin NAT where it send the data to the internet but the router realises the destination is within your LAN so routes locally.

Thank you.
Now that makes sense. I thought I was doing local tests. They seemed to work fine. Then, just to prove a point to myself, to prove these were indeed local tests, I unplugged the dsl line from my router. I would have expected succesful local test. Then found it wouldn't work locally. D'uh? Was I doing local tests or not? Confusion. Head starts spinning. World turned upside down. What you've just said makes sense. It can't go out there to do the U-turn and back to do local? Am I in the ball park?

I still wanna be a tree though .

 

[Steveocee]

Thank you.
Now that makes sense. I thought I was doing local tests. They seemed to work fine. Then, just to prove a point to myself, to prove these were indeed local tests, I unplugged the dsl line from my router. I would have expected succesful local test. Then found it wouldn't work locally. D'uh? Was I doing local tests or not? Confusion. Head starts spinning. World turned upside down. What you've just said makes sense. It can't go out there to do the U-turn and back to do local? Am I in the ball park?

I still wanna be a tree though .

You are in the right ball park.

Oh the fun of networking eh?

 

[Baldbloke]

You are in the right ball park.

Oh the fun of networking eh?

Yes. It is fun, in a strange massochistic sort of way. Well, interesting anyway.
Got myself a Synology 2600 router arriving in a few days. We shall see if my existing router is the stumbling block. More likely it is I who is the stumbling block though..

Back when I was a tadpole this networking malarky hadn't been a thing. Once upon a time I was a whizkid in the technology department. That's when the art of soldering and diy circuit design was a black art. Ah, themz woz the days.
Now I'm just a bloomin' dinosaur.
However I have learnt quite a few new networking acronyms recently. None of which impresses my missus. She still thinks I'm an old codger.

Sorry for the late reply. My alerts don't always appear. Just spotted yours. I like to reply. It's manners.