Hi. On Wed, Oct 04, 2017 at 12:54:46PM -0700, Gary Roach wrote: > On 10/04/2017 10:59 AM, Reco wrote: > > Hi. > > > > 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: > > > > Hi. > > > > > > > > On Tue, Oct 03, 2017 at 01:30:11PM -0700, Gary Roach wrote: > > > > > OK Rico> I followed your instructions and still have the same problem. > > > > > Attached are the new files. Already installed were isc-dhcp-client and > > > > > resolvconf. You are right about the br1 entry not being needed. the > > > > > virtual > > > > > machine works fine without it. > > > > > > > > So, what we have now is a definite improvement over the last time, but > > > > some twists are needed. > > > > > > > > While "dns-nameserver" stanzas are working now, your DHCP server also > > > > advertises its own: > > > > > > > > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > > > > > resolvconf(8) > > > > > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE > > > > > OVERWRITTEN > > > > > nameserver 192.168.1.1 > > > > > nameserver 8.8.8.8 > > > > > nameserver 8.8.4.4 > > > > > > > > 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 8.8.8.8 as > > > > forwarder DNS. > > > > Since it's unnaturally complex to do so in a consumer-grade routers, a > > > > hack is in order. > I made the changes to dhclient you suggested. There was no change in the > problem. Attached is the new version of dhclient. > > Next?
The contents of /etc/nsswitch.conf, please. The current contents of /etc/resolv.conf. The output of (terminate it with Ctrl+C after 60 seconds): tcpdump -nvi any udp port 53 or tcp port 53 or udp port 5353 While doing: getent hosts go.dev Reco
