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.

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:

If the problem persists, contact Verkada Support.

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).

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.

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

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:

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.

Need more help? Contact Verkada Support