PORT FORWARDING FOR MAC OS X SERVER VPN PLUS

This is why I've still got router Internet DNS coming back to its own local DNS Server. It then used the router's Internet DNS settings to do its thing. I've not looked recently but Safe Access seemed to avoid the DHCP DNS resolution and intercept requests to the router as DNS. Network Center -> Local Network -> General.Preferred DNS Server: Router's LAN IP (A.B.C.1).Network Center -> Internet -> Connection.I then use the router as primary DNS server on the LAN.įinally my configuration of RT2600ac DNS settings, whcih work and mostly I was trying to get Safe Access to resolve using the LAN DNS:

On the router I've created slave zones of the master zones. I use Forward First and have OpenDNS as primary and Cloudflare as secondary. Just make sure it's only LAN/VPN devices.Īfter Zones you'll want to setup Resolution.

Choose which you want as these can be used by devices and programmes, such as tcpdump.įor zones there are other settings to tighten up which devices can access them etc. the NAS's LAN IP) so you only get one reverse record per IP. you may have used many subdomain A and CNAME records to one IP (e.g. The reverse zone resolves an IP address to the subdomain that you prefer. Other records: some PTR will probably get created NS for nameservers MX for mailservers. You can also specify wildcard '*' as a subdomain name too. Where A records are subdomain names to IP addresses, and CNAME are subdomain names that are aliased to other subdomain names. Reverse zone (if not created automatically, it's been so long since I did this):įor forward zones you most create A and CNAME records. Master DNS Server: I guess I put the NAS's LAN IP.I run DNS Server on my NAS as the master fwd/rvs zones and also on the router as slave fwd/rvs zones. But as far as I know there are no ACP block logs. I would need some logs from the ACP on NAS to be able to troubleshoot, because there would be listed the IP used for the blocked access. But can't prove it and I have no idea why would that happen. The only explanation for the weird behavior is that when I am connected over VPN, I actually don't use always my home public IP for internet access, but some 'scenarios' still use my computers public IP (of some other remote ISP). Why is that? My public IP is still the same for both VPN connection and my local LAN connection, because I have just one public IP (and the IP is allowed on the ACP). When I am connected over VPN, I can access NAS via local IP, but not public domain name. When I am physically in the local network, I can access NAS via both local IP and public domain name. I have one static public IPv4 at home that is used for incoming and outgoing communication. Maybe you will see something wrong that I don't see. Check the screenshots in the first post where you can see both VPN config and NAS config. Yes I have included VPN subnet in the ACP. My OpenVPN profile is configured with redirect-gateway def1 and when I check my public IP on some webpage, I see my home static public IP.ĭo you have any idea why? What should I check? Some logs? Some configuration? I can access it using the internal IP address of the NAS, but when I try to access it via its public domain name (which works from local network though), I am blocked by the access control profile.Īnd I have no idea why. Because via VPN, I can't access DSM using the public domain name.

PORT FORWARDING FOR MAC OS X SERVER VPN PLUS

I use OpenVPN server on my RT2600ac router via the VPN Plus Server package. From the internet, access is blocked by the access control profile, because I see the DSM's block screen.īut the problem is when I am connected via VPN. If I am connected in my local network, everything works fine and I can access DSM via its public domain name. So points to my public IP too, even though access control profile allows only access from internal addresses and my one public IP (+IPv6 address space which should not be necessary at all, because it is not used for the public domain names). Some services, for example DSM, are not publicly available, but have public domain name pointing to the public IP (to be able to get a Let's Encrypt certificate for the domains on the NAS). All public packages use reverse proxy publicly on 443. I can access the services that are publicly available, for example Drive via. I have a domain name with a few subdomains that I use for some services running on the router and NAS. And behind the router, I have a DS218 (with DSM 7) with forwarded ports 443, 80, 6690. I have a RT2600ac router with public static IPv4.

Port forwarding for mac os x server vpn