View Single Post

  #4 (permalink)  
Old 12-30-2003
Andrey Asadchev
 
Posts: n/a
Default Re: dhcp server and isp's dns...

Luke wrote:
> On 2003-12-30, Andrey Asadchev <dont.spam.me@softhome.net> wrote:
>
>>Luke wrote:
>>
>>>How can I pass the DNS info along to my clients when the DNS info is
>>>dynamically assigned? I see in the DHCP howto that you can do it easily
>>>if they are static, but what about dynamic?

>>
>>I doubt the DNS servers of your provider will be changing IPs often
>>enough to cause your discomfort. They are dynamically assigned, yes -
>>but they are the same every time (unless the provider is doing something
>>really really weird). Get the nameservers IPs from /etc/resolv.conf on
>>the router and put them into /etc/dhcp(3)?/dhcpd.conf.

>
>
> How do my hardware routers handle this? Seems like it should be
> possible with dhcpd, and its definitely the preferred behavior for me in
> this case (though I do recognize that the DNS servers will change
> infrequently).


Not sure about your question. How to get the nameserver info from your
router?

> So what I thought this meant was that "all Mircosoft DHCP clients" would
> need this workaround, as mentioned above... sounds like from your post,
> that this is not the case, however. I don't need to support win95, so I
> guess I won't bother with it then.


I must have skipped that part of the HOWTO :-).
I have ran dhcpd v3 and v2 and Windows clients (98 and above) had no
problems at all. I am also using Debian Woody. If you do run into
trouble i guess it does not hurt to check that options as well.


> Huh, I would've thought the /etc/init.d/dhcp scripts would have been
> replaced each upgrade... thanks for the info


Debian policy
<snip>
The /etc/init.d scripts must be treated as configuration files, either
(if they are present in the package, that is, in the .deb file) by
marking them as conffiles, or, (if they do not exist in the .deb) by
managing them correctly in the maintainer scripts (see Configuration
files, Section 10.7). This is important since we want to give the local
system administrator the chance to adapt the scripts to the local
system, e.g., to disable a service without de-installing the package, or
to specify some special command line options when starting a service,
while making sure her changes aren't lost during the next package upgrade
</snip>




Reply With Quote