openSUSE 12.3 not able to resolve server names (*Sorry DenverD :-( no outputs )

English Network/Internet
#1

Hello,

I just restarted my laptop and tried to access internet using firefox, it took too long for the page to load.

So i checked the internet connection by using

ping 8.8.8.8

Google’s DNS server i am using currently

it went fine, replied at about 14ms

then i tried to access Google, which did not open (server not found)

then i obtained the ip address of Google from my desktop (which is connected to the same router, able to access internet on it) which is 173.194.36.50 and entered it in firefox’s address bar through which i was able to access Google

openSUSE is not able to resolve the server name into ip address (but that’s what i think)

nslookup also doesn’t work

PS : I don’t have access to internet on the laptop due to this problem so i’m not able to provide outputs at present. (I would use a pendrive to get a text file of the output from my laptop if anyone requested)

Thank You!

#2

On 05/16/2013 08:56 AM, ThePerfectPunk wrote:
>
> I don’t have access to internet on the laptop

temporarily you might give openSUSE a hint as to which nameservers to
use (it should happen automatically that networking finds a usable
Domain Name Server, but that depends on how you have set up the
networking (maybe with Network Manager, or traditional ifup…and,
how you have directed the DHCP to blah blah)

you can do this temporarily (if you wish) by using what i always use:

using a SuperUser/root file editor i made a backup of the file and
then changed /etc/resolv.conf.

when i began the bottom portion looked like this (the numbers in
yours will be different):


blah blah blah
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
nameserver 192.168.1.1
nameserver 208.67.222.222
nameserver 208.67.220.220

what i did was i just added a # to the beginning of each line which
began with “nameserver” and then added in the IPv4 and IPv6 DNS
address for Google’s FREE name servers, so my resolv.conf looked like:


blah blah blah
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
#nameserver 192.168.1.1
#nameserver 208.67.222.222
#nameserver 208.67.220.220
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844

when yours is so edited (i do not know if you know how to edit system
files or not…if you do not, ask), save it and then log out of the
DE and back in (this will cause the networking to restart…it is not
required to boot)

and, unless i am mistaken you should be able to get to the openSUSE
wiki via either of these:

http://en.opensuse.org/
http://130.57.66.6/

that is the way i leave my resolv.conf because that way no matter if
i am at home (where my router is pointed to Googles DNS) or hooked up
at the (say) coffee shop, i always get good fast DNS, no matter what
the serving ISP has in use (which often will not correctly process
IPv6 addresses!)

–
dd
http://tinyurl.com/DD-Caveat

#3

On 2013-05-16 08:56, ThePerfectPunk wrote:

…

> openSUSE is not able to resolve the server name into ip address (but
> that’s what i think)
>
> nslookup also doesn’t work
>
> PS : I don’t have access to internet on the laptop due to this problem
> so i’m not able to provide outputs at present. (I would use a pendrive
> to get a text file of the output from my laptop if anyone requested)

Yes, you will have to provide them that way :slight_smile:

Let me see, what we can ask…


cat /etc/resolv.conf
host -v suse.com
/sbin/ifconfig
/sbin/route

All complete, command and response block, inside code tags. The commands
can all be used as plain user as typed above :slight_smile:

Please use code tags for printouts and commands. Advanced editor, ‘#’
button. Posting in Code Tags - A Guide

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#4

When you think your DNS server does not function (and from what you tell, though not from what you dont show, I think the same) you should then check if you have a DNS(s) server configured and which one(s)

grep -v '^#' /etc/resolv.conf

And when there is/are DNS servers configured there, first check if you can reach it/them with ping.

When there aren’t ay there, you have to find out why not, but in the mean time you couls add the line

nameserver 8.8.8.8

to that file.

#5

Thank you!!!

putting the line “nameserver 8.8.8.8” in the /etc/resolv.conf did the trick :slight_smile:

Still not sure what caused the problem but at least got it to work :slight_smile:

#6

Well, that is the problem now. What you did is on;y a by-pass (but you live rather long with it).
For some reason your DHCP server (I guess you use one) did not provide you with a decent DNS server.

As you decided NOT to post the output we suggested you to post here, we can not go further into that.

#7

I’m really sorry, didn’t know the output was still relevant

robinlistas :


mohit@linux-xmln:~/Downloads/NB087_Ubuntu/NB087_BT_ubuntu_release/rtbth_v3.9.3/rtbth_v3.9.3> cat /etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
#nameserver 192.168.43.1                                                                                                                                                                        
nameserver 8.8.8.8                                                                                                                                                                              
nameserver 8.8.4.4mohit@linux-xmln:~/Downloads/NB087_Ubuntu/NB087_BT_ubuntu_release/rtbth_v3.9.3/rtbth_v3.9.3> host -v suse.com                                                                 
Trying "suse.com"                                                                                                                                                                               
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45153                                                                                                                                       
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0                                                                                                                            
                                                                                                                                                                                                
;; QUESTION SECTION:
;suse.com.                      IN      A

;; ANSWER SECTION:
suse.com.               21599   IN      A       130.57.5.70

Received 42 bytes from 8.8.8.8#53 in 405 ms
Trying "suse.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45230
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;suse.com.                      IN      AAAA

;; AUTHORITY SECTION:
suse.com.               899     IN      SOA     dnsmgmt.provo.novell.com. bwayne.novell.com. 2013032004 10800 3600 2419200 900

Received 90 bytes from 8.8.8.8#53 in 315 ms
Trying "suse.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2491
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;suse.com.                      IN      MX

;; ANSWER SECTION:
suse.com.               21599   IN      MX      2 prv-mx.provo.novell.com.
suse.com.               21599   IN      MX      2 prv1-mx.provo.novell.com.
suse.com.               21599   IN      MX      2 prv3-mx.novell.com.

Received 110 bytes from 8.8.8.8#53 in 310 ms
mohit@linux-xmln:~/Downloads/NB087_Ubuntu/NB087_BT_ubuntu_release/rtbth_v3.9.3/rtbth_v3.9.3> /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 38:EA:A7:EC:4A:69  
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11822 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11940 errors:0 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:9554582 (9.1 Mb)  TX bytes:1612631 (1.5 Mb)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:5321 (5.1 Kb)  TX bytes:5321 (5.1 Kb)

ra0       Link encap:Ethernet  HWaddr 9C:2A:70:5B:9F:A1  
          inet addr:192.168.1.9  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20274 errors:0 dropped:0 overruns:0 frame:0
          TX packets:712 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:5625179 (5.3 Mb)  TX bytes:11618 (11.3 Kb)
          Interrupt:16 

mohit@linux-xmln:~/Downloads/NB087_Ubuntu/NB087_BT_ubuntu_release/rtbth_v3.9.3/rtbth_v3.9.3> /sbin/route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0 ra0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0

hcvv :


mohit@linux-xmln:~/Downloads/NB087_Ubuntu/NB087_BT_ubuntu_release/rtbth_v3.9.3/rtbth_v3.9.3> grep -v '^#' /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
#8

Well, thanks, but now you post of course the situation as it is now. Not how it was when you had the problem. rotfl!

But we can try to discover the past.

From your resolv.conf we can read hat you had as a DNS server: 192.168.43.1

I assume that that is your router. I then asked you to ping to that IP address. You never told if you did, let alone that you posted what the computer said.

I have the strong idea, that either that IP address is wrong, or your router does not provide DNS services. As said, in both cases you can live long and happy with 8.8.8.8 as DNS server, but I then would do two things:
a) remove the line with 192.168.43.1 from the file (because it does not work);
b) do what it says in the comment:

### Please remove (at least) this line when you modify the file!

This is to tell your DHCP client software that you do not want it to set a server because you have already one there.

#9

On 05/16/2013 03:56 PM, hcvv wrote:
> a) remove the line with 192.168.43.1 from the file (because it does not
> work);
> b) do what it says in the comment:

both of which he could/would have done hours before you posted (the
first time in this thread), had he chosen to follow my hints.

or, maybe my post was invisible <shrug>

–
dd

#10

On 2013-05-16, hcvv <hcvv@no-mx.forums.opensuse.org> wrote:
> From your resolv.conf we can read hat you had as a DNS server:
<SNIP>
> This is to tell your DHCP client software that you do not want it to
> set a server because you have already one there.

Please correct my (clearly poor) misunderstanding. I thought that the use of DHCP meant /etc/resolv.conf is ignored and
that the relevant configuration was set in /etc/sysconfig/network/config along the following lines:


DEFAULT_BROADCAST="+"
GLOBAL_POST_UP_EXEC="yes"
GLOBAL_PRE_DOWN_EXEC="yes"
CHECK_DUPLICATE_IP="no"
SEND_GRATUITOUS_ARP="no"
DEBUG="no"
USE_SYSLOG="yes"
CONNECTION_SHOW_WHEN_IFSTATUS="no"
CONNECTION_CHECK_BEFORE_IFDOWN="no"
CONNECTION_CLOSE_BEFORE_IFDOWN="no"
CONNECTION_UMOUNT_NFS_BEFORE_IFDOWN="no"
CONNECTION_SEND_KILL_SIGNAL="no"
MANDATORY_DEVICES=""
WAIT_FOR_INTERFACES="30"
FORCE_PERSISTENT_NAMES=""
LINK_READY_WAIT="0"
IPV6_DAD_WAIT=""
FIREWALL="yes"
LINKLOCAL_INTERFACES="eth*[0-9]|tr*[0-9]|wlan[0-9]|ath[0-9]"
IFPLUGD_OPTIONS="-f -I -b"
NETWORKMANAGER="no"
NM_ONLINE_TIMEOUT="0"
NETCONFIG_MODULES_ORDER="dns-resolver dns-bind dns-dnsmasq nis ntp-runtime"
NETCONFIG_DNS_POLICY="auto"
NETCONFIG_DNS_FORWARDER="resolver"
NETCONFIG_DNS_FORWARDER_FALLBACK="yes"
NETCONFIG_DNS_STATIC_SEARCHLIST=""
NETCONFIG_DNS_STATIC_SERVERS=""
NETCONFIG_DNS_RANKING="auto"
NETCONFIG_NTP_POLICY="auto"
NETCONFIG_NTP_STATIC_SERVERS=""
NETCONFIG_NIS_POLICY="auto"
NETCONFIG_NIS_SETDOMAINNAME="yes"
NETCONFIG_NIS_STATIC_DOMAIN=""
NETCONFIG_NIS_STATIC_SERVERS=""
WIRELESS_REGULATORY_DOMAIN=''
#11

On 05/16/2013 05:30 PM, flymail wrote:
> Please correct my (clearly poor) misunderstanding. I thought that
> the use of DHCP meant /etc/resolv.conf is ignored and that the
> relevant configuration was set in /etc/sysconfig/network/config
> along the following lines:

i think (i clearly do not know exactly how it works…but, i
think) what happens is determined by whether you use NetworkManager
of traditional ifup with YaST…i think it also depends on eye of
newts and chicken bones buried during a full moon…

on the other hand, my system has the resolv revealed above and you
can see from below which DNS is being used:


denver@linux-os114:~> nslookup forums.opensuse.org
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   forums.opensuse.org
Address: 130.57.66.6

denverd@linux-os114:~>

and, by the way i see in my /etc/sysconfig/network/config these (and
as far as i remember i’ve been in that file before–which is where
the chicken bones comes in):

NETWORKMANAGER=“yes”
NETCONFIG_DNS_STATIC_SERVERS=“8.8.8.8 8.8.4.4”

so i assume with NetworkManager doing the job instead of
“/etc/resolv.conf is ignored” it is dictating what will be used…

OR, maybe since NAT router is also set up to point to Google it is
setting the rules…

–
dd

#12

On 2013-05-16, dd <DenverD@no-mx.forums.opensuse.org> wrote:
> i think (i clearly do not know exactly how it works…but, i
> think) what happens is determined by whether you use NetworkManager
> of traditional ifup with YaST…i think it also depends on eye of
> newts and chicken bones buried during a full moon…

Okay, so I’m even more confused - not difficult :)!

I guess my original standpoint came from reading post #10 from thread…

http://forums.opensuse.org/english/get-technical-help-here/network-internet/452460-manually-changing-dns-settings.html

…but I only ever use ifup for desktops and NM for laptops.

#13

My explanation was a bit a shortcut, but it is not untrue IMHO.

In any case, the configurations in /etc/syconfig/network are used at the setting up of the nwetwork. They are NOT the configurations of the several network involved items themselves. Some of the parameters there go directly to the devices at setup (e.g. IP address), others go into the time honoured configuraion files (e.g. /etc/resolv.conf).

With reagrds to the DNS servers, that configuration is in /etc/resolv.conf. How this file is generated is something different (a combination of DHCP when used and the file you mention above), but setting it manualy, will prevent the setting up from DHCP and/or the config files. We had threads here on the forums where people had a resolv.conf file that differed from the setup used in openSUSE (IIRC there was at least one with a leftover from another distribution) and their DHCP did not set the DNS server and the one sitting there was not valid (some router of a different network).

The reason behind it being rather straight forward. When you configure manualy, that has priority over everything else.

#14

On 05/16/2013 06:35 PM, flymail wrote:
> I guess my original standpoint came from reading post #10 from thread…
>
> http://forums.opensuse.org/english/get-technical-help-here/network-internet/452460-manually-changing-dns-settings.html

that is a 28 month old post for an openSUSE 11.1, so i don’t know how
correct it might be for 12.3 (or whatever you are using)…

i am pretty sure NetworkManager has grown a bit in capability since
those old days…maybe it ‘learned’ to read resolve and do what the
root decided was the law!

–
dd

#15

On 2013-05-16 17:30, flymail wrote:

> Please correct my (clearly poor) misunderstanding. I thought that the use of DHCP meant /etc/resolv.conf is ignored and
> that the relevant configuration was set in /etc/sysconfig/network/config along the following lines:

No, it is not ignored. The file is rewritten with the information that
is got from the DHCP server. Notice the comments in the file, if you
modify it yourself then the file is untouched and then the information
from the dhcp server is ignored.

The information can be static, via yast ifup configuration, or from
network manager, or it can be dynamic from any of them.

Not so simple :slight_smile:

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#16

On 2013-05-16 15:36, ThePerfectPunk wrote:
>
> I’m really sorry, didn’t know the output was still relevant

If you want to find out why your system did not work, yes, it is. But
first you have to undo the change you did.

But I see something interesting. Your gateway (the router) is
“192.168.1.1”, but your DNS server was “192.168.43.1” - and this IP is
not reachable with your network mask.

Who set up that DNS address?

If it came from the DHCP server, that server is misconfigured.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#17

Very interesting discussion.
I still have two questions, though. :
Changing the DNS within the network manager (after selecting Automatic (DHCP) addresses only) has the same effect than editing the /etc/resolv.conf file?
It’s covenient to set the Google DNS directly in the router settings?

#18

DNS servers are not set in router settings. DNS and routing are two complete different things.

DNS is the telephone directory of the internet: which IP address belongs to which full qualified domain name (and vv)?

Routing are the handposts in the internet. When I want to go to IP address suchandsuch, which way do I have to go?

#19

On 2013-05-19 09:16, PiElle wrote:
>
> Very interesting discussion.
> I still have two questions, though. :
> Changing the DNS within the network manager (after selecting Automatic
> (DHCP) addresses only) has the same effect than editing the
> /etc/resolv.conf file?

Yes, it does - because in fact the network manager edits that file. But
for that to work you have to revert to the original file: once the
system detects that you changed it manually it understands that you want
to handle the file yourself and will not touch it.

> It’s covenient to set the Google DNS directly in the router settings?

That’s very convenient, because that way the entire house gets a working
DNS. You don’t have to edit computers.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#20

On 2013-05-19 12:46, hcvv wrote:
>
> PiElle;2558155 Wrote:
>>
>> It’s covenient to set the Google DNS directly in the router settings?
> DNS servers are not set in router settings. DNS and routing are two
> complete different things.

Not on many home setups :slight_smile:

You are of course correct, router, dhcp server, dns server, are
different things - but they can reside in the same machine.

The access router provided by ISPs usually contain a DHCP server, and
this one gives the proper DNS settings to the computers in the local
network. The DNS they give can be one at the ISP network, or it can be
the router itself running a cached DNS. And it can also be configured to
give back any other DNS address.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)