Score:0

DNS resolution fails with "SERVFAIL" after running "udevadm trigger"

pk flag

I'm experiencing an issue where DNS resolution fails with a "SERVFAIL" error after executing the "udevadm trigger" command on my Ubuntu Server. I've noticed that this problem occurs consistently whenever I run that command:

root@backend:~# nslookup azure.com
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   azure.com
Address: 20.43.132.131
Name:   azure.com
Address: 191.235.228.36
...

root@backend:~# udevadm trigger
root@backend:~# nslookup azure.com
Server:         127.0.0.53
Address:        127.0.0.53#53

** server can`t find azure.com: SERVFAIL

root@backend:~# systemctl restart NetworkManager
root@backend:~# nslookup azure.com
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   azure.com
Address: 20.50.2.51
Name:   azure.com
Address: 20.37.196.198
...

Could anyone provide insights into why running "udevadm trigger" might cause DNS resolution to fail? Any help or suggestions would be greatly appreciated. Thank you!

Version: Ubuntu 22.04.1 LTS (5.15.0-46-generic)

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.