DNS resolution on a home network

On Mon February 9 2009 09:16 pm, bobinmurphy wrote:

>
> ken_yap;1941714 Wrote:
>> You shouldn’t parallel name servers like that in /etc/resolv.conf. There
>> is no guarantee of the order in which the requests are made or replies
>> received. So some requests might be able to resolve your local zone, and
>> some not. Instead you should get your local nameserver to forward
>> requests for non-local zones.
>
> Yeah, but since I don’t have a static IP from my ISP I’ve set the
> ethernet connected to my ISP to configure via DHCP. This causes the
> /sbin/dhclient-script to write my ISP’s domain and nameservers into
> /etc/resolv.conf. Short of modifying the system script I haven’t found
> the widget to control this, although I’d think it should be smart enough
> to not do this if there’s a local DNS server running. If I edit
> /etc/sysconfig/network/config to fix this, it ends up resetting the
> resolver to “bind” breaking my local DNS and in this mode all it writes
> to /etc/resolv.conf is the search domains, no nameservers. And for some
> odd reason it insists on including my ISP’s domain in the search line.
>
>
bobinmurphy;

Why not just add a router to isolate your local lan from the ISP. Behind the
router, you can have a static IP for your DNS server and have it forward
requests to your ISP’s DNS. Simple routers are available for < $40 US.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green