http://qa.mandrakesoft.com/show_bug.cgi?id=2829
------- Additional Comments From [EMAIL PROTECTED] 2003-03-12 14:02 ------- I've tried two installations now, both on VirtualPC but different environments One worked with no problems at all - the one within the Sun internal network didn't even need the new cooker rpms for dhcp and dns to work correctly. Second install - at home using the Longshine LCS-882R-WR4 4-Port Switch Router at 192.168.1.254 fails. The router acts as dns proxy. The real dns servers are: 213.191.74.18 and 213.191.74.19. dhcp works ok, but there is no nameresolution. I altered the file resolv.conf to reflect my dns proxy (nameserver 192.168.1.254) with no success. Then i set the real dns-servers in /etc/resolv - same negative result. Installing the latest dhcp-packages (dhcp-client-3.0-2pl2.5mdk.i586.rpm and dhcp-common-3.0-2pl2.5mdk.i586.rpm) from cooker at vat.tu-dresden and restarting networking didn't help. Changing /etc/hosts localhost-entry to 127.0.0.1 localhost.localdomain localhost didn't help I can reach other machines within my LAN by specifying the IP or - if listed in /etc/hosts - by name. To me the configuration looks ok, but i'm not so much of an expert in networking. I put my /etc-directory as tar.gz (approx. 2.5 Megs) here: http://www.gleitmeier.de/downloads/etc.tar.gz and a screenshot of the Control Center showing the current network configuration: http://www.gleitmeier.de/downloads/screenshot1.gif i hope that helps. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: I'm very late on this report, but I've been trying to get it fixed to no avail. I have two boxes, one running 9.0, the other 9.1RC2. Both get an IP address allocated via DHCP and both are on the same network. However, for the 9.1 box it cannot seem to resolve hostnames correctly, forcing you to specify IP addresses in your applications. (Resolving doesn't seem to be working correctly) In both the machines, /etc/resolv.conf looks as follows. (Automagically configured from DHCP) /etc/resolv.conf: nameserver 10.1.1.16 nameserver 10.1.1.10 search af.didata.local Now on the 9.0 box I do a ping (ping terminal.af.didata.local) to a Windows terminal server and it works correctly: [EMAIL PROTECTED] jaco]$ ping terminal.af.didata.local PING terminal.af.didata.local (10.1.0.240) from 10.1.35.66 : 56(84) bytes of data. 64 bytes from terminal.af.didata.local (10.1.0.240): icmp_seq=1 ttl=125 time=0.360 ms ... [EMAIL PROTECTED] jaco]$ >From the 9.1 box I get the following: [EMAIL PROTECTED] jaco]$ ping terminal.af.didata.local ping: unknown host terminal.af.didata.local [EMAIL PROTECTED] jaco]$ Ok, but networking is up and running: [EMAIL PROTECTED] jaco]$ ping 10.1.0.240 PING terminal.af.didata.local (10.1.0.240) from 10.1.35.66 : 56(84) bytes of data. 64 bytes from 10.1.0.240: icmp_seq=1 ttl=125 time=0.374 ms ... [EMAIL PROTECTED] jaco]$ In other news, doing a "ping terminal" on the 9.0 box works, on the 9.1 box not. However, doing a nslookup on "terminal" on both boxes results in the following: [EMAIL PROTECTED] jaco]$ nslookup terminal ... Name: terminal.af.didata.local Address: 10.1.0.240 [EMAIL PROTECTED] jaco]$ Which means that at least that part works. I'm stumped. Any ssh, telnet, rdesktop, etc. to any hostname (with or without the af.didata.local domain) doesn't work. Doing an nslookup and using that IP to connect to, does. The 9.1 machine was upgraded from a working 9.0 box to 9.1RC1 which broke the addresseing. RC2 has not addressed this problem. In addition in 9.1 /etc/hosts still does not contain "127.0.0.1 localhost.localdomain localhost", instead only "127.0.0.1 localhost" which breaks some applications. (eg. Eclipse debugger, not part of main but in full use here) On new bootups the DHCP configuration seems to change it back to "localhost" again, forcing you to make the change manually to get your applications to work.
