[Bug 71554] Re: resolv.conf has wrong entry

2006-11-17 Thread Dennis Kaarsemaker
DHCP gets the info from your router. Fix your router if this is wrong. ** Changed in: resolvconf (Ubuntu) Status: Needs Info => Rejected -- resolv.conf has wrong entry https://launchpad.net/bugs/71554 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mail

[Bug 71554] Re: resolv.conf has wrong entry

2006-11-17 Thread manu
If DHCP were setting resolv.conf, it should set it on every reboot removing any custom configuration, isn't it? It seems that is not happening here. Strange. -- resolv.conf has wrong entry https://launchpad.net/bugs/71554 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ub

[Bug 71554] Re: resolv.conf has wrong entry

2006-11-14 Thread Dori
This was all done by the installer, through I can only assume DHCP, and it was whatever auto detection mechanism it used that included the wrong entry. I downloaded and used the standard 6.10 ISO for desktop PCs (x86). I didn't set anything manually during the install. I did manually remove the ent

[Bug 71554] Re: resolv.conf has wrong entry

2006-11-14 Thread Stéphane Graber
Can you describe exactly what you did to have this problem ? Do you have all your settings set by DHCP, what kind of installation did you use (livecd or alternate). If DHCP, did the installer detected it correctly or did you have to set them manually ? -- resolv.conf has wrong entry https://lau

[Bug 71554] Re: resolv.conf has wrong entry

2006-11-14 Thread Dori
The problem is that it shouldn't put the wrong entry in there. Requests for websites timed out and the second entry was not used. I don't know how much clearer I could be. It simply put an entry that shouldn't be there, which resulted in websites being unreachable. If you want to ignore it fine, I

[Bug 71554] Re: resolv.conf has wrong entry

2006-11-13 Thread Stéphane Graber
So, where is the problem ? It didn't use the second one when receiving no answer from the first one ? (It shoulds but after a really long delay) Your bug report isn't clear enough (for me at least), can you provide more info on what is exactly your problem ? ** Changed in: Ubuntu Status: U