Otherwise said, glibc and libresolver don't respect if you are running a `resolv.conf` with `nameserver 127.0.1.1`.
If one of `eth0`, `wlan0` are online "up", it's no problem for the resolver to get name `github.com` into `A 192.30.252.130`.
But if all of `eth0`, `wlan0` are offline "down", the resolver doesn't even try to ask `127.0.0.3` for to lookup `github.com`. It just assumes NX.
So to say, if I don't have a connection, you can't access `github.com`.
But what if I'm going to lookup for `my.service.local`, or `my.service.localhost`?
If I do not have ANY connection, there IS a connection to localhost 127/8!
So to say, you MUST remove the restriction, that a service running on localhost 127/8 can't be accessed, just because you (eth0, wlan0) are offline "down"; even if you (lo) should always be online "up".
Otherwise said, glibc and libresolver don't respect if you are running a `resolv.conf` with `nameserver 127.0.1.1`.
If one of `eth0`, `wlan0` are online "up", it's no problem for the resolver to get name `github.com` into `A 192.30.252.130`.
But if all of `eth0`, `wlan0` are offline "down", the resolver doesn't even try to ask `127.0.0.3` for to lookup `github.com`. It just assumes NX.
So to say, if I don't have a connection, you can't access `github.com`.
But what if I'm going to lookup for `my.service.local`, or `my.service. localhost` ?
If I do not have ANY connection, there IS a connection to localhost 127/8!
So to say, you MUST remove the restriction, that a service running on localhost 127/8 can't be accessed, just because you (eth0, wlan0) are offline "down"; even if you (lo) should always be online "up".