DNS Registration for VPN Clients (Client to Side)

Options
Dexta
Dexta Posts: 12
First Anniversary Friend Collector First Comment

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

  • Zyxel_Stanley
    Zyxel_Stanley Posts: 1,374  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer
    edited April 11
    Options

    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.

  • Dexta
    Dexta Posts: 12
    First Anniversary Friend Collector First Comment
    edited April 22
    Options

    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

  • Dexta
    Dexta Posts: 12
    First Anniversary Friend Collector First Comment
    edited April 22
    Options

    Dear @Zyxel_Stanley

    Any news for the matter?

    Kind regards,

    Michael

Nebula Tips & Tricks