DSM 7.0 Domain name to target NAS

[piperseneca]

Good afternoon.

Sorry if the thread already exist. I couldn't find something similar.

My ultimate goal is to use my "exempledomain.com" on my DS920+.

The NAS is connected onto a RT2600ac. My exempledomain.com is through OVH and I already DNS-ed the domain to point towards my ISP IP address. Right now when I type exempledomain.com, it goes onto the SRM of the RT2600ac.

- How should I parameter the Syno router so that when I type exempledomain.com, it goes into the DSM on my NAS ?
- How should I then parameter MX and A DNS records to have MailPlus Server working with [email protected] ?

Thank you lots for your help

Art.

 

[Rusty]

Reverse proxy will solve the problem of getting to your nas using a custom name but also with a port forward towards a specific port on your NAS (as opposed to your router). So just configure a port forward towards a service/port on your nas.

Reverse proxy can kick in later on if you have multiple services that you want access to.

Have you configured your email records on your dns provider side?

 

[piperseneca]

Reverse proxy will solve the problem of getting to your nas using a custom name but also with a port forward towards a specific port on your NAS (as opposed to your router). So just configure a port forward towards a service/port on your nas.

Reverse proxy can kick in later on if you have multiple services that you want access to.

Have you configured your email records on your dns provider side?

Thanks for your answer. I already have these ports opened (see picture) but it doesn't change anything. How do I set up Reverse Proxy on SRM ?

I have not configured MX yet.

 

[Rusty]

How do I set up Reverse Proxy on SRM ?

You can’t. RP is on DSM.

 

[fredbert]

I don't have UPnP firewall policies enabled on the SRM router so I can't say for certain, but ... It looks like you have UPnP enabled in Network Center / Local Network / General:

Which allows any LAN device to configure you perimeter security to enable them to behave as they see fit. While this makes things easy for you it also allows compromised and poorly implemented devices to remove protection by opening holes in the firewall policy. You really should only open the access that you want, and to do this you can start by disabling UPnP and manually configure the firewall and port forwarding.

If you are running the HTTPS web server on the NAS then it will likely be using TCP port 443. Assuming 192.168.1.8 is your NAS and you want this to be accessible from the Internet then on the RT2600ac in Network Center:

• Add a rule in Port Forwarding to forward connections to the router's WAN interface on to the NAS:
  • Private IP address: 192.168.1.8
  • Public port: 443
  • Private port: 443
  • Protocol: TCP
• In Security / Firewall there should be a corresponding new rule (greyed) to allow access to the NAS. The firewall policy is applied after the forwarding, but you need both rules for this to work.

Tutorial - How the Internet (IPv4) works ... a simplistic overview

The Internet enables computers and devices to talk to each other across the world. To do this requires each device to be uniquely identifiable. On the local network Any device with a WiFi or LAN interface will have a unique MAC address that is...

www.synoforum.com