Custom domain for local network

RémyDG

Hello!

I have a Synology Nas that I have set in order to be accessible from outside my home, with a custom domain that I own, ports forwarding and so on.

When I access it from outside it works just fine but when I try to access from my local network it is very slow and it sometimes does not work at all…

I think that this is due to the fact that the requests go all the way to internet then back to my local network, this went even worst when I installed the InternetBooster 5G that I disabled for my nas in order to work at all.

Now I would like to know how I could solve the part on local network.

Like for example manually input the local address the DNS cache of my InternetBox 3.

Thank you in advance.

Black Mamba

@RémyDG

thank’s for contribution

this discussion in German Community may help

Synology via OpenVPN ohne Portforwarding von weite… | Swisscom Community

Zugriff per Subdomain DDNS auf Synologie NAS Docke… | Swisscom Community

RémyDG

thanks it is very interesting but it does not help me.

It now works more often, maybe due to an update…

I am still looking for a way to tell my computer “go there (on the local network)” instead of asking external DNS server to know it has to remain on the local network

Tchris

Can’t provide you with a step-by-step fix myself, but a parallel.

(…and what I believe is a direct fix in link below).

All outbound from my LAN is examined by pfSense running Unbound & pfBlockerNG-devel, …and some other stuff not related to your question.

DNS queries for 4 million “malicious” sites are redirected to a one pixel “web page” on pfSense – over 400,000 times/month. Sorry user: my LAN, I decided you can’t go there. Justification: my public IP address..

…DNS re-redirection (by pfBlocker).

NTP queries redirected to pfSense itself (pfSense uses a nearby Stratum-1 server that has local Stratum-0 GPS access). Sorry user: my LAN, I decided you will use my Time. Justification: log comparison if issues.

…port/protocol redirection (by pfSense).

Redirecting DNS/ports/protocols to wherever you want is very-evidently do-able from the above examples

…I just don’t need to do what you want to do, so can’t provide a step-by-step.

What I do is simple pfSense GUI stuff.

A link showing how to persuade Unbound to do EXACTLY what you ask::

https://dnswatch.com/dns-docs/UNBOUND/

…it is long …it is technical …it is command-line, and you need a box running Unbound..

A quote from that link:

“We can setup Unbound to spoof the dns query of LAN clients so instead of getting the external address for the external name, they receive an internal ip for the external name. webserver.example.com which normally resolves to 111.222.333.444 now resolves 10.0.0.222. 10.0.0.222 would be the same web server which is located on the inside of the firewall in a DMZ”.

Chris

bitracer

For this to work properly you need something called hairpin NAT rule.

https://en.wikipedia.org/wiki/Network_address_translation#NAT_hairpinning

Some routers do it automatically when you configure port forwarding NAT rules. For example FritzBox. On others you need to configure this manually in the firewall/NAT config.

bitracer

I just configured the port forwarding in my IB4. Good news is that the hairpin NAT rule is automatically created. I was able to access my NAS using the FQDN (host.mydomain.com:port).