Date: Wed, 20 Aug 2008 15:02:25 -0400 From: Michael Powell <nightrecon@verizon.net> To: freebsd-questions@freebsd.org Subject: Re: Loss of Internet Contivity Message-ID: <g8hpk9$go5$1@ger.gmane.org> References: <200808200854.m7K8skoh032455@mail8.tpg.com.au> <34701C68-22F3-40A9-8031-F9EA21D015AD@lafn.org> <200808201213.m7KCD1UI017672@mail13.tpg.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Warren Liddell wrote:
>
>>The attachment shows that DNS is unable to find the IP address. This
>>appears to be a DNS resolver issue, not a network issue. Check
>>/etc/ resolv.conf and make sure its correct. Then check the indicated DNS
>>servers using dig.
>
> such a simple thing i didnit even think to check and it solved my
> problem, it would seem the static DNS entries in my router are being
> added into the resolv.conf file as nameservers and ironically as soon
> as i del those entries i had internet traffic restored.
>
>
If you are getting this assigned by DHCP from your router, it can be
controlled with /etc/dhclient.conf. Typically most of the settings do not
require alteration, but maybe an item or two needs a tweak. Placing these
into dhclient.conf can either override or adjust, as needed.
This is an example from my pf/gateway box which gets all it's external NIC
settings by DHCP from my DSL modem. I wanted this box to use it's own DNS
server, as do the other boxen on the LAN, instead of the one in the DSL
modem.
interface "rl0" {
send dhcp-client-identifier 00:0e:2e:6d:17:54;
prepend domain-name-servers 127.0.0.1;
}
There are many other settings, man dhclient.conf and man dhcp-options for
more details.
-Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?g8hpk9$go5$1>