All Collections
Viewing Station
Viewing Station Network Settings
Viewing Station Network Settings

Learn about the required network settings for Verkada viewing stations

Updated over a week ago

This article outlines the required network settings that your Verkada viewing stations need to communicate 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

Viewing stations must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Viewing stations support both wired and wireless internet connections. They use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations.

If you require your viewing station 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

Viewing stations 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 intercom where the DNS server is on the network and the intercom communicates using UDP port 53.

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

Firewall settings

Viewing stations 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 viewing stations to communicate with the general required endpoints.

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

  • 34.216.15.26 - UDP/123

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

  • *.vcamera.net - TCP+UDP/443

  • *.apple.com - TCP/80

  • *.apple.com - TCP/443

  • *.apple.com - TCP/2197

  • *.apple.com - TCP/5223

  • *.apple.com - UDP/123

  • *.aaplimg.com - UDP/123

  • app-measurement.com - TCP+UDP/443

  • browser-intake-datadoghq.com - TCP+UDP/443

  • firebaselogging-pa.googleapis.com - TCP+UDP/443

  • crl.entrust.net - TCP/80

  • crl3.digicert.com - TCP/80

  • crl4.digicert.com - TCP/80

  • *.mzstatic.com - TCP/443

  • ocsp.digicert.com - TCP/80

  • ocsp.entrust.net - TCP/80

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

  • 34.216.15.26 - UDP/123

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

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

  • device-nlb.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

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

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

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

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

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

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

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

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

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

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

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

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

  • *.apple.com - TCP/80

  • *.apple.com - TCP/443

  • *.apple.com - TCP/2197

  • *.apple.com - TCP/5223

  • *.apple.com - UDP/123

  • *.aaplimg.com - UDP/123

  • app-measurement.com - TCP+UDP/443

  • browser-intake-datadoghq.com - TCP+UDP/443

  • firebaselogging-pa.googleapis.com - TCP+UDP/443

  • crl.entrust.net - TCP/80

  • crl3.digicert.com - TCP/80

  • crl4.digicert.com - TCP/80

  • *.mzstatic.com - TCP/443

  • ocsp.digicert.com - TCP/80

  • ocsp.entrust.net - TCP/80

Region: Europe

  • 34.216.15.26 - UDP/123

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

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

  • firmware.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

  • vfilter.prod2.verkada.com - TCP+UDP/443

  • vecho.prod2.verkada.com - TCP+UDP/443

  • vlocaldns.prod2.verkada.com - TCP+UDP/443

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

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

  • vprovision.prod2.verkada.com - TCP+UDP/443

  • vsensor.prod2.verkada.com - TCP+UDP/443

  • vstream.prod2.verkada.com - TCP+UDP/443

  • vsubmit.prod2.verkada.com - TCP+UDP/443

  • vvx.prod2.verkada.com - TCP+UDP/443

  • device-nlb.prod2.vcamera.net - TCP+UDP/443

  • nlb.prod2.vcamera.net - TCP+UDP/443

  • *.apple.com - TCP/80

  • *.apple.com - TCP/443

  • *.apple.com - TCP/2197

  • *.apple.com - TCP/5223

  • *.apple.com - UDP/123

  • *.aaplimg.com - UDP/123

  • app-measurement.com - TCP+UDP/443

  • browser-intake-datadoghq.com - TCP+UDP/443

  • firebaselogging-pa.googleapis.com - TCP+UDP/443

  • crl.entrust.net - TCP/80

  • crl3.digicert.com - TCP/80

  • crl4.digicert.com - TCP/80

  • *.mzstatic.com - TCP/443

  • ocsp.digicert.com - TCP/80

  • ocsp.entrust.net - TCP/80


Need more help? Contact Verkada Support

Did this answer your question?