DNS connectivity issues

[Yaslanagrey 0]

I've had a look through a lot of the other posts, but I can't find something the same as what i'm dealing with.

I've connected my Emby to a DNS... but It seems to drop out roughly every... half hour...maximum...

It only seems to refresh once i open the link on my computer, however it only lasts a little bit of time...

and then I'll try and connect via my mobile and BAM.. it's down again..

Can someone walk me through what I'm doing wrong?

using FreeDNS


Router has been mapped to forward through Port 8096

http://yaslana.strangled.net

It works for a bit.. but half the time you start streaming something and then it disconnects..


I can't seem to find anything in the logs, however not 100% sure what I'd be looking for anyway.

[rbjtech 5284]

DDNS is simply dynamically updating your WAN Address to an internet name based on updates from a local update 'client'.

 

Based on the IP resolution of the FQDN provided (using www.yougetsignal.com to remote test that IP on Port 8096) the emby port is closed - ie port forwarding is not setup correctly / firewall issue.

 

Ensure your DDNS is correctly updating to your real WAN address - if that is correct, then it must be a port forwarding issue or something local like a incoming firewall rule(s) has not been setup.

 

Remember DDNS updates can take a while to replicate - a couple of mins to a couple of hours sometimes.

 

If it works 'sometimes' and the WAN IP does not change (unless you keep resetting your Router, it usually keeps the allocated IP fairly static) - then it may simply be a WAN bandwidth/reliability issue.

Edited May 9, 2020 by rbjtech

[Yaslanagrey 0]

So it works, if i open the link in the browser (which local network so doesn't load) then i will work for a bit.. however no WAN IP change... and the outgoing signals direct to IP address worked fine even with several locations connected. it's just that my IP had a tendency to jump around a bit that i considered the dns option..

So what would be the difference between direct IP load and the DNS load in terms of WAN bandwidth?

If you search it now.. It'll probably come up as blocked.

If you search it after i open the web address through emby... it'll probably work for 10-15 minutes

[pwhodges 2014]

 after i open the web address through emby...

 

What does this mean?  What are you doing to "open the web address through Emby"?

 

Paul

[Q-Droid 989]

I'm having a hard time understanding your description of the problem but it almost sounds like you've setup port-triggering and not port-forwarding on your router.

[rbjtech 5284]

I'm having a hard time understanding your description of the problem but it almost sounds like you've setup port-triggering and not port-forwarding on your router.

 

Sounds a good possibility this is the problem ?

 

"So it works, if i open the link in the browser (which local network so doesn't load) then i will work for a bit." - ie you are activating the port triggering.

 

Which then allows traffic incoming - but port triggering has a timeout value - usually 5 mins - after which, you need to create outbound traffic again by clicking on the WAN link ...

 

"Port triggering is unsuitable for servers behind a NAT router because it relies on the local computer to make an outgoing connection before it can receive incoming ones"  - Wiki

 

So remove the port trigger, and change it to port forward - and you should be good.

 

DDNS is not related to any of this 

Edited May 9, 2020 by rbjtech