hostmyi.blogg.se

Nat loopback
Nat loopback









nat loopback
  1. Nat loopback full#
  2. Nat loopback windows#

Create CNAME records for main devices that might need swapping (mainnas, backupnas, etc) pointing to the relevant A record.All physical devices get an A record (defines the IP that I've reserved in DHCP).The reverse proxy features of DSM needs to receive the traffic in order for it to do its reverse proxying. and the DNS server is the master resolver (internally) for the domain so it won't ask out on the Internet.Īt minimum you need to create records for every subdomain you want to use internally, even it they all point to the NAS. If you want to use any other subdomains then you need to define these in the DNS server, otherwise you local device will ask the SRM's DNS server to resolve it and it won't have a record so will respond 'no idea'. Nslookup This will say which DNS server is being used and what IP address it resolves for the request.

Nat loopback windows#

refresh the DCHP configuration and then launch you console terminal of choice (Mac Terminal, WIndows cmd.exe) and run the nslookup command: The last bit is handy when you want to be lazy you can enter just the subdomain in the URL and your device will append.

  • Forward known DNS server: Disabled (I didn't want local devices to get any external DNS server from the SRM Internet settings).
  • Nat loopback full#

    I probably set the SRM's DNS Server as primary at one time but cannot remember what happened: it probably worked but thought having an off-box server was better in case the local DNS hadn't full launched when SRM needed it during reboot. SRM's Internet settings have the NAS as DNS primary and Cloudflare as secondary (I found this worked better than using my backup NAS as a second internal DNS server). This is what I have done and helps to have going direct at home, where is my personal domain and is managed via Namecheap for Internet resolution. So I'm assuming you've set up various records (A and CNAME) on the NAS's DNS Server for all your home devices and the various subdomains of NAS packages. With slave zones you can convert these to master zones should the NAS have a problem. For each zone you can then setup Forward First so that any no local resolution gets sent to another DNS service (OpenDNS, etc etc). You may want to use the zone settings to limit which devices can access and do what: depends on you environment. On the router's DNS Server you create slave zones for the master zones you created on the NAS DNS Server. You can use DNS Server on both the NAS and router, and in fact will provide some resilience and backup too.











    Nat loopback