Re: Can't find the DNS Servers
On Wed 04 Oct 2017 at 21:13:51 (+0300), Reco wrote:
> On Wed, Oct 04, 2017 at 02:08:17PM -0400, Michael Stone wrote:
> > On Wed, Oct 04, 2017 at 08:59:46PM +0300, Reco wrote:
> > > On Wed, Oct 04, 2017 at 11:59:04AM -0500, David Wright wrote:
> > > > On Wed 04 Oct 2017 at 09:11:37 (+0300), Reco wrote:
> > > > > A correct way to fix this is to "persuade" your DHCP server not to
> > > > > provide DNS information.
> > > > > Even more correct way is to force your DNS-at-DHCP to use 188.8.131.52 as
> > > > > forwarder DNS.
> > > > > Since it's unnaturally complex to do so in a consumer-grade routers, a
> > > > > hack is in order.
> > > >
> > > > But won't that send local host lookups to google which won't have a clue?
> > >
> > > Why won't it have a clue?
> > Because google doesn't know what names you use on your local network.
> Once one starts using 184.108.40.206 - it will. Even it won't show it.
> Friends don't let friends use Google resolvers.
> A software that's using "Four Eights" by default was considered buggy in
> Debian back in the day.
Can I just check that we're talking about the same thing? Are you
saying that if I ask 220.127.116.11 for the IP address of wasp (that's its
"FQDN") it will reply with 192.168.1.13?
> > To
> > implement local lookups you need a name server which can selectively either
> > serve a local name or forward the request to an internet name server.
Just to be clear, I'm using "local" in the everyday meaning, not in
the sense of .local in whichever RFC it is.
> > That
> > can't be done in resolv.conf, but can be done either centrally or locally
> > via unbound or similar.
> Or, /etc/hosts. For a simple household network how hard could it be?
I was under the impression that the OP had a DNS-serving router which
could perform that job successfully (a) before setting up qemu-kvm
and (b) still worked for whatever a qemu-kvm is but not for the
actual ?host machine.