All Collections
Guest
Guest Network Settings
Guest Network Settings

Learn about the required network settings for Verkada Guest features

Updated over a week ago

This article outlines the required network settings that your Verkada Guest tablets and phones need to be able to communicate with the printer through the LAN and speak with Verkada Command. For more information on the required network settings for other Verkada product lines see Required Network Settings.

Note: Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command.

IP address

Guest tablets and phones must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Guest devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations.

If you require your Guest device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device's label).

Domain Name System

Guest tablets and phones use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Guest device where the DNS server is on the network and the Guest device communicates using UDP port 53.

Note: DNS over HTTPS (DoH) is currently not supported.

Firewall settings

Guest tablets and phones require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the Guest devices to communicate with the general required endpoints.

These are the general domains to allow, applicable for all organization-regions:

  • 3.1.77.0/24 - UDP/10000-20000

  • 3.104.90.0/24 - UDP/10000-20000

  • 3.112.80.0/24 - UDP/10000-20000

  • 3.122.181.0/24 - UDP/10000-20000

  • 18.228.249.0/24 - UDP/10000-20000

  • 34.203.250.0/23 - UDP/10000-20000

  • 34.216.15.26 - UDP/123

  • 35.156.191.128/25 - UDP/10000-20000

  • 52.215.127.0/24 - UDP/10000-20000

  • 54.65.63.192/26 - UDP/10000-20000

  • 54.169.127.128/26 - UDP/10000-20000

  • 54.171.127.192/26 - UDP/10000-20000

  • 54.172.60.0/23 - UDP/10000-20000

  • 54.244.51.0/24 - UDP/1024-65535

  • 54.252.254.64/26 - UDP/10000-20000

  • 177.71.206.192/26 - UDP/10000-20000

  • *.verkada.com - UDP/123 + TCP+UDP/443

If your firewall does not allow wildcard masking, or you prefer to have the entire FQDN of the endpoint in your firewall rules, you can add the domains to your allowlist based on the region your devices are in.

Note: Your region is selected when you create an organization in Command.

Region: United States

  • 3.1.77.0/24 - UDP/10000-20000

  • 3.104.90.0/24 - UDP/10000-20000

  • 3.112.80.0/24 - UDP/10000-20000

  • 3.122.181.0/24 - UDP/10000-20000

  • 18.228.249.0/24 - UDP/10000-20000

  • 34.203.250.0/23 - UDP/10000-20000

  • 34.216.15.26 - UDP/123

  • 35.156.191.128/25 - UDP/10000-20000

  • 52.215.127.0/24 - UDP/10000-20000

  • 54.65.63.192/26 - UDP/10000-20000

  • 54.169.127.128/26 - UDP/10000-20000

  • 54.171.127.192/26 - UDP/10000-20000

  • 54.172.60.0/23 - UDP/10000-20000

  • 54.244.51.0/24 - UDP/1024-65535

  • 54.252.254.64/26 - UDP/10000-20000

  • 177.71.206.192/26 - UDP/10000-20000

  • api.control.verkada.com - TCP+UDP/443

  • api.global-prod.control.verkada.com - TCP+UDP/443

  • device-nlb.verkada.com - TCP+UDP/443

  • device.pyramid.verkada.com - TCP+UDP/443

  • firmware.control.verkada.com - TCP+UDP/443

  • index.control.verkada.com - TCP+UDP/443

  • nlb.verkada.com - TCP+UDP/443

  • relay.control.verkada.com - TCP+UDP/443

  • relay.global-prod.control.verkada.com - TCP+UDP/443

  • time.control.verkada.com - UDP/123

  • update.control.verkada.com - TCP+UDP/443

  • user.pyramid.verkada.com - TCP+UDP/443

  • vconductor.global-prod.command.verkada.com - TCP+UDP/443

  • vdoorman.command.verkada.com - TCP+UDP/443

  • vdoorman.prod1.command.verkada.com - TCP+UDP/443

Region: Europe

  • 3.1.77.0/24 - UDP/10000-20000

  • 3.104.90.0/24 - UDP/10000-20000

  • 3.112.80.0/24 - UDP/10000-20000

  • 3.122.181.0/24 - UDP/10000-20000

  • 18.228.249.0/24 - UDP/10000-20000

  • 34.203.250.0/23 - UDP/10000-20000

  • 34.216.15.26 - UDP/123

  • 35.156.191.128/25 - UDP/10000-20000

  • 52.215.127.0/24 - UDP/10000-20000

  • 54.65.63.192/26 - UDP/10000-20000

  • 54.169.127.128/26 - UDP/10000-20000

  • 54.171.127.192/26 - UDP/10000-20000

  • 54.172.60.0/23 - UDP/10000-20000

  • 54.244.51.0/24 - UDP/1024-65535

  • 54.252.254.64/26 - UDP/10000-20000

  • 177.71.206.192/26 - UDP/10000-20000

  • api.global-prod.control.verkada.com - TCP+UDP/443

  • api.prod2.control.verkada.com - TCP+UDP/443

  • index.prod2.control.verkada.com - TCP+UDP/443

  • relay.global-prod.control.verkada.com - TCP+UDP/443

  • relay.prod2.control.verkada.com - TCP+UDP/443

  • time.control.verkada.com - UDP/123

  • update.control.verkada.com - TCP+UDP/443

  • vconductor.global-prod.command.verkada.com - TCP+UDP/443

  • vconductor.prod2.command.verkada.com - TCP+UDP/443

  • vdoorman.prod2.command.verkada.com - TCP+UDP/443

Need more help? Contact Verkada Support

Did this answer your question?