I think I found a fix, but I’m not sure that this is the way to go.
I was able to get NetworkManager to handle name resolution with the following steps:
sudo systemctl disable systemd-hostnamed.service
sudo rm /etc/resolv.conf
sudo systemctl restart NetworkManager
ping bing.com
Should this have been required?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
Thank you for reaching out with your question. The steps you took to address the DNS resolution issue on Torizon 7, such as disabling the systemd-hostnamed service and removing the /etc/resolv.conf file, are not typically required for standard DNS resolution. These actions might have temporarily resolved your issue, but they are not standard practice.
In Torizon, NetworkManager is responsible for managing network configurations, including DNS settings. The /etc/resolv.conf file is usually managed by NetworkManager, and manual modifications can lead to conflicts or unexpected behavior. Disabling systemd-hostnamed is also not a standard procedure for resolving DNS issues, as this service manages the system’s hostname independently of DNS resolution.
For DNS resolution issues, consider these standard troubleshooting steps:
Check NetworkManager Configuration: Ensure NetworkManager is correctly configured to handle DNS. You can verify this by checking the DNS settings in the NetworkManager configuration files or using the nmcli command-line tool.
Verify Network Connectivity: Make sure your device has a stable network connection and can reach DNS servers.
Review DNS Server Settings: Confirm that the correct DNS servers are being used. This can be done through NetworkManager settings or by inspecting the /etc/resolv.conf file.
Restart NetworkManager: If changes are made, restart NetworkManager to apply them: sudo systemctl restart NetworkManager.
Check for Updates: Ensure your Torizon system is up-to-date, as updates may resolve underlying issues.
Following these steps should help maintain system stability and ensure proper DNS resolution. If issues persist, further investigation into network logs and configurations may be necessary.
I hope this helps! If you have any more questions, feel free to ask.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
Greetings @kdubious,
Are you claiming that ping bing.com was not working until you did those steps?
That would be strange since I just flashed our latest 7.1.0 Torizon OS image, and on first boot it seems to work fine on my module:
ping -c 10 bing.com
PING bing.com (150.171.28.10): 56 data bytes
64 bytes from 150.171.28.10: seq=0 ttl=117 time=11.940 ms
64 bytes from 150.171.28.10: seq=1 ttl=117 time=11.919 ms
64 bytes from 150.171.28.10: seq=2 ttl=117 time=11.672 ms
64 bytes from 150.171.28.10: seq=3 ttl=117 time=11.004 ms
64 bytes from 150.171.28.10: seq=4 ttl=117 time=10.911 ms
64 bytes from 150.171.28.10: seq=5 ttl=117 time=10.418 ms
64 bytes from 150.171.28.10: seq=6 ttl=117 time=10.181 ms
64 bytes from 150.171.28.10: seq=7 ttl=117 time=10.392 ms
64 bytes from 150.171.28.10: seq=8 ttl=117 time=11.615 ms
64 bytes from 150.171.28.10: seq=9 ttl=117 time=11.153 ms
--- bing.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 10.181/11.120/11.940 ms
Did you do any modifications to this OS image or is it the default image from Toradex?
Best Regards,
Jeremias