On Tuesday, 28 May 2019 9:31:04 ACST Mark Misulich wrote:
On Mon, 2019-05-27 at 23:52 +0200, Carlos E. R. wrote:
On 27/05/2019 20.42, Mark Misulich wrote:
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote:
On 27/05/2019 18.36, Mark Misulich wrote:
So you don't have any DNS servers defined, and your machine does not know how to resolve hostnames to IP addresses. That is what we have to solve now. What DNS servers are other hosts on your LAN using? If you're using DHCP, you should be able to get his information automatically from your router (or whatever is acting as the DHCP server), but you may need to tell Network Manager to get the DNS servers for this connection automatically. Alternatively, you can manually configure DNS servers to override the auto config. My laptop etc/resolve.conf file reads nameserver 192.168.1.1 It reads
On Tue, 2019-05-28 at 10:17 +0930, Rodney Baker wrote: the same as the resolve.conf file on my desktop, nameserver 192.168.1.1.
[...]
As expected, your wired ethernet results match those of the wireless connection, so I've cut them out for brevity.
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
When I ping www.google.com it says Name or service not known
This would point to the name resolution not working. What is the result of this:
egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
?
Mark
So the machine in question is pointing to the router as its DNS server. Assuming that is the same as the other machines on your LAN that is probably correct.
Are either nslookup or dig installed? If so, you can manually set the server used for name lookups by those utilities and test name resolution. For example (screen capture from my machine):
user@hostname ~ $ nslookup
server 10.128.1.9
Default server: 10.128.1.9 Address: 10.128.1.9#53
www.google.com
Server: 10.128.1.9 Address: 10.128.1.9#53
Non-authoritative answer: Name: www.google.com Address: 216.58.199.68 Name: www.google.com Address: 2404:6800:4006:809::2004
(Use Ctrl+C to exit the nslookup interactive prompt).
Or with dig, you would do:
dig @192.168.1.1 www.google.com
It should return the IP address details.
~> dig @192.168.1.1 www.google.com ; <<>> DiG 9.11.2 <<>> @192.168.1.1 www.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45760 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 258 IN A 172.217.9.68 ;; Query time: 29 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Mon May 27 22:50:23 EDT 2019 ;; MSG SIZE rcvd: 59 ~> nslookup
nslookup never did provide any readout, after 15 minutes of waiting.
Assuming that works, it is then a matter of figuring out why your machine is not parsing /etc/resolv.conf (may be hinted at in another response) or why it is not getting the dns server address from your router and automatically creating the appropriate file/entry if /etc/resolv.conf is no longer used.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org