Forget a semi-colon in named.conf, lose sudo!
March 1st, 2007
I was playing with setting up bind for my local network at home yesterday and forgot a semi-colon at the end of the localdomain zone. Of course, I’d removed localhost and mugen (the name of the machine I was using) from /etc/hosts so that I could test bind. Restart bind, ping mugen, fail. Oh well… sudo vim /etc/bind/named.conf… sudo can’t look up mugen using gethostbyname(). Shit. No sudo for me. No root user either. Eventually fixed by connecting a monitor and keyboard and starting in single user mode.
Moral of the story? Don’t screw up your resolver if you like having sudo.
Entry Filed under: General
2 Comments Add your own
1. Anonymous | September 13th, 2007 at 12:34 pm
cool
2. Anonymous | September 15th, 2007 at 7:18 pm
The real moral of the story is that you should only use sudo on multi-user machines and if you’re going to be using root with any frequency (such as on a desktop) you’re better off enabling root logins.
It’s always the first thing I do on an Ubuntu install…
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Subscribe to the comments via RSS Feed