BloxOne Endpoint is a lightweight mobile agent that redirects DNS traffic from your remote devices to the BloxOne Cloud. BloxOne Endpoint communicates with BloxOne Cloud using DNS over Transport Layer Security (DoT) on TCP port 443. It allows you to apply applicable security policies to your roaming end users in remote sites and branch offices.
In order for end users to connect to Infoblox cloud services, you must download and install Endpoint on their devices. The client enforces security policies that you apply to the remote networks, regardless of where your end users are and which networks they are connected to. Endpoint listens on port 53 on the device's 127.0.0.2 loopback address. If other software listens on the same port, DNS traffic cannot be redirected to BloxOne Cloud, and your device will not be protected by Endpoint.
When you use Endpoint, DNS queries are sent to BloxOne Cloud directly, except for ((1) queries that target the bypassed internal domains (see Configuring Internal Domains) and (2) internal domains collected through the DHCP server. If you have internal domains that are served by your local DNS servers and you want to reach them without interruptions, you should consider adding them to the bypassed internal domains list so that DNS queries for these internal domains are sent to the local DNS servers instead of BloxOne Cloud.
BloxOne Endpoint supports dual-stack IPv4/IPv6, and IPv6 DNS configurations, thereby protecting all devices regardless of their network environments. This means roaming clients will be protected in different networking environments. When BloxOne Endpoint is connected to a network, endpoint can communicate with BloxOne Cloud using both protocols. Endpoint in a dual-stack environment is able to proxy IPv6 DNS queries and forward them to BloxOne Cloud over IPv4.
Once endpoints are deleted and moved to the Recycle Bin, they will not appear in the Cloud Services Portal. Additionally, the statistics in the Endpoint page's details pane will exclude these deleted endpoints. System administrators have the ability to restore deleted endpoints from the Recycle Bin. By default, any restored endpoints will have a 'disabled' status. However, system administrators can choose to either modify these endpoints or restore them while maintaining the 'disabled' status. For information, seeViewing Endpoint Devices.
When an endpoint group is deleted, all the endpoints associated with the deleted group will move to the default group. If an endpoint group containing deleted endpoints is deleted, then all deleted endpoints associated with the deleted endpoint group will also move to the default group where their deleted status will remain unchanged. When restoring any of these deleted endpoints, they will continue to remain members of the default endpoint group. For information, see Viewing Endpoint Groups.
Note
Endpoint does not support IPv6-only environments.
Changes in the FQDN of the host running Endpoint will be added to the existing endpoint group in the Cloud Services Portal and will not be attached to the default endpoint group. Security policies of all the existing endpoint groups will be affected. If the host is re-installed after the FQDN changes have been made without assigning it to a group, it will be added to the default endpoint group.
For information on setting up, using endpoint and endpoint services, refer to the following topics.