http://qa.mandrakesoft.com/show_bug.cgi?id=2829
------- Additional Comments From [EMAIL PROTECTED] 2003-03-12 16:30 ------- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 jsk_priv wrote: environments network Your dhcp server was probably providing a domain name. Switch Router resolv.conf to Can you try testing your dns server to see if it gives responses. Try: $ host www.google.com 192.168.1.254 and see if you get a valid address. Also, try $ host www.google.com 213.191.74.18 to see if the router could feasibly send the real dns server addresses (ie has rules supporting dns traffic both ways). (dhcp-client-3.0-2pl2.5mdk.i586.rpm and restarting localhost listed in networking. Control Can you send the contents of /var/lib/dhcp/dhclient-eth0.leases (if your network device is eth0 of course, adjust if defferent). This will show exactly what the dhcp server is sending. Regards, Buchan - -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+b1RSrJK6UGDSBKcRAoavAKCnCwMtxdNpb2Zqny9s0j2idFp6rQCgxYMv 3ggTLkUHMskklLarxK5DWcE= =aRES -----END PGP SIGNATURE----- ------- 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.