Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SuSE 9.1 DNS problem 1

Status
Not open for further replies.

Dbyte

Technical User
Mar 6, 2002
87
I am unable to view any websites using either Konquerer or Firefox except by using their IP address. I cannot get DNS to work correctly. My linux box is part of a peer-to-peer LAN. I can view/ping all other PCs (Windows boxes) on the LAN fine using either their hostname or IP address. All machines share a frational T1 connection with static IP addresses. I have 2 nameserver IPs provided by our ISP: 216.204.111.033 & 216.204.102.010. All the Windows boxes use these 2 nameserver IPs & have no problems whatsoever. My resolv.conf file has both of these IP addresses in it & no others. Here is my output from ifconfig:

eth0
Link encap:Ethernet HWaddr 00:01:02:91:47:D8
inet addr:192.168.1.12 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr:fe80::201:2ff:fe91:47d8/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500
Metric:1
RX packets:694 errors:0 dropped:0 overruns:0 frame:0
TX packets:230 errors:0 dropped:0 overruns:0 carrier:5
collisions:5 txqueuelen:1000
RX bytes:80719 (78.8Kb) TX bytes:61965 (60.5Kb)
Interrupt:9 Base address:0x1000
lo
Link encap:Local loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2331 errors:0 dropped:0 overruns:0 frame:0
TX packets:2331 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:466160 (455.2Kb) TX bytes:466160 (455.2Kb)

Any ideas on what I should check out next? BTW, I'm a relative newbie to Linux so please simplify your advice as much as possible - thanks.

-Dbyte
 
OK, here's some additional info:

# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0


I also wanted to add that our ISP controls the gateway (192.168.1.1) that all the PCs route thru to reach the Internet.
 
Another update:

I can do digs & nslookups for URLs but not pings. When I try to ping any URL the cursor just sits there; no error or timeout message.
 
There should be a place to enter your DNS address' and gateway in your Linux desktop for the Network configuration.

From the command line, you can run redhat-network-config, if this is Redhat.
 
sorry, just noticed the SUSE, but I would assume that on the configuration, you should be able to enter the gateway, and DNS ip's
 
cdlvj,
I forgot to mention that the gateway is already setup as 192.168.1.1 & that IP forwarding is disabled. When trying to configure the DNS servers in YaST (Network Services, DNS & Host Name) the host name is 'Dbyte' & the domain name is 'default'. When I tried to manually enter the 2 nameserver IP addresses I got the following error message: "the primary name server is not correct." The domain search for the 1st entry says 'default' while the 2nd entry's is blank. I ended up vi'ing the resolv.conf file to add both nameserver IP's that I indicated in my initial post. I am confident that the gateway & nameserver values are correct & in [at least some of] the right files. The successful digs & nslookups confirm this. What I can't figure out is what configuration files the browsers are using that the command line tools are not(?). It's also strange because the browsers time out trying to resolve the URLs; they don't immediately respond with any kind of error message.
 
maybe a silly question, but what does your resolv.conf file look like? Does it contain the name 'nameserver' ?
It should look something like this:

nameserver 216.204.111.033
nameserver 216.204.102.010


 
BIS,
My resolv.conf file looks exactly like the example you posted, except that the 1st nameserver's IP address is 216.204.000.033.

Any other ideas/suggestions/thoughts? This is driving me nuts & seems to be a critical flaw w/ Linux, judging by all the posts w/ similar network-related questions.
 
Can you try and de-install/re-install the nic using that YaSt program? And the driver is correct?
 
cdlvj,
I thought about this, but then I realized that if I can browser my LAN & connect to websites via their IP addresses that the problem doesn't involve the NIC. I also checked the boot messages onscreen for the NIC & it is configured correctly @ boot time (correct MAC, IP, & loopback addresses).

I honestly don't believe this is hardware related. And I don't know enough about all the configuration files used to determine where else to look on the software side. Is there any way to simply reinstall the networking components of the OS off the CD to overwrite all the files that have been modified & start over (i.e. a "repair" install)?
 
Dbyte,

I wish I would have looked at your thread earlier.

Change your /etc/resolv.conf to reflect this.

nameserver 216.204.111.33
nameserver 216.204.102.10

This removed the added "0" in the fourth octet. Suse Linux does not recognize this as a valid IP address.
 
dirkdiggy, I'll give that a try tomorrow AM & let you kow how it works. Thanks.
 
dirkdiggy is THE MAN!

Worked brilliantly. I'm typing this reply on my newly web-enabled SuSE box now. I never would have thought of it on my own. Now to download some updates...

THANKS!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top