At 04:43 PM 3/31/2006, you wrote:
Your saying that dhcp client has no built in way to communicate to
dhcpd the dns ip address it receives at boot time or during the
normal lease update process?
Not that I've seen. The script is pretty one-minded. Impression I
get is you're expected to edit
"fbsd_user" <[EMAIL PROTECTED]> wrote:
>
> Let me see if I understand you correctly.
>
> Your saying that dhcp client has no built in way to
> communicate to dhcpd the dns ip address it receives
> at boot time or during the normal lease update process?
Yes.
> That your suggesting the work aroun
Let me see if I understand you correctly.
Your saying that dhcp client has no built in way to
communicate to dhcpd the dns ip address it receives
at boot time or during the normal lease update process?
That your suggesting the work around is to customize the
dhclient-script code at the point whe
Kris Anderson <[EMAIL PROTECTED]> writes:
> I think the answer you are looking for lies in
> dhclient-script. I noticed it futzes with resolv.conf.
> If you happen to notice resolv.conf changing (You can
> test this about by making a backup of resolv.conf,
> erasing its contents and then rebooting
--- fbsd_user <[EMAIL PROTECTED]> wrote:
> I use dhcp client to get the info needed from my ISP
> at boot time.
> I also run dhcpd for issuing ip address to my LAN.
>
> In the dhcpd.conf file I have option statement for
> the
> ISP's dns ip address like this:
>
> option domain-name-servers xx.16
