<div dir="ltr">Wad,<br><br>If you are pointing to localhost in resolv.conf, will there be at least a caching DNS named server to catch it?<br><br>--HH<br><br><div class="gmail_quote">On Tue, Aug 26, 2008 at 10:08 AM, John Watlington <span dir="ltr"><<a href="mailto:wad@laptop.org">wad@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I've figured out more about why my first install of 0.4 went so badly.<br>
<br>
For some reason, the network interfaces weren't configured properly<br>
on first boot (even though the files were in the right places).<br>
In conjuction with having the cable to my wired net plugged into the<br>
LAN port, nothing was happening.<br>
<br>
What worried me in addition to the above was that DNS had completely<br>
broken.<br>
Any DNS queries on the server (host/dig/nslookup), such as<br>
"schoolserver",<br>
were hanging. But queries directed to the DNS server on localhost<br>
were just fine.<br>
<br>
The answer is that /etc/resolv.conf should probably point to localhost,<br>
not the address of one of the interfaces (<a href="http://172.18.0.1" target="_blank">172.18.0.1</a>). Just in case...<br>
<br>
I'll git the change after a suitable comment period.<br>
<br>
Second install went like a breeze,<br>
wad<br>
<br>
_______________________________________________<br>
Server-devel mailing list<br>
<a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/server-devel" target="_blank">http://lists.laptop.org/listinfo/server-devel</a><br>
</blockquote></div><br></div>