DNS Registration for VPN Clients (Client to Side)
Freshman Member
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
Zyxel Employee
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 147 Nebula Ideas
- 96 Nebula Status and Incidents
- 5.7K Security
- 262 USG FLEX H Series
- 271 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.4K Consumer Product
- 249 Service & License
- 387 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.5K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 73 Security Highlight
