1

First, I am not really a network guy. Hence, I would like to validate my approach of setting up a solution, before I dive into the rabbit hole...

I have a small home office / entertainment LAN, which is used by a hand full of Mac and Windows laptops, desktops, entertainment devices, mobile phones and tablets by WLAN. The cable router (UPC Ubee EVW 3226) is working as DNS and DHCP server for the LAN. There is also a Synology NAS, mainly used as fileserver. Which I would like to reach internally and externally under the same url.

Problem now is the external IP of the router can only be reached, from external networks. Hence, I need to reach the NAS under two different IPs under the same URL depending where the laptop is located:

  • When it is located in the LAN nas.example.com needs to resolve to e.g. 10.0.0.123 for the internal address.
  • When it is located outside the LAN, an external DNS (e.g. Route53) has to kick in and resolve nas.example.com to the external IP of the router, which then is doing the port forwarding to the NAS.

My first guess would be to disable the DNS in the router and set up a local DNS server in the lan, which lists nas.example.com under the internal IP. And then there would be the need for an external DNS, knowing the external IP of the router, which would do the forwarding.

Will this work, given I set up a short TTL for the DNS entries to ensure not to have problems with locally cached ips? Or is there something I did not consider, which would prevent the whole setup from working?

I have an Raspberry PI 3 with Ubuntu, would this be a good enough fit for an internal DNS server? Or should I use the Synology NAS for DNS as well?

1 Answer 1

0

The DNS of your router works to resolve outbound traffic.

Your solution will involve port forwarding on the router (consult your manual) and probably a ddns client to be run inside your home network so your LAN is always available at www.$user375251.com Check http://www.howtogeek.com/66438/how-to-easily-access-your-home-network-from-anywhere-with-ddns/

4
  • The ddns part is quiet clear to me, also the role of the DNS of the router in case of domains to be resolved outside my network. I am just worried, I can not configure a DNS to serve a IP for my LAN devices, and a different one, by an external one. I think about using Amazons Route53 with an little script to read out the external IP of the router and update the Route53 setting periodically.
    – user375251
    Nov 23, 2016 at 21:05
  • Your comment would indicate you are not "quiet clear" on ddns, as "your little script to update..." is exactly what ddns-client is. Your router *should have the option to port forward based on the source of the request, but it should also automatically route to your NAS (once configured) if you type www.$user375251.com from within your network.
    – user657451
    Nov 23, 2016 at 21:11
  • maby it's my inability to express myself in a foreign language, but I know, what ddns is doing. I will try to edit my question to clearly express what I need to know.
    – user375251
    Nov 23, 2016 at 21:13
  • Quoting and citing relevant links is very important.
    – Ramhound
    Nov 25, 2016 at 1:29

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .