<br><br><div class="gmail_quote">On Jan 31, 2008 3:36 PM, Steve Johnson <<a href="mailto:srj@adnd.com">srj@adnd.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 1/31/08, Sean <<a href="mailto:seanvanco@gmail.com">seanvanco@gmail.com</a>> wrote:<br></div><div class="Ih2E3d">> Ah you meant the router ;)<br>><br>> Is it possible to assign additional or static DNS servers, but still<br>
> use DHCP for the router's IP address, with Linksys routers? I don't<br>> have access to one at the moment, but it wouldn't surprise me.<br><br></div>Yes you can do that.<br><br>He should get rid of the <a href="http://sonic.net" target="_blank">sonic.net</a> DNS entry, they do not allow<br>
recursive lookups for non <a href="http://sonic.net" target="_blank">sonic.net</a> customer (I believe..) and this<br>can cause it to appear to not be on the internet.<br></blockquote></div><br>Or put it on the bottom in case it might be needed. Here's what I have for resolv.conf. I'm connected to Comcast through a Linksys too, only in Michigan. I'd use the DNS servers in California if I were there, this is only for reference.<br>
<br>search <a href="http://hsd1.mi.comcast.net">hsd1.mi.comcast.net</a>.<br>nameserver <a href="http://68.87.77.130">68.87.77.130</a><br>nameserver <a href="http://68.87.72.130">68.87.72.130</a><br><br>I'd definitely be leery of 192.168 DNS server entries, they sound like a private network.<br>
-- <br>Jack Smith<br><br>English doesn't borrow from other languages -- English follows other languages down dark alleys and takes what it wants.