after running some tests on my Verdin board and your Torizon Cloud platform, it seems like both provisioning and a online connection to the cloud server need a working DNS-server configured on the Verdin.
Is it possible to configure the board to not need a DNS server and still be able to connect to the cloud server? We would like to reduce the network configuration required in field, for the online updates to work.
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Did you like my answer?
Hello,
Based on the available documentation, I don’t have specific information about configuring Torizon Cloud connectivity to work without DNS servers. The sources discuss various aspects of Torizon updates and network configuration, but don’t provide detailed guidance on DNS-free cloud connectivity.
What the Documentation Shows
The Toradex Easy Installer documentation mentions that network connectivity issues can occur when DNS servers are missing (1). It states that “In case this fails (e.g. due to missing DNS server or standard Gateway) an error will be shown” and recommends ensuring “your DHCP provides a complete Network configuration that allows Internet access” (1).
Potential Approaches to Explore
While not explicitly documented in the available sources, you might consider:
Static IP Configuration: Configure your Verdin board with static network settings that include hardcoded IP addresses for Torizon Cloud servers instead of relying on DNS resolution.
Local DNS Resolution: Set up a minimal local DNS configuration or use /etc/hosts entries to resolve Torizon Cloud server names to IP addresses.
Network Infrastructure: Consider if a minimal DHCP server with DNS capability could be deployed in your field environments.
Recommendation
I’d suggest checking the complete Torizon documentation for network configuration options, particularly around static IP settings and DNS alternatives. You may also want to test different network configurations in your development environment to determine the minimal requirements for Torizon Cloud connectivity.
For the most accurate and up-to-date information about DNS requirements and alternative configurations for Torizon Cloud connectivity, I recommend consulting the full Torizon documentation or reaching out through the official support channels.
A working DNS server is required so that the devices can properly access the Torizon Cloud and its features.
The following page documents the network requirements: Device and Fleet Management | Toradex Developer Center
There is no way around this as these domains may resolve to different IPs.
Is the list of requirements outlined in the page enough to do the necessary network configuration for your use case?
thank you for the swift response.
Since a DNS server is needed, we will be taking the correct steps to ensure a working one can be configured for all devices.