Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #187138 > unrolled thread
| Started by | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| First post | 2017-09-24 03:10 +0200 |
| Last post | 2017-09-26 05:20 +0200 |
| Articles | 20 on this page of 102 — 17 participants |
Back to article view | Back to linux.debian.user
Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-09-24 03:10 +0200
Re: Can't find the DNS Servers Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-09-24 06:40 +0200
Re: Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-09-25 21:50 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-09-26 09:00 +0200
Re: Can't find the DNS Servers Richard Hector <richard@walnut.gen.nz> - 2017-09-27 11:20 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-09-27 18:40 +0200
Re: Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-10-01 22:40 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-02 04:30 +0200
Re: Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-10-02 04:30 +0200
Re: Can't find the DNS Servers Weaver <weaver@riseup.net> - 2017-10-02 04:40 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-02 09:10 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-10-02 12:30 +0200
Re: E-mail headers 101 (was: Can't find the DNS Servers) Reco <recoverym4n@gmail.com> - 2017-10-02 12:40 +0200
Re: E-mail headers 101 (was: Can't find the DNS Servers) Gene Heskett <gheskett@shentel.net> - 2017-10-02 13:00 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-02 23:10 +0200
Re: Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-10-03 22:40 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-04 01:00 +0200
Re: Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-10-04 01:50 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-04 14:40 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-04 19:00 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-04 08:20 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-04 14:30 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-04 14:40 +0200
Re: Can't find the DNS Servers Michael Stone <mstone@debian.org> - 2017-10-04 15:00 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-04 15:30 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-04 19:00 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-04 19:30 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-04 20:40 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-10-05 00:20 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-05 02:30 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-10-05 04:00 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-06 05:00 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-10-06 07:30 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-06 18:00 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-05 15:00 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-06 03:40 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-06 15:10 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-06 18:00 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-04 20:10 +0200
Re: Can't find the DNS Servers Michael Stone <mstone@debian.org> - 2017-10-04 20:10 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-04 20:20 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-04 20:40 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-04 22:00 +0200
Re: Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-10-05 01:00 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-05 08:30 +0200
Re: Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-10-04 22:10 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-04 22:50 +0200
Re: (solved) Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-10-05 19:10 +0200
Re: (solved) Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-05 19:10 +0200
Re: (solved) Can't find the DNS Servers Brian <ad44@cityscape.co.uk> - 2017-10-05 19:40 +0200
Re: (solved) Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-10-05 20:40 +0200
Re: (solved) Can't find the DNS Servers Brian <ad44@cityscape.co.uk> - 2017-10-06 16:10 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-02 23:00 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-10-02 23:40 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-10-03 05:10 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-25 15:00 +0200
Re: Can't find the DNS Servers Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-25 15:20 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-25 15:30 +0200
Re: Can't find the DNS Servers Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-25 15:50 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-25 16:00 +0200
Re: Can't find the DNS Servers Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-25 16:30 +0200
Re: Can't find the DNS Servers Gary Roach <gary719_list1@verizon.net> - 2017-09-30 04:20 +0200
Re: Can't find the DNS Servers Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-30 08:50 +0200
Re: Can't find the DNS Servers Curt <curty@free.fr> - 2017-09-30 14:00 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-25 17:40 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-09-25 18:20 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-25 18:30 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-09-25 18:40 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-25 23:40 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-09-26 20:00 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-26 21:10 +0200
Re: Can't find the DNS Servers Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-25 19:40 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-25 20:00 +0200
Re: Can't find the DNS Servers Reco <recoverym4n@gmail.com> - 2017-09-25 21:00 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-25 21:30 +0200
Re: Can't find the DNS Servers Don Armstrong <don@debian.org> - 2017-09-25 21:30 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-25 21:50 +0200
Re: Can't find the DNS Servers Don Armstrong <don@debian.org> - 2017-09-25 23:20 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-26 15:20 +0200
Re: Can't find the DNS Servers <tomas@tuxteam.de> - 2017-09-26 15:50 +0200
Re: Can't find the DNS Servers Darac Marjal <mailinglist@darac.org.uk> - 2017-09-26 16:10 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-26 17:40 +0200
Re: Can't find the DNS Servers Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-26 16:30 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-26 17:30 +0200
Re: Can't find the DNS Servers Michael Stone <mstone@debian.org> - 2017-09-26 17:40 +0200
Re: Can't find the DNS Servers <tomas@tuxteam.de> - 2017-09-26 17:40 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-26 18:00 +0200
Finding the appropriate manpage [Re: Can't find the DNS Servers] Don Armstrong <don@debian.org> - 2017-09-26 23:20 +0200
Re: Finding the appropriate manpage [Re: Can't find the DNS Servers] Lck Ras <likcoras@riseup.net> - 2017-09-27 16:20 +0200
Re: Finding the appropriate manpage [Re: Can't find the DNS Servers] Curt <curty@free.fr> - 2017-09-27 17:20 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-26 00:50 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-09-26 20:50 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-26 21:10 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-26 21:40 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-26 21:50 +0200
Re: Can't find the DNS Servers Michael Stone <mstone@debian.org> - 2017-09-26 22:10 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-27 05:30 +0200
Re: Can't find the DNS Servers David Wright <deblis@lionunicorn.co.uk> - 2017-09-27 00:50 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-26 21:30 +0200
Re: Can't find the DNS Servers Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-26 21:50 +0200
Re: Can't find the DNS Servers Gene Heskett <gheskett@shentel.net> - 2017-09-27 05:40 +0200
Re: Can't find the DNS Servers Celejar <celejar@gmail.com> - 2017-09-26 05:20 +0200
Page 3 of 6 — ← Prev page 1 2 [3] 4 5 6 Next page →
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-10-04 20:20 +0200 |
| Message-ID | <uwWr0-1f7-5@gated-at.bofh.it> |
| In reply to | #187563 |
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 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? > > Because google doesn't know what names you use on your local network. Once one starts using 8.8.8.8 - 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. > 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. Avahi, anyone? > 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? Reco
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-10-04 20:40 +0200 |
| Message-ID | <uwWKl-1ng-9@gated-at.bofh.it> |
| In reply to | #187564 |
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 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? > > > > Because google doesn't know what names you use on your local network. > > Once one starts using 8.8.8.8 - 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 8.8.8.8 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. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-10-04 22:00 +0200 |
| Message-ID | <uwXZL-258-9@gated-at.bofh.it> |
| In reply to | #187567 |
On Wed, Oct 04, 2017 at 01:30:21PM -0500, David Wright wrote: > 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 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? > > > > > > Because google doesn't know what names you use on your local network. > > > > Once one starts using 8.8.8.8 - 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 8.8.8.8 for the IP address of wasp (that's its > "FQDN") it will reply with 192.168.1.13? No, it should answer NXDOMAIN. But Google will remember that you have a host with this name. It may even advertise you a wasp repellent one day. > > > 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. Other than being a violation of RFC 6762 (and the thing Microsoft suggests) that's probably OK. > > > 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 "apt install qemu-kvm" could not lead to this result. Even with "apt install libvirt-daemon-system" it's impossible. Installing these packages *and* implementing a howto or two from random Internet sites - that's definitely possible. > and (b) still worked for whatever a qemu-kvm is but not for the > actual ?host machine. By default libvirt creates "virbr0" bridge and starts dnsmasq (if it's installed) to serve DNS and DHCP requests coming from "domains" (aka virtual machines). So yes, *some* DNS requests from inside virbr0 should work. Reco
[toc] | [prev] | [next] | [standalone]
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-10-05 01:00 +0200 |
| Message-ID | <ux0NY-40F-7@gated-at.bofh.it> |
| In reply to | #187564 |
On 10/04/2017 11:13 AM, 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 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? >> >> Because google doesn't know what names you use on your local network. > > Once one starts using 8.8.8.8 - 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. > >> 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. > > Avahi, anyone? > >> 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? > > Reco > > Rico, I filled /etc/hosts and can get named service to my local network but can't get on to the internet. It's like something is blocking access to any nameservers. Gary R.
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-10-05 08:30 +0200 |
| Message-ID | <ux7Pr-yE-1@gated-at.bofh.it> |
| In reply to | #187573 |
On Wed, Oct 04, 2017 at 03:57:33PM -0700, Gary Roach wrote: > On 10/04/2017 11:13 AM, 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 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? > > > > > > Because google doesn't know what names you use on your local network. > > > > Once one starts using 8.8.8.8 - 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. > > > > > 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. > > > > Avahi, anyone? > > > > > 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? > > > > Reco > > > > > Rico, > > I filled /etc/hosts and can get named service to my local network but can't > get on to the internet. It's like something is blocking access to any > nameservers. 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
[toc] | [prev] | [next] | [standalone]
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-10-04 22:10 +0200 |
| Message-ID | <uwY9r-2nw-3@gated-at.bofh.it> |
| In reply to | #187562 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-10-04 22:50 +0200 |
| Message-ID | <uwYM9-2Cd-1@gated-at.bofh.it> |
| In reply to | #187569 |
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
[toc] | [prev] | [next] | [standalone]
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-10-05 19:10 +0200 |
| Subject | Re: (solved) Can't find the DNS Servers |
| Message-ID | <uxhON-5Kt-5@gated-at.bofh.it> |
| In reply to | #187570 |
On 10/04/2017 01:44 PM, Reco wrote: > > 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 > > Hooray, Solved. Rico, your question about nsswitch.conf was the key. I printed out the file from another computer and found that the "hosts:" line was missing "dns and mdns4'. I added these to the end of the line and everything now works fine. I can't thank all of you enough for your support. Sincerely Gary R.
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-10-05 19:10 +0200 |
| Subject | Re: (solved) Can't find the DNS Servers |
| Message-ID | <uxhOO-5Kt-21@gated-at.bofh.it> |
| In reply to | #187582 |
Hi. On Thu, Oct 05, 2017 at 10:00:01AM -0700, Gary Roach wrote: > On 10/04/2017 01:44 PM, Reco wrote: > > > > 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 > > > > > Hooray, Solved. > Rico, your question about nsswitch.conf was the key. I printed out the file > from another computer and found that the "hosts:" line was missing "dns and > mdns4'. I added these to the end of the line and everything now works fine. > I can't thank all of you enough for your support. I'm glad it worked out for you. But do not thank only me - the credit for nsswitch.conf goes to Nemeth Gyorgy from [1]. [1] https://lists.debian.org/msgid-search/acf65f96-8e4e-d3d6-0350-6717b940295a@freemail.hu Reco
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-10-05 19:40 +0200 |
| Subject | Re: (solved) Can't find the DNS Servers |
| Message-ID | <uxihQ-60a-17@gated-at.bofh.it> |
| In reply to | #187582 |
On Thu 05 Oct 2017 at 10:00:01 -0700, Gary Roach wrote: > On 10/04/2017 01:44 PM, Reco wrote: > > > >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 > > > > > Hooray, Solved. > Rico, your question about nsswitch.conf was the key. I printed out the file > from another computer and found that the "hosts:" line was missing "dns and > mdns4'. I added these to the end of the line and everything now works fine. > I can't thank all of you enough for your support. I could be wrong but I think you mean "mdns4_minimal [NOTFOUND=return]" was missing. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-10-05 20:40 +0200 |
| Subject | Re: (solved) Can't find the DNS Servers |
| Message-ID | <uxjdU-6Bo-11@gated-at.bofh.it> |
| In reply to | #187586 |
On 10/05/2017 10:30 AM, Brian wrote: > On Thu 05 Oct 2017 at 10:00:01 -0700, Gary Roach wrote: > >> On 10/04/2017 01:44 PM, Reco wrote: >>> >>> 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 >>> >>> >> Hooray, Solved. >> Rico, your question about nsswitch.conf was the key. I printed out the file >> from another computer and found that the "hosts:" line was missing "dns and >> mdns4'. I added these to the end of the line and everything now works fine. >> I can't thank all of you enough for your support. > > I could be wrong but I think you mean "mdns4_minimal [NOTFOUND=return]" > was missing. > No. The particular line reads: "hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4" It works! Didn't mean to slight anyone with the thanks. I know that this was somewhat of a community effort. So thanks to all. Gary R
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-10-06 16:10 +0200 |
| Subject | Re: (solved) Can't find the DNS Servers |
| Message-ID | <uxBua-2vO-3@gated-at.bofh.it> |
| In reply to | #187589 |
On Thu 05 Oct 2017 at 11:38:20 -0700, Gary Roach wrote: > On 10/05/2017 10:30 AM, Brian wrote: > >On Thu 05 Oct 2017 at 10:00:01 -0700, Gary Roach wrote: > > > >>Hooray, Solved. > >>Rico, your question about nsswitch.conf was the key. I printed out the file > >>from another computer and found that the "hosts:" line was missing "dns and > >>mdns4'. I added these to the end of the line and everything now works fine. > >>I can't thank all of you enough for your support. > > > >I could be wrong but I think you mean "mdns4_minimal [NOTFOUND=return]" > >was missing. > > > No. The particular line reads: > "hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4" > It works! So the line went from "hosts: files mdns4_minimal [NOTFOUND=return]" (no dns!) to "hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4", The stock Debian line is "hosts: files mdns4_minimal [NOTFOUND=return] dns" "mdns4" is not on the line because of #433943. Please drop the final "mdns4" from the default nsswitch.conf line. While it is quite useful to enable proper reverse lookups on non-link-local addresses it also has the big drawback that if there is neither avahi nor classic dns set up for an IP address this module has to timeout before the reverse lookup can fail. This becomes a problem because many programs freeze during these lookups, one being ssh on every single incoming connection. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-10-02 23:00 +0200 |
| Message-ID | <uwfYN-zn-53@gated-at.bofh.it> |
| In reply to | #187472 |
On Mon 02 Oct 2017 at 10:00:28 (+0300), Reco wrote: > To bring order to this chaos, you'll need this e/n/i: > > auto enp4s0 > iface enp4s0 inet dhcp > dns-nameserver 8.8.4.4 > dns-nameserver 8.8.8.8 > > Please note the indentation, … which looks tidy, but the indentation carries no meaning (lest people spend time fiddling with it thinking that it does). Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-10-02 23:40 +0200 |
| Message-ID | <uwgBu-18n-69@gated-at.bofh.it> |
| In reply to | #187495 |
Hi. On Mon, Oct 02, 2017 at 11:15:16AM -0500, David Wright wrote: > On Mon 02 Oct 2017 at 10:00:28 (+0300), Reco wrote: > > > To bring order to this chaos, you'll need this e/n/i: > > > > auto enp4s0 > > iface enp4s0 inet dhcp > > dns-nameserver 8.8.4.4 > > dns-nameserver 8.8.8.8 > > > > Please note the indentation, > > … which looks tidy, but the indentation carries no meaning > (lest people spend time fiddling with it thinking that it does). While the indentation is ignored by ifupdown indeed, it carries invaluable meaning to human beings. In this particular case, the meaning is: Both "dns-nameserver" stanzas are applied to enp4s0 interface only, not that other one, and even not the one you want it to apply to. Also, one should promote neatness in configuration files. Otherwise first you put tiny amounts of badly-formatted configuration stanzas, next you're going Slackware by configure/make/make install and *finally* you're trying to parse HTML with regular expressions bringing doom and demise to unsuspecting humankind. Reco
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-10-03 05:10 +0200 |
| Message-ID | <uwlKN-4iE-1@gated-at.bofh.it> |
| In reply to | #187507 |
On Mon 02 Oct 2017 at 21:32:40 (+0300), Reco wrote: > Hi. > > On Mon, Oct 02, 2017 at 11:15:16AM -0500, David Wright wrote: > > On Mon 02 Oct 2017 at 10:00:28 (+0300), Reco wrote: > > > > > To bring order to this chaos, you'll need this e/n/i: > > > > > > auto enp4s0 > > > iface enp4s0 inet dhcp > > > dns-nameserver 8.8.4.4 > > > dns-nameserver 8.8.8.8 > > > > > > Please note the indentation, > > > > … which looks tidy, but the indentation carries no meaning > > (lest people spend time fiddling with it thinking that it does). > > While the indentation is ignored by ifupdown indeed, it carries > invaluable meaning to human beings. > In this particular case, the meaning is: > > Both "dns-nameserver" stanzas are applied to enp4s0 interface only, not > that other one, and even not the one you want it to apply to. … which is precisely the delusion. > Also, one should promote neatness in configuration files. By all means. But this is just as tidy without adding meaningless "meanings": ########## Primary network interface ########## auto enp4s0 iface enp4s0 inet dhcp dns-nameserver 8.8.4.4 dns-nameserver 8.8.8.8 ########## Bridging stuff ##################### [… … …] Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2017-09-25 15:00 +0200 |
| Message-ID | <utB9o-6tv-33@gated-at.bofh.it> |
| In reply to | #187138 |
On Sat, Sep 23, 2017 at 06:03:12PM -0700, Gary Roach wrote: > I have been trying for several day to get firefox to work on a newly > installed Debian Stretch system. It Seems that Firefox can't find a DNS > server. I am having the same problem with apt-get update. None of my mirrors > can be reached. ls -ld /etc/resolv.conf cat /etc/resolv.conf dpkg -l resolvconf network-manager grep ^hosts: /etc/nsswitch.conf > Ping works just fine. pinging what? > I can't even reach the other computers > on my home network if I use their names. IP addresses work OK. LAN configuration can be done in several ways. For most small home LANs, you probably just want to put the IPs and hostnames in /etc/hosts on each machine. For larger or fancier setups, you can configure a private DNS server. > I have > installed resolvconf *shudder* I mean, unless this is a laptop or a tablet or a phone or something. Then it may be appropriate, because you might actually WANT your resolv.conf file to be rewritten every time the wind changes direction. For desktop machines with a static internal network configuration, it's an abomination. And unfortunately it's not the only malevolent fiend trying to usurp control of your resolv.conf file. There's also dhclient, and network-manager, and systemd-resolved, and who knows what else. See <https://www.cyberciti.biz/faq/dhclient-etcresolvconf-hooks/> for some of your options. Of course, before you can apply any of those suggestions, you have to seize back control of your resolv.conf file in the first place. Make sure it's a FILE and not a symlink, and put the correct content into it. Make sure name resolution works. Then choose your favorite solution to keep the file under YOUR control.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-09-25 15:20 +0200 |
| Message-ID | <utBsK-6S0-11@gated-at.bofh.it> |
| In reply to | #187175 |
Le 25/09/2017 à 14:56, Greg Wooledge a écrit : > On Sat, Sep 23, 2017 at 06:03:12PM -0700, Gary Roach wrote: > >> I have installed resolvconf > > *shudder* > > I mean, unless this is a laptop or a tablet or a phone or something. > Then it may be appropriate, because you might actually WANT your > resolv.conf file to be rewritten every time the wind changes direction. resolvconf does not do this. Besides, resolvconf is required for the dns-nameservers option in /etc/network/interfaces to have any effect with static configuration. Don't you think it is better to have all the IP parameters (IP address, mask, gateway, DNS) in a single config file ? > For desktop machines with a static internal network configuration, it's > an abomination. And unfortunately it's not the only malevolent fiend > trying to usurp control of your resolv.conf file. There's also dhclient, > and network-manager, and systemd-resolved, and who knows what else. resolvconf is designed to prevent these pieces of software to write directly in resolv.conf, giving you better control. Without resolvconf, all of them wildy rewrite resolv.conf without taking the others into account.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2017-09-25 15:30 +0200 |
| Message-ID | <utBCq-6Vt-15@gated-at.bofh.it> |
| In reply to | #187177 |
On Mon, Sep 25, 2017 at 03:14:02PM +0200, Pascal Hambourg wrote: > Besides, resolvconf is required for the dns-nameservers option in > /etc/network/interfaces to have any effect with static configuration. Don't > you think it is better to have all the IP parameters (IP address, mask, > gateway, DNS) in a single config file ? No. I think it's better for all the unix-like systems to work the same way (the way that they have all done for the last 30+ years), rather than each one doing something different. Sadly, there was never any uniformity in how interfaces, IPs, netmasks and routes are configured. So, we just have to live with every system being different for that stuff. But /etc/resolv.conf is a universal standard. You can log into ANY unix-like system and see what nameservers it's using, and correct them if they're wrong (though you may need to remove the chattr +i bit before you can write to the file).
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-09-25 15:50 +0200 |
| Message-ID | <utBVL-735-1@gated-at.bofh.it> |
| In reply to | #187179 |
Le 25/09/2017 à 15:24, Greg Wooledge a écrit : > > I think it's better for all the unix-like systems to work the same way > (the way that they have all done for the last 30+ years), rather than > each one doing something different. > > Sadly, there was never any uniformity in how interfaces, IPs, netmasks > and routes are configured. These two statements contradict each other. If there was never any uniformity, then Unix-like systems have not worked the same way for the 30+ years. > But /etc/resolv.conf is a universal standard. You can log into ANY > unix-like system and see what nameservers it's using Yes. But I do not think that the Unix standard defines the way the file should be created and modified. > and correct them if they're wrong Prepare to be disappointed if you modify directly resolv.conf, because the software which wrote it first could rewrite it after you, as DHCP clients do each time they renew the lease. > (though you may need to remove the chattr +i bit before > you can write to the file). Ugly hack. Some software modify the DNS server list. IMO, better bear with it and learn how to control them.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2017-09-25 16:00 +0200 |
| Message-ID | <utC5r-76I-5@gated-at.bofh.it> |
| In reply to | #187180 |
On Mon, Sep 25, 2017 at 03:45:06PM +0200, Pascal Hambourg wrote: > Prepare to be disappointed if you modify directly resolv.conf, because the > software which wrote it first could rewrite it after you, as DHCP clients do > each time they renew the lease. In a battle between me and stupid new software programs, I always win in the end. I will do whatever it takes to make the software behave correctly, even if what it takes is REMOVING the software.
[toc] | [prev] | [next] | [standalone]
Page 3 of 6 — ← Prev page 1 2 [3] 4 5 6 Next page →
Back to top | Article view | linux.debian.user
csiph-web