I have installed opensuse11.2 on a HP proliant 350
This is a server configuration with DHCP, BIND, XEN and Apache servers
I cannot browse the internet. I looked at same problems described on this forum and did a lot of testing
The network is up : I can ping the router-modem and the DNS address of my provider
I can reach google with the browser when setting the address 209.85.229.103 but not with the name Google
I have disabled the IPV6 flag in the Yast network
I have set ipv6.disable=1 in the boot option
I have removed the file /etc/resolv.conf
Nothing help but I think that it is a problem of DNS. If I stop the BIND server still cannot reach the internet >:(
in the Bind log I see these lines
14-Nov-2009 12:15:55.891 network unreachable resolving ‘www.symantec.com/A/IN’: 2001:503:231d::2:30#53
14-Nov-2009 12:15:56.485 network unreachable resolving ‘za.akadns.org/A/IN’: 2001:500:2f::f#53
14-Nov-2009 12:15:56.485 network unreachable resolving ‘za.akadns.org/AAAA/IN’: 2001:503:ba3e::2:30#53
The addresses are IPV6
Si I think that there is a problem with IPV6
In the /var/log/messages log I have found this
Nov 14 12:00:46 hpprol avahi-daemon[2739]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.130.
Nov 14 12:00:46 hpprol avahi-daemon[2739]: Interface br0.IPv4 no longer relevant for mDNS.
Nov 14 12:00:50 hpprol avahi-daemon[2739]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.130.
Nov 14 12:00:50 hpprol avahi-daemon[2739]: New relevant interface br0.IPv4 for mDNS.
Nov 14 12:00:50 hpprol avahi-daemon[2739]: Registering new address record for 192.168.1.130 on br0.IPv4.
Nov 14 12:00:51 hpprol avahi-daemon[2739]: Registering new address record for fe80::221:5aff:fe4d:fe50 on eth0.*.
Nov 14 12:15:03 hpprol named[10596]: using default UDP/IPv6 port range: [1024, 65535]
Nov 14 12:15:03 hpprol named[10596]: listening on IPv6 interfaces, port 53
DNS seems to be a common problem with fresh 11.2 installations. There’s plenty of other solutions around this forum, most recommending deletion of resolv.conf: switching to ifup worked for me so I haven’t tried any of the others.
I also encountered the same problem and still, I can’t find a better solution. I was able to remove the file resolv.conf but I don’t know excatly what you mean “swith to ifup”.
removing resolv.conf doesn’t solve the problem because when configuring the network interface with Yast (network settings) the same resolv.conf was recreated.
It contains only the comments and “search xxxxx” where xxxxx is domain search set in Yast ==> Network setting ==> hostname/DNS
the Name server 1 to 3 defined on the same tab in Yast are missing
I added in resolv.conf the strings
nameserver xxx.xxx.xxx.xxxx
nameserver xxx.xxx.xxx.xxxx
where xxx.xxx.xxx.xxx are the DNS address of my provider
Thereafter internet browsing works:)
Manage the network through YaST. There’s a selection box there somewhere to disable Network Manager and use what it calls the “traditional method”. Then just enter your connection details.
This worked for me, but may not work for you.
I had a similar issue. The Firefox was working okay but after enabling the DNS server Firefox stopped working and neither could I ping. Though $host command did resolve the ip address. Finally if had to manually edit etc/resolv.conf to direct the system towards the name servers.
nameserver (name server ip1)
nameserver (name server ip2)
search domain_name.com
The system is up and running well. YAST has a tendency of overwriting configuration files.
There is a major bug in OpenSUSE 11.2 X64, that seems to have been around for some months, affecting new installations. It impacts DNS, DHCP, Wget, Firefox, etc., and possibly IPV6 and Avahi, and there are comments all over the discussion boards about various secondary consequences of it, and some proposed fixes, but the correct solution is not prominently noted.
The effect of the bug is that ping to a static IP works, but DNS lookups do not, and thus browsers do not work by URL (but will by IP address), and packages cannot be updated from repositories.
Some have suggested turning IPV6 off, some telling Firefox not to use IPV6, and some to edit /etc/resolv.conf --although this is a temporary solution as the file may get overwritten, or it may prevent future updates by Yast.
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
THE TEMPORARY FIX IS:
MANUALLY RUN UPDATES TO DOWNLOAD THE PERMANENT FIX FROM THE REPOSITORIES; PARTICULARLY TO DHCPD!!! [Update cites Bugzilla 565030 and 569972]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If you are lucky, the fix will be in the update and the bug will go away.