Web lists-archives.com

Re: Can't find the DNS Servers




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.

But won't that send local host lookups to google which won't have a clue?

Why won't it have a clue?

"Four eights" is a huge pool of public resolvers. "Free" to use (in a
Google sense of a word).

An unnamed consumer-grade router will happily pass DNS requests to
anywhere. Unless it's been tinkered with, which is outside of scope of
this problem.

ISP, of course can:

1) Pass DNS request along, as good ISP should.

2) Route DNS queries to *their* DNS servers. Whenever IPS is abided by
law to do so or merely tries to hijack NXDOMAIN answers to raise some
profit is hardly relevant to the issue.

3) Block DNS requests unless it is going to *their* DNS. Best thing that
can be done about this kind of ISP is contract termination.

Reco


I made the changes to dhclient you suggested. There was no change in the problem. Attached is the new version of dhclient.

Next?

Gary R
# Configuration file for /sbin/dhclient.
#
# This is a sample configuration file for dhclient. See dhclient.conf's
#	man page for more information about the syntax of this file
#	and a more comprehensive list of the parameters understood by
#	dhclient.
#
# Normally, if the DHCP server provides reasonable information and does
#	not leave anything out (like the domain name, for example), then
#	few changes must be made to this file, if any.
#

option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;

send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset, routers,
	domain-name,
	dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
	netbios-name-servers, netbios-scope, interface-mtu,
	rfc3442-classless-static-routes, ntp-servers;

#send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;
#require subnet-mask, domain-name-servers;
#timeout 60;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/sbin/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;

#alias {
#  interface "eth0";
#  fixed-address 192.5.5.213;
#  option subnet-mask 255.255.255.255;
#}

#lease {
#  interface "eth0";
#  fixed-address 192.33.137.200;
#  medium "link0 link1";
#  option host-name "andare.swiftmedia.com";
#  option subnet-mask 255.255.255.0;
#  option broadcast-address 192.33.137.255;
#  option routers 192.33.137.250;
#  option domain-name-servers 127.0.0.1;
#  renew 2 2000/1/12 00:00:01;
#  rebind 2 2000/1/12 00:00:01;
#  expire 2 2000/1/12 00:00:01;
#}