sudo stops working after filling a domain name in manual network configuration
Bug #222935 reported by
gary_inNYC
This bug report is a duplicate of:
Bug #32906: sudo fails if it cannot resolve the local hostname and no MTA is installed.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu |
New
|
Undecided
|
Unassigned | ||
Bug Description
In Hardy (x86 final release clean install), I found that manually typing in a domain name in Network Settings (general section) stops the sudo command from working. Subsequently, an "unresolved host" message comes up when issuing a sudo command in the terminal, crippling much functionality of the system.
To fix the issue, I had to remove the domain name I entered, and sudo worked correctly again.
- Gary
Revision history for this message
| Thomas Hood (jdthood) wrote | #1 |
To post a comment you must log in.
/etc/hosts should look like this, where /etc/hostname contains "foo":
127.0.0.1 localhost
127.0.1.1 foo
If foo has a permanent IP address (e.g., 123.45.67.89) and fully qualified domain name ("foo.bar.com") then /etc/hosts should look like this:
127.0.0.1 localhost
123.45.67.89 foo.bar.com foo
See http://