Re: Can't find the DNS Servers
- Date: Wed, 4 Oct 2017 21:13:51 +0300
- From: Reco <recoverym4n@xxxxxxxxx>
- Subject: Re: Can't find the DNS Servers
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 220.127.116.11 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 18.104.22.168 - 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.
> 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.
> 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?