-
Connman and DNS
2017-03-09 "I’ve been running Connman instead of NetworkManager for a week since it is supposed to be more lightweight. Lightweight is good.
However, I had really weird problems with DNS, where some hosts wouldn’t resolve.
$ ping outlook.office365.com PING outlook.office365.com (40.101.40.226) 56(84) bytes of data. 64 bytes from 40.101.40.226 (40.101.40.226): icmp_seq=1 ttl=238 time=44.7 ms 64 bytes from 40.101.40.226 (40.101.40.226): icmp_seq=2 ttl=238 time=44.6 ms 64 bytes from 40.101.40.226 (40.101.40.226): icmp_seq=3 ttl=238 time=44.8 ms ^C --- outlook.office365.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 44.625/44.755/44.890/0.267 ms $ ping smtp.office365.com ping: smtp.office365.com: Temporary failure in name resolutionWe use Outlook 365 at work, please don’t judge me.
"