DNS Registration for VPN Clients (Client to Side)
Since we changed our Firewall from a USG60 to ATP500 and switched to Nebula the client registration (VPN-Client) on the AD DNS-Server is not working anymore. The VPN Client can resolve all hostnames on the network. But on the network the VPN Client hostname cannot be resolved.
It seems like the dhcp which for the vpn is handled by the atp500 does not register the clients on the dns server. On the USG60 it worked flawless. Is this a known problem or is there any workaround for this?
Kind regards,
Michael
All Replies
-
Hi @Dexta,
Once a client establishes a VPN tunnel, the firewall will provide IP information to the client.
Within the "Advanced Options," you'll find settings for the Client VPN subnet and DNS name servers.
Here, you can configure the DNS IP settings to point to your AD server.
This configuration will enable the client to query intranet hostnames using your own AD.0 -
Dear @Zyxel_Stanley
We already have our DNS Server listed under "Custom nameservers" and the nameresolution on the vpn-client works flawlessly. The problem is, that the Firewall (DHCP) does not register the vpn-clients on the dns server. So i cannot resolve the hostname of any vpn-client computer on our network. This is important to us for managing remote computers.
Kind regards,
Michael
0 -
0
Categories
- All Categories
- 396 Beta Program
- 2.1K Nebula
- 117 Nebula Ideas
- 81 Nebula Status and Incidents
- 5.1K Security
- 86 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 69 Switch Ideas
- 916 WirelessLAN
- 34 WLAN Ideas
- 5.9K Consumer Product
- 211 Service & License
- 337 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2K FAQ
- 912 Nebula FAQ
- 419 Security FAQ
- 237 Switch FAQ
- 207 WirelessLAN FAQ
- 46 Consumer Product FAQ
- 139 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 72 About Community
- 62 Security Highlight