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 1 of 6 [1] 2 3 4 5 6 Next page →
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-09-24 03:10 +0200 |
| Subject | Can't find the DNS Servers |
| Message-ID | <ut3AJ-2af-3@gated-at.bofh.it> |
Hi all. 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. Ping works just fine. I can't even reach the other computers on my home network if I use their names. IP addresses work OK. I have installed resolvconf and followed several installation instructions to no avail. The name servers for my router (192.168.1.1)and both google servers at 8.8.8.8 and 8.8.4.4. are listed in the correct file (can't remember which one). This system worked fine when first installed. I installed qemu-kvm on the system and I think in broke things.I've run out of ideas. Please help Gary R.
[toc] | [next] | [standalone]
| From | Cindy-Sue Causey <butterflybytes@gmail.com> |
|---|---|
| Date | 2017-09-24 06:40 +0200 |
| Message-ID | <ut6RX-483-3@gated-at.bofh.it> |
| In reply to | #187138 |
On 9/23/17, Gary Roach <gary719_list1@verizon.net> wrote: > Hi all. > 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. Ping works just fine. I can't even reach the > other computers on my home network if I use their names. IP addresses > work OK. I have installed resolvconf and followed several installation > instructions to no avail. The name servers for my router > (192.168.1.1)and both google servers at 8.8.8.8 and 8.8.4.4. are listed > in the correct file (can't remember which one). This system worked fine > when first installed. I installed qemu-kvm on the system and I think in > broke things.I've run out of ideas. > > Please help Hi, Gary, I absolutely feel your pain. I've been locked out most of the entire past week. Could mostly only access ~400 to 900 BITES per second download once in a little while. After some nosing around, I've initially stumbled upon a quick fix that will help you at least upgrade right now. This came about k/t an Ubuntu issue [0]. Yes, I know you're saying you can't access something like that right now so this is posted in hopes someone can further translate that into appropriate IP addresses (unless you're accessing from another computer and can do that yourself, that is). In the process of learning from that issue over there, this came up: https://wiki.debian.org/SourcesList#Name_Resolution VERY cool. It says you can temporarily change your /etc/apt/sources.list by personalizing the following *example*/*template*: echo "deb http://128.30.2.26/debian testing main contrib" > /etc/apt/sources.list You simply tweak that to match one's own favored release (e.g. jessie, stretch, buster, etc) such as it already exists within /etc/apt/sources.list. That is SO cool because the tip I learned from Ubuntu was about tweaking your /etc/hosts. I like tweaking sources.list much better. I think I like it mostly because it's something more familiar than other files. Afterthought is that, because you're only swapping out a domain name for an IP address (and not touching ANYTHING ELSE), hopefully that should just keep right on moving from where you left off last time. If it was me doing this, I would make sure I had a safe backup copy of sources.list to put back in place when things were solved. :) So now we hopefully have you upgrading.. Oh, and yes, I know.. there are all kinds of the fancy commands the rest of everyone uses to debug this type of topic. That right there above is *so* easy to test drive and is surely a new toy for someone besides me (too). I even tested http://128.30.2.26/debian/ = IT WORKS as expected!!! If it then still doesn't work after upgrading, you can do the tip from the Ubuntu page where you pick and add appropriate /etc/hosts lines as you need them. But you need the IP addresses. I've almost figured that out but not quite. As it turns out, we might have the power to get those right from our terminals. I'm not sure if it would work for you, Gary, due to your issues, but it's a quick install to test and see. Via Google, I learned about "nslookup". "apt-cache search nslookup" landed the "dnsutils" package (285kb for me). Once installed, you type in "nslookup" (as a normal user) and hit Enter. Then you type in the domain name that needs an IP equivalent. You'll receive back something like this: > deb.debian.org Server: 192.168.0.1 Address: 192.168.0.1#53 Non-authoritative answer: deb.debian.org canonical name = static.debian.org. Name: static.debian.org Address: 130.89.148.14 Name: static.debian.org Address: 149.20.4.15 Name: static.debian.org Address: 5.153.231.4 Name: static.debian.org Address: 128.31.0.62 That didn't match what Debian Wiki provided so I next tested "dig" which is also included in dnsutils. I'm not sure how to implement that one so I'm going to send this off now. Maybe someone else is versed in "dig" and can help decode its flags, etc. It looks far more powerful than nslookup.. :) Or maybe they know an even more productive tool with possibly easier to remember flags. :) Originally it had come to mind that there's always the option of sharing files like these to check for formation and typos: /etc/network/interfaces /etc/hosts (before potential tweaking) /etc/resolv.conf Those interfaces and hosts files are places I have to touch on and sometimes fill in some things for during each new debootstrap. That tells me they're places where things can get messed up. That /etc/resolv.conf always resolves itself for me, yayhoo, but maybe something's not quite ok in yours. I'm saying that because my notes are showing one thing, and now my own /etc/resolv.conf has apparently populated itself with an additional line these days. Beyond that, I'm pretty much... speechless. :) Cindy :) [0] https://askubuntu.com/questions/928144/no-internet-access-lubuntu-17-04-eeepc-1001pxd/936972#936972 -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with Geraldine Laverne's goldfish food *
[toc] | [prev] | [next] | [standalone]
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-09-25 21:50 +0200 |
| Message-ID | <utHya-2oD-11@gated-at.bofh.it> |
| In reply to | #187145 |
On 09/23/2017 09:31 PM, Cindy-Sue Causey wrote: > On 9/23/17, Gary Roach <gary719_list1@verizon.net> wrote: >> Hi all. >> 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. Ping works just fine. I can't even reach the >> other computers on my home network if I use their names. IP addresses >> work OK. I have installed resolvconf and followed several installation >> instructions to no avail. The name servers for my router >> (192.168.1.1)and both google servers at 8.8.8.8 and 8.8.4.4. are listed >> in the correct file (can't remember which one). This system worked fine >> when first installed. I installed qemu-kvm on the system and I think in >> broke things.I've run out of ideas. >> >> Please help > An addition is necessary here. The problem started when I installed the qemu-kvm virtual machine. Now the Kubuntu system - the guest - network access works fine. But the host machine can't find the DNS servers. This makes no sense. Gary R
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-09-26 09:00 +0200 |
| Message-ID | <utS0y-18O-13@gated-at.bofh.it> |
| In reply to | #187209 |
Hi. On Mon, Sep 25, 2017 at 12:49:22PM -0700, Gary Roach wrote: > On 09/23/2017 09:31 PM, Cindy-Sue Causey wrote: > > On 9/23/17, Gary Roach <gary719_list1@verizon.net> wrote: > > > Hi all. > > > 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. Ping works just fine. I can't even reach the > > > other computers on my home network if I use their names. IP addresses > > > work OK. I have installed resolvconf and followed several installation > > > instructions to no avail. The name servers for my router > > > (192.168.1.1)and both google servers at 8.8.8.8 and 8.8.4.4. are listed > > > in the correct file (can't remember which one). This system worked fine > > > when first installed. I installed qemu-kvm on the system and I think in > > > broke things.I've run out of ideas. > > > > > > Please help > > > An addition is necessary here. The problem started when I installed the > qemu-kvm virtual machine. Now the Kubuntu system - the guest - network > access works fine. But the host machine can't find the DNS servers. This > makes no sense. And it never make any sense unless you troubleshoot it. Please post these things from the problematic PC: ip a l ip ro l cat /etc/resolv.conf "tcpdump -nvi any udp port 53 or tcp port 53" run while doing "getent hosts www.google.com" Reco
[toc] | [prev] | [next] | [standalone]
| From | Richard Hector <richard@walnut.gen.nz> |
|---|---|
| Date | 2017-09-27 11:20 +0200 |
| Message-ID | <uugFA-nX-3@gated-at.bofh.it> |
| In reply to | #187225 |
[Multipart message — attachments visible in raw view] — view raw
On 26/09/17 19:50, Reco wrote: > Please post these things from the problematic PC: > > ip a l > > ip ro l Can I make a request? When giving example commands, can you give them in full, rather than abbreviated? I believe 'a' and 'ro' are 'address' and 'route' respectively, but 'l' is a bit harder to find - not in the result of "ip address help", anyway. 'list' perhaps? Which I think is the default anyway? I believe anyone who knows the short versions will know the long ones, and those who don't won't have to go digging up the manpages to understand what's going on :-) Cheers, Richard
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-09-27 18:40 +0200 |
| Message-ID | <uunxo-5yo-3@gated-at.bofh.it> |
| In reply to | #187298 |
On Wed, Sep 27, 2017 at 10:16:20PM +1300, Richard Hector wrote: > On 26/09/17 19:50, Reco wrote: > > Please post these things from the problematic PC: > > > > ip a l > > > > ip ro l > > Can I make a request? When giving example commands, can you give them in > full, rather than abbreviated? Sure, ip address list ip route list > I believe 'a' and 'ro' are 'address' and 'route' respectively, Yep. > but 'l' > is a bit harder to find - not in the result of "ip address help", > anyway. 'list' perhaps? Which I think is the default anyway? It's 'list' indeed. 'ip a l' is a personal habit. > I believe anyone who knows the short versions will know the long ones, > and those who don't won't have to go digging up the manpages to > understand what's going on :-) I've requested these commands as I suspect that current IPv4 routing of that host prevents it to talk to configured DNSes. Of course, it might as well be: 1) Misconfigured 'nat' netfilter table (libvirt can do some strange things in this regard for instance). 2) Misconfigured 'filter' netfilter table (iptables are teh hard sometimes). 3) Misconfigured 'mangle' netfilter table (forced UDP checksumming for no good reason). 4) Misconfigured IPv6. 5) All those martian green men that wish evil to us all. But in cases like this I like to search for simple explanation first, and proceed to complex ones after. PS I agree that iproute's manpages have a great improvement potential. Speaking lightly ☺. Reco
[toc] | [prev] | [next] | [standalone]
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-10-01 22:40 +0200 |
| Message-ID | <uvTbP-6Ge-3@gated-at.bofh.it> |
| In reply to | #187323 |
[Multipart message — attachments visible in raw view] — view raw
On 09/27/2017 09:31 AM, Reco wrote: > On Wed, Sep 27, 2017 at 10:16:20PM +1300, Richard Hector wrote: >> On 26/09/17 19:50, Reco wrote: >>> Please post these things from the problematic PC: >>> >>> ip a l >>> >>> ip ro l >> >> Can I make a request? When giving example commands, can you give them in >> full, rather than abbreviated? > > Sure, > > ip address list > > ip route list > > >> I believe 'a' and 'ro' are 'address' and 'route' respectively, > > Yep. > >> but 'l' >> is a bit harder to find - not in the result of "ip address help", >> anyway. 'list' perhaps? Which I think is the default anyway? > > It's 'list' indeed. 'ip a l' is a personal habit. > > >> I believe anyone who knows the short versions will know the long ones, >> and those who don't won't have to go digging up the manpages to >> understand what's going on :-) > > I've requested these commands as I suspect that current IPv4 routing of > that host prevents it to talk to configured DNSes. > > Of course, it might as well be: > > 1) Misconfigured 'nat' netfilter table (libvirt can do some strange > things in this regard for instance). > > 2) Misconfigured 'filter' netfilter table (iptables are teh hard > sometimes). > > 3) Misconfigured 'mangle' netfilter table (forced UDP checksumming for > no good reason). > > 4) Misconfigured IPv6. > > 5) All those martian green men that wish evil to us all. > > But in cases like this I like to search for simple explanation first, > and proceed to complex ones after. > > > PS I agree that iproute's manpages have a great improvement potential. > Speaking lightly ☺. > > Reco > > OK, I've been remiss in getting you the information requested. I think what you need is in the attachments. Nowhere have I found reference to 8.8.8.8 and 8.8.4.4 name servers. I have tried serveral different ways to get them into the resolv.conf files and have failed. Gary R.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-10-02 04:30 +0200 |
| Message-ID | <uvYEx-1Cq-5@gated-at.bofh.it> |
| In reply to | #187463 |
On Sun 01 Oct 2017 at 13:36:28 (-0700), Gary Roach wrote: > OK, I've been remiss in getting you the information requested. I > think what you need is in the attachments. Nowhere have I found > reference to 8.8.8.8 and 8.8.4.4 name servers. I have tried serveral > different ways to get them into the resolv.conf files and have > failed. > > Gary R. > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > > ## The loopback network interface > auto lo > iface lo inet loopback > > ##The primary network interface > allow-hotplug eth0 > iface eth0 inet dhcp > > > ##The bridge network interface to qemu virtual machine > #auto br1 > iface br1 inet dhcp > bridge_ports br1 > bridge_stp off > bridge_fd 0.0 > > dns-nameserver 8.8.8.8 > dns-nameserver 8.8.4.4 > > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > > ## The loopback network interface > auto lo > iface lo inet loopback > > ##The primary network interface > allow-hotplug eth0 > iface eth0 inet dhcp > > > ##The bridge network interface to qemu virtual machine > #auto br1 > iface br1 inet dhcp > bridge_ports br1 > bridge_stp off > bridge_fd 0.0 > > dns-nameserver 8.8.8.8 > dns-nameserver 8.8.4.4 > Disclaimer: I know nothing about bridging, sorry. Why doesn't this file have: ## The loopback network interface auto lo iface lo inet loopback ##The primary network interface allow-hotplug eth0 iface eth0 inet dhcp dns-nameserver 8.8.8.8 ← in the eth0 interface stanza dns-nameserver 8.8.4.4 ← ditto ##The bridge network interface to qemu virtual machine #auto br1 iface br1 inet dhcp bridge_ports br1 bridge_stp off bridge_fd 0.0 ## … and then nameserver lines if bridging requires them. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-10-02 04:30 +0200 |
| Message-ID | <uvYEx-1Cq-3@gated-at.bofh.it> |
| In reply to | #187323 |
[Multipart message — attachments visible in raw view] — view raw
On 09/27/2017 09:31 AM, Reco wrote: > On Wed, Sep 27, 2017 at 10:16:20PM +1300, Richard Hector wrote: >> On 26/09/17 19:50, Reco wrote: >>> Please post these things from the problematic PC: >>> >>> ip a l >>> >>> ip ro l >> >> Can I make a request? When giving example commands, can you give them in >> full, rather than abbreviated? > > Sure, > > ip address list > > ip route list > > >> I believe 'a' and 'ro' are 'address' and 'route' respectively, > > Yep. > >> but 'l' >> is a bit harder to find - not in the result of "ip address help", >> anyway. 'list' perhaps? Which I think is the default anyway? > > It's 'list' indeed. 'ip a l' is a personal habit. > > >> I believe anyone who knows the short versions will know the long ones, >> and those who don't won't have to go digging up the manpages to >> understand what's going on :-) > > I've requested these commands as I suspect that current IPv4 routing of > that host prevents it to talk to configured DNSes. > > Of course, it might as well be: > > 1) Misconfigured 'nat' netfilter table (libvirt can do some strange > things in this regard for instance). > > 2) Misconfigured 'filter' netfilter table (iptables are teh hard > sometimes). > > 3) Misconfigured 'mangle' netfilter table (forced UDP checksumming for > no good reason). > > 4) Misconfigured IPv6. > > 5) All those martian green men that wish evil to us all. > > But in cases like this I like to search for simple explanation first, > and proceed to complex ones after. > > > PS I agree that iproute's manpages have a great improvement potential. > Speaking lightly ☺. > > Reco > > This is the second time I've tried to send this. The first one just disappeared to the bit bucket I assume. So lets try again. Sorry about the delay in replying to your request. Attached is the information you requested. I could not find nameservers 8.8.8.8 and 8.8.4.4 listed anywhere. This is probably the root of my problem. I tried every thing I could think of but couldn't get them to stick in resolv.conf. Gary R.
[toc] | [prev] | [next] | [standalone]
| From | Weaver <weaver@riseup.net> |
|---|---|
| Date | 2017-10-02 04:40 +0200 |
| Message-ID | <uvYOe-1FS-33@gated-at.bofh.it> |
| In reply to | #187466 |
On 2017-10-02 12:26, Gary Roach wrote: > On 09/27/2017 09:31 AM, Reco wrote: >> On Wed, Sep 27, 2017 at 10:16:20PM +1300, Richard Hector wrote: >>> On 26/09/17 19:50, Reco wrote: >>>> Please post these things from the problematic PC: >>>> >>>> ip a l >>>> >>>> ip ro l >>> >>> Can I make a request? When giving example commands, can you give them in >>> full, rather than abbreviated? >> >> Sure, >> >> ip address list >> >> ip route list >> >> >>> I believe 'a' and 'ro' are 'address' and 'route' respectively, >> >> Yep. >> >>> but 'l' >>> is a bit harder to find - not in the result of "ip address help", >>> anyway. 'list' perhaps? Which I think is the default anyway? >> >> It's 'list' indeed. 'ip a l' is a personal habit. >> >> >>> I believe anyone who knows the short versions will know the long ones, >>> and those who don't won't have to go digging up the manpages to >>> understand what's going on :-) >> >> I've requested these commands as I suspect that current IPv4 routing of >> that host prevents it to talk to configured DNSes. >> >> Of course, it might as well be: >> >> 1) Misconfigured 'nat' netfilter table (libvirt can do some strange >> things in this regard for instance). >> >> 2) Misconfigured 'filter' netfilter table (iptables are teh hard >> sometimes). >> >> 3) Misconfigured 'mangle' netfilter table (forced UDP checksumming for >> no good reason). >> >> 4) Misconfigured IPv6. >> >> 5) All those martian green men that wish evil to us all. >> >> But in cases like this I like to search for simple explanation first, >> and proceed to complex ones after. >> >> >> PS I agree that iproute's manpages have a great improvement potential. >> Speaking lightly ☺. >> >> Reco >> >> > This is the second time I've tried to send this. The first one just > disappeared to the bit bucket I assume. So lets try again. > Sorry about the delay in replying to your request. Attached is the > information you requested. I could not find nameservers 8.8.8.8 and > 8.8.4.4 listed anywhere. This is probably the root of my problem. I > tried every thing I could think of but couldn't get them to stick in > resolv.conf. I received it the first time, for reference. -- "It is the duty of the patriot to protect his country from its government." -- Thomas Paine Registered Linux User: 554515
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-10-02 09:10 +0200 |
| Message-ID | <uw31v-4jS-3@gated-at.bofh.it> |
| In reply to | #187466 |
Hi. On Sun, Oct 01, 2017 at 07:26:30PM -0700, Gary Roach wrote: > This is the second time I've tried to send this. The first one just > disappeared to the bit bucket I assume. So lets try again. It did not. Everyone on the list got it, I believe. > Sorry about the delay in replying to your request. Attached is the > information you requested. I could not find nameservers 8.8.8.8 and 8.8.4.4 > listed anywhere. This is probably the root of my problem. No, your problem is different. > I tried every > thing I could think of but couldn't get them to stick in resolv.conf. So, let's get this party started. First, you have "eth0" defined in your /etc/network/interfaces. A simple DHCP configuration that *can*, but *does not* honor your "dns-nameserver" stanzas. The reason being - you put them *after* br1 interface. Second, you have "br1" bridge that: 1) Tries to bridge itself. Nothing good will ever come out of this. 2) Does not try to bridge eth0. I don't know, it may be intended. 3) Does not have *auto* keyword defined, so this bridge does not come into play. Third, and that's no wonder, you have so-called Predictable NIC Names configured, so your *actual* interface is called enp4s0, not eth0. Therefore e/n/i does not apply to it, something else was used to configure it. Fourth, you have your virbr0 interface presumably configured by libvirt. Which means that it's configured at /etc/libvirt/qemu/networks/default.xml or maybe some other file at /etc/libvirt/qemu/networks. Routing table does not contain anything unusual, as does /etc/resolv.conf. 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, and that I deliberately omitted "br1". You don't need it anyway, you have libvirt to take care of bridging. What you also need is: 1) resolvconf package. dns-nameserver stanzas are ignored unless you install it. 2) Any kind of dhcp client. A stock isc-dhcp-client should do it. 3) Deinstalling (disabling) whatever you're using now to configure enp4s0 now. 4) libvirt-doc package. After you restore your primary network connectivity, please point your browser to /usr/share/doc/libvirt-doc/formatnetwork.html . Reco
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-02 12:30 +0200 |
| Message-ID | <uw694-66R-15@gated-at.bofh.it> |
| In reply to | #187472 |
On Monday 02 October 2017 03:00:28 Reco wrote: > Hi. > > On Sun, Oct 01, 2017 at 07:26:30PM -0700, Gary Roach wrote: > > This is the second time I've tried to send this. The first one just > > disappeared to the bit bucket I assume. So lets try again. > > It did not. Everyone on the list got it, I believe. > You are using gmail. To gmail, the echo from the list is a duplicate, and deleted. Just one of the reasons I left gmail. [...] Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2017-10-02 12:40 +0200 |
| Subject | Re: E-mail headers 101 (was: Can't find the DNS Servers) |
| Message-ID | <uw6iN-6a9-39@gated-at.bofh.it> |
| In reply to | #187479 |
On Mon, Oct 02, 2017 at 06:26:08AM -0400, Gene Heskett wrote: > On Monday 02 October 2017 03:00:28 Reco wrote: > > > Hi. > > > > On Sun, Oct 01, 2017 at 07:26:30PM -0700, Gary Roach wrote: > > > This is the second time I've tried to send this. The first one just > > > disappeared to the bit bucket I assume. So lets try again. > > > > It did not. Everyone on the list got it, I believe. > > > You are using gmail. To gmail, the echo from the list is a duplicate, and > deleted. Just one of the reasons I left gmail. You misunderstood me. I meant that Gary Roach sent two different e-mails recently to this maillist. Both e-mails have similar contents. The one was replying to has this header: Message-ID: <feaf8cc0-b6ad-d07d-f0ab-14f7b431f893@verizon.net> The one I saw but choose not to reply has this header: Message-ID: <40d6cb1d-3867-1643-fbf6-49be4e1dacc3@verizon.net> Whatever evil sorcery GMail does with mails has nothing to do with this. Reco
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-02 13:00 +0200 |
| Subject | Re: E-mail headers 101 (was: Can't find the DNS Servers) |
| Message-ID | <uw6C5-6hb-13@gated-at.bofh.it> |
| In reply to | #187481 |
On Monday 02 October 2017 06:39:00 Reco wrote: > On Mon, Oct 02, 2017 at 06:26:08AM -0400, Gene Heskett wrote: > > On Monday 02 October 2017 03:00:28 Reco wrote: > > > Hi. > > > > > > On Sun, Oct 01, 2017 at 07:26:30PM -0700, Gary Roach wrote: > > > > This is the second time I've tried to send this. The first one > > > > just disappeared to the bit bucket I assume. So lets try again. > > > > > > It did not. Everyone on the list got it, I believe. > > > > You are using gmail. To gmail, the echo from the list is a > > duplicate, and deleted. Just one of the reasons I left gmail. > > You misunderstood me. > I meant that Gary Roach sent two different e-mails recently to this > maillist. > Both e-mails have similar contents. > The one was replying to has this header: > > Message-ID: <feaf8cc0-b6ad-d07d-f0ab-14f7b431f893@verizon.net> > > The one I saw but choose not to reply has this header: > > Message-ID: <40d6cb1d-3867-1643-fbf6-49be4e1dacc3@verizon.net> > > Whatever evil sorcery GMail does with mails has nothing to do with > this. > > Reco I believe that "evil sorcery" is an accurate description. I had, several years ago now, a lengthy discussion regarding that over the LL with googles tech support. They were adamant that it was not open for discussion. So I moved my list subscriptions, but left fetchmails access active, and still used it for PM's. A month or so later fetchmails logins became invalid intermittently, then permanently. Since I wasn't of a mind to waste another quarter argueing with a stone wall, I commented that poll stanza out of my .fetchmailrc. Shrug. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-10-02 23:10 +0200 |
| Message-ID | <uwg8u-TY-97@gated-at.bofh.it> |
| In reply to | #187479 |
On Mon 02 Oct 2017 at 06:26:08 (-0400), Gene Heskett wrote: > On Monday 02 October 2017 03:00:28 Reco wrote: > > > Hi. > > > > On Sun, Oct 01, 2017 at 07:26:30PM -0700, Gary Roach wrote: > > > This is the second time I've tried to send this. The first one just > > > disappeared to the bit bucket I assume. So lets try again. > > > > It did not. Everyone on the list got it, I believe. > > > You are using gmail. To gmail, the echo from the list is a duplicate, and > deleted. Just one of the reasons I left gmail. As Reco wrote, the OP posted twice. My response to the first post was already six minutes old by the time the OP reposted. (Reco's response was much more thorough.) Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-10-03 22:40 +0200 |
| Message-ID | <uwC8V-5tH-1@gated-at.bofh.it> |
| In reply to | #187479 |
[Multipart message — attachments visible in raw view] — view raw
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. Gary R
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-10-04 01:00 +0200 |
| Message-ID | <uwEkp-6JD-1@gated-at.bofh.it> |
| In reply to | #187536 |
On Tue 03 Oct 2017 at 13:30:11 (-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. Perhaps you need to rereport your symptoms. Indeed, report them at all: you said ping worked; pinging what? Can you ping the loopback? the router? other local hosts, by number or by name? 8.8.8.8? "The same problem" doesn't cut it. At least you've now got the external nameservers in your resolv.conf. And does your router do DNS or not? Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Gary Roach <gary719_list1@verizon.net> |
|---|---|
| Date | 2017-10-04 01:50 +0200 |
| Message-ID | <uwF6N-7fW-1@gated-at.bofh.it> |
| In reply to | #187538 |
On 10/03/2017 03:53 PM, David Wright wrote: > On Tue 03 Oct 2017 at 13:30:11 (-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. > > Perhaps you need to rereport your symptoms. Indeed, report them > at all: you said ping worked; pinging what? Can you ping the > loopback? the router? other local hosts, by number or by name? > 8.8.8.8? "The same problem" doesn't cut it. At least you've now > got the external nameservers in your resolv.conf. And does your > router do DNS or not? > > Cheers, > David. > > Symptoms: Any package that needs access to the network sends an error message indicating that it doesn't have access to the internet. Ping doesn't work for names but does for ip addresses. All ip addresses both local and global. In short, there doesn't seem to be any access to a name server. My believe that my Actiontec router at 192.168.1.1 also acts as a name server. Thanks for the help Gary R
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2017-10-04 14:40 +0200 |
| Message-ID | <uwR7X-6fP-3@gated-at.bofh.it> |
| In reply to | #187539 |
On Tue, Oct 03, 2017 at 04:47:35PM -0700, Gary Roach wrote: > Symptoms: Any package that needs access to the network sends an error > message indicating that it doesn't have access to the internet. Ping doesn't > work for names but does for ip addresses. All ip addresses both local and > global. Show, don't tell. Run some basic diagnostic commands and paste THE COMMANDS and their output here. For example, wooledg:~$ ls -ld /etc/resolv.conf -rw-r--r-- 1 root root 112 Aug 21 08:29 /etc/resolv.conf ^^ This shows whether resolv.conf is a regular file or a symlink. wooledg:~$ cat /etc/resolv.conf domain eeg.ccf.org search eeg.ccf.org nameserver 10.76.142.103 nameserver 10.76.142.42 nameserver 172.28.254.24 ^^ This shows the CONTENT of resolv.conf, i.e. what the resolver library inside libc will try to use. wooledg:~$ ping -c 1 10.76.142.103 PING 10.76.142.103 (10.76.142.103) 56(84) bytes of data. 64 bytes from 10.76.142.103: icmp_seq=1 ttl=63 time=0.431 ms --- 10.76.142.103 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms ^^ This shows that I can ping my nameserver and get a response. wooledg:~$ host www.debian.org www.debian.org has address 149.20.4.15 www.debian.org has address 128.31.0.62 www.debian.org has IPv6 address 2001:4f8:1:c::15 ^^ This shows a DNS name resolution attempt using resolv.conf but not libc's resolver. wooledg:~$ getent hosts www.debian.org 2001:4f8:1:c::15 www.debian.org ^^ This shows a "regular" name lookup attempt using libc's resolver. wooledg:~$ dig @10.76.142.103 www.debian.org ; <<>> DiG 9.10.3-P4-Debian <<>> @10.76.142.103 www.debian.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16916 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 6 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.debian.org. IN A ;; ANSWER SECTION: www.debian.org. 59 IN A 128.31.0.62 www.debian.org. 59 IN A 149.20.4.15 ;; AUTHORITY SECTION: www.debian.org. 28559 IN NS geo2.debian.org. www.debian.org. 28559 IN NS geo3.debian.org. www.debian.org. 28559 IN NS geo1.debian.org. ;; ADDITIONAL SECTION: geo1.debian.org. 14775 IN A 82.195.75.105 geo2.debian.org. 14775 IN A 209.87.16.31 geo2.debian.org. 14775 IN AAAA 2607:f8f0:614:1::1274:31 geo3.debian.org. 14775 IN A 194.177.211.201 geo3.debian.org. 14775 IN AAAA 2001:648:2ffc:deb::211:201 ;; Query time: 0 msec ;; SERVER: 10.76.142.103#53(10.76.142.103) ;; WHEN: Wed Oct 04 08:29:27 EDT 2017 ;; MSG SIZE rcvd: 236 ^^ This shows an explicit DNS name resolution attempt, specifying the exact nameserver IP to use, and showing full details. wooledg:~$ dig @8.8.8.8 www.debian.org ; <<>> DiG 9.10.3-P4-Debian <<>> @8.8.8.8 www.debian.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20704 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.debian.org. IN A ;; ANSWER SECTION: www.debian.org. 295 IN A 149.20.4.15 www.debian.org. 295 IN A 128.31.0.62 ;; Query time: 19 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Wed Oct 04 08:32:59 EDT 2017 ;; MSG SIZE rcvd: 75 ^^ This shows an explicit DNS name resolution attempt using Google's public nameserver. > In short, there doesn't seem to be any access to a name server. My believe > that my Actiontec router at 192.168.1.1 also acts as a name server. In your diagnostic command-and-response session, be sure to include the results of your attempts to ping your nameserver by IP address, and of performing a DNS lookup using that nameserver. See examples above. In the event that one of the commands does not work as expected, it's helpful to try alternatives. E.g. if you can't do name resolutions through 192.168.1.1 then try through 8.8.8.8. Most plastic routers don't run their own nameserver; instead, they just forward your DNS requests to your ISP's nameservers, which may or may not be functional on any given day. So, if 192.168.1.1 fails but 8.8.8.8 works, then you know you're going to need to go down the road of changing what resolv.conf contains to something usable, a topic upon which we've already had a massive discussion within this thread. If both 192.168.1.1 and 8.8.8.8 fail, then you may be facing a firewall or routing issue.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-10-04 19:00 +0200 |
| Message-ID | <uwVbz-i3-3@gated-at.bofh.it> |
| In reply to | #187546 |
On Wed 04 Oct 2017 at 08:38:10 (-0400), Greg Wooledge wrote: > On Tue, Oct 03, 2017 at 04:47:35PM -0700, Gary Roach wrote: > > Symptoms: Any package that needs access to the network sends an error > > message indicating that it doesn't have access to the internet. Ping doesn't > > work for names but does for ip addresses. All ip addresses both local and > > global. > > Show, don't tell. […] > > In short, there doesn't seem to be any access to a name server. My believe > > that my Actiontec router at 192.168.1.1 also acts as a name server. > > In your diagnostic command-and-response session, be sure to include > the results of your attempts to ping your nameserver by IP address, > and of performing a DNS lookup using that nameserver. See examples > above. > > In the event that one of the commands does not work as expected, it's > helpful to try alternatives. E.g. if you can't do name resolutions > through 192.168.1.1 then try through 8.8.8.8. > > Most plastic routers don't run their own nameserver; instead, they just > forward your DNS requests to your ISP's nameservers, which may or may > not be functional on any given day. So, if 192.168.1.1 fails but > 8.8.8.8 works, then you know you're going to need to go down the road > of changing what resolv.conf contains to something usable, a topic upon > which we've already had a massive discussion within this thread. > > If both 192.168.1.1 and 8.8.8.8 fail, then you may be facing a firewall > or routing issue. Last time this came up with this OP, the discussion of whether routers contain DNS servers ran into the sand unanswered, though the paucity of lines in their /etc/hosts (localhost plus those allnodes/routers) seemed to suggest that this one (if it's still the same one) might. https://lists.debian.org/debian-user/2015/08/msg01349.html Cheers, David.
[toc] | [prev] | [next] | [standalone]
Page 1 of 6 [1] 2 3 4 5 6 Next page →
Back to top | Article view | linux.debian.user
csiph-web