Bill Moseley writes:
> On Thu, May 29, 2003 at 10:51:38PM -0400, Jerry Quinn wrote:
>
> > That's one. You don't have to go out of your way in the simple case
> > to get dnsmasq to forward dns requests upstream. It also incorporates
> > /etc/hosts into its cache.
>
> Just so I'm clear, th
* Jeffrey L. Taylor ([EMAIL PROTECTED]) [030527 20:53]:
> 2) configure DHCP server to give out the same IP address each time and
> configure DNS with the names and IP addresses once and edit
> /etc/resolv.conf once on each box.
You could use the dhcp server options "domain-name" and "domain-name
s
On Thu, May 29, 2003 at 10:51:38PM -0400, Jerry Quinn wrote:
> That's one. You don't have to go out of your way in the simple case
> to get dnsmasq to forward dns requests upstream. It also incorporates
> /etc/hosts into its cache.
Just so I'm clear, the reason it reads /etc/hosts is so that so
Bill Moseley writes:
> On Thu, May 29, 2003 at 07:11:12PM -0400, Jerry Quinn wrote:
> > R Ransbottom writes:
> > >
> > >
> > > > This is great! I put in a wishlist to have dnsmasq read the dhcp
> > > > lease file out of the box. Then dnsmasq will really be plug and
> > > > play.
>
On Thu, May 29, 2003 at 07:11:12PM -0400, Jerry Quinn wrote:
> R Ransbottom writes:
> >
> >
> > > This is great! I put in a wishlist to have dnsmasq read the dhcp
> > > lease file out of the box. Then dnsmasq will really be plug and
> > > play.
> >
> > Since only one dhcp server should
R Ransbottom writes:
>
>
> > This is great! I put in a wishlist to have dnsmasq read the dhcp
> > lease file out of the box. Then dnsmasq will really be plug and
> > play.
>
> Since only one dhcp server should exist on a segment it is a bad
> idea to have such a package work without, a
> This is great! I put in a wishlist to have dnsmasq read the dhcp
> lease file out of the box. Then dnsmasq will really be plug and
> play.
Since only one dhcp server should exist on a segment it is a bad
idea to have such a package work without, at least, forcing the user to
set it up.
-
Jerry Quinn writes:
> Stephen A. Witt writes:
> > On Tue, 27 May 2003, Jerry Quinn wrote:
> > > Hi, all. I have a debian box serving as my firewall/router/dhcp
> > > server. The dhcp does the job fine, except for dns.
>
> Excellent pointer! Except for the fact that it doesn't seem to w
Stephen A. Witt writes:
> On Tue, 27 May 2003, Jerry Quinn wrote:
>
> > Hi, all. I have a debian box serving as my firewall/router/dhcp
> > server. The dhcp does the job fine, except for dns.
> >
> > I'd like to have dns lookups work correctly for my internal network.
> > So is there a si
On Tue, 27 May 2003, Jerry Quinn wrote:
> Hi, all. I have a debian box serving as my firewall/router/dhcp
> server. The dhcp does the job fine, except for dns.
>
> I'd like to have dns lookups work correctly for my internal network.
> So is there a simple means of having my dhcp clients being ab
Quoting Jerry Quinn <[EMAIL PROTECTED]>:
> Jeffrey L. Taylor <[EMAIL PROTECTED]> writes:
> >
> > Setting up DNS takes a couple of hours in one go. Getting around it
> > will take about the same amount of time in smaller chunks. You have
> > three (or more) alternatives:
> >
> > 1) configu
Jerry Quinn wrote:
Thanks for the info.
This is clearly depressing. I was hoping someone had already made it
simple to Do The Right Thing(tm).
Ah, well. I guess I can add fixing a DNS server to work right to the
list of many projects I might get around to doing some day.
Thanks,
Jerry
H
Jeffrey L. Taylor <[EMAIL PROTECTED]> writes:
>
> Setting up DNS takes a couple of hours in one go. Getting around it
> will take about the same amount of time in smaller chunks. You have
> three (or more) alternatives:
>
> 1) configure DHCP server to always give out the same IP address t
On Tue, May 27, 2003 at 11:02:48PM -0400, Jerry Quinn wrote:
> Hi, all. I have a debian box serving as my firewall/router/dhcp
> server. The dhcp does the job fine, except for dns.
>
> I'd like to have dns lookups work correctly for my internal network.
> So is there a simple means of having my
Quoting Jerry Quinn <[EMAIL PROTECTED]>:
> Hi, all. I have a debian box serving as my firewall/router/dhcp
> server. The dhcp does the job fine, except for dns.
>
> I'd like to have dns lookups work correctly for my internal network.
> So is there a simple means of having my dhcp clients being a
Hi, all. I have a debian box serving as my firewall/router/dhcp
server. The dhcp does the job fine, except for dns.
I'd like to have dns lookups work correctly for my internal network.
So is there a simple means of having my dhcp clients being able to
have their names resolve to IP's easily (no
16 matches
Mail list logo
