All Collections
Access Control
Access Control Network Settings
Access Control Network Settings

Learn about the required network settings for Verkada Access Control devices

Updated over a week ago

This article outlines the required network settings that your Verkada access controllers 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.

Status LED

At the top left of the physical access controller, if you see a flashing blue status LED this indicates that the access controller is not communicating with Command.

If you see this behavior:

  • Check that the network is set up correctly for the access controller.

  • See Verkada Access Offline Operation to understand what the access system does when it cannot communicate with Command.

If the problem persists, contact Verkada Support.

IP address

Access controllers need an IPv4 address to communicate on the local area network (LAN) and to Command through the internet. Access controllers use Dynamic Host Configuration Protocol (DHCP), UDP ports 67 and 68, to obtain their IP addresses and network configurations.

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

Domain Name System

Access Controllers 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 access controller where the DNS server is on the network and the access controller communicates using UDP port 53.

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


For specifics on power requirements, see the access controller's datasheet.

Firewall settings

Verkada access controllers 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 access controllers to communicate with the general required endpoints.

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

  • - UDP/123

  • - UDP/123 + TCP+UDP/443

  • * - 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

Standard Verkada Endpoints

NTP Endpoints

Access Control Endpoints

Region: Europe

Standard Verkada Endpoints

NTP Endpoints

Access Control Endpoints

Need more help? Contact Verkada Support

Did this answer your question?