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. For non-MAC devices, Endpoint listens on port 53 on the device's 127.0.0.1 loopback address. For MAC devices only, 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.
...
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.
...