Score:0

dig @hostIP works but dig alone does not lots of errors saying my host name can not be resolved. named is fine

in flag

All of my services seem to be ok. I was configuring bind to use another domain and the checkconf and checkzone all work. If i do dig @myIP google.com. it replies fine dig google.com gives Sudo: unable to resolve host myhost.mydomain.com temporary failure in name resolution. This is a ubuntu 21.04 dns worked before i broke it.

user10489 avatar
in flag
try `systemd-resolver --flush` although that may be necessary but not sufficent
in flag
Tired sudo systemd-resolver --flush and got:: systemd-resolver: colmando not found sorry editor will not leave colmando alone
in flag
I currently suspect I need to fix 127.0.0.1 dns to my IP. Resolv.conf says nameserver 127.0.0.1. And not my 192.168.... addr.
in flag
Latest... if I change resolvd.conf it says not too... and restart systdmd-resolved then all is well. I suspect a reboot will reset the global dns to 127.0.0.1. So now I will Google that problem
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.