:
Static IP Address - 192.168.1.10
Dynamic Pool - 192.168.1.20 - 192.168.1.100
Hope that helps
Craig
- Original Message -
From: "Stefan Drees" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 12, 2002 9:31 PM
Subject: Re: dhcp-dns problem
> DN
On Tuesday 12 November 2002 6:40 am, Alex Malinovich wrote:
> Unfortunately, I'm not very familiar with what BOOTP is.
> All I know is that it allows a computer to get an IP address and some
> basic network information.
in my understanding, bootp is mostly usefull for giving a machine an ip
addres
DNS-Updating:
I´m running dhcp-dns on SuSe (switching to debian), do you have
checked if "allow-update { localhost; };" in forward DNS record
of named.conf is set? If so, try running dhcp-dns from command
line to check if there are any errors. Another thing is to check
if the dhcpd.lease file is fi
Alex Malinovich, 2002-Nov-12 00:40 -0600:
> And finally, I keep seeing references to BOOTP while looking around for
> information. Unfortunately, I'm not very familiar with what BOOTP is.
> All I know is that it allows a computer to get an IP address and some
> basic network information. It sounds
On Sat, Sep 08, 2001 at 03:02:54PM -0700, Dean A. Roman wrote:
> For future reference, I was using an alias for the NS name in my
> database records.
yep, you can't use a CNAME for an NS record. like MX records, NS records
can only point at A records.
btw, i strongly recommend using a subdomain f
Craig,
I believe I answered my own questions.
For future reference, I was using an alias for the NS name in my database
records. nsupdate barfs when it encounters this and won't do the update. I was
getting "res_nupdate: res_findzonecut failed (0)" error on stderr when I ran
nsupdate by
Craig,
Another tidbit of info. to help out...
After running the nsupdate command by hand with what dhcp-dns had created,
here is what I got.
There is a "res_findzonecut failed (0)" message. Does this mean anything to
you?
Thanks,
---Dean.
srfs1:/var/lib/dhcp-dns# nsupdate -d ./n
Craig,
I did find this error in /var/log/messages and looked it up, the mails I've
read seem to indicate that the name server can't find this domain?
However, everything(nslookup) seems to work fine. The messages log file is
listed below if you feel like looking at it.
===>>> "Sep 8 0
On Fri, Sep 07, 2001 at 08:47:10PM -0700, Dean A. Roman wrote:
>Will turning this "feature??" off in Win2K allow the dhcp-dns scripts in
> linux to update bind?
>How do I fix the problem of dhcp-dns not updating bind? Is it related to
> the
> win2K "feature??"
Are you saying that the dhc
> Craig Sanders wrote:
>
> > On Fri, Sep 07, 2001 at 08:17:04AM -0700, Dean A. Roman wrote:
> > > I'm a bit confused, and it is probably because I don't totally
> > > understand how the dynamic dns updates work.
> >
> > if the rejected updates are coming from a W2K machine then it has
> > noth
On Fri, Sep 07, 2001 at 08:47:10PM -0700, Dean A. Roman wrote:
> Will turning this "feature??" off in Win2K allow the dhcp-dns scripts
> in linux to update bind?
no, it's unrelated. it'll just stop the w2k clients from attempting to
update the dns server.
> How do I fix the problem of dhcp-dns n
Craig,
Thanks for all the info. It's amazing what Microsoft will try to pass off as
a feature while the whole time opening up your entire DNS structure to the whims
of any user out there.
Anyway, back to the problem at hand:
Will turning this "feature??" off in Win2K allow the dhcp-dns sc
On Fri, Sep 07, 2001 at 08:17:04AM -0700, Dean A. Roman wrote:
> I'm a bit confused, and it is probably because I don't totally
> understand how the dynamic dns updates work.
if the rejected updates are coming from a W2K machine then it has
nothing to do with dhcp-dns. it's a fault with W2K.
On Fri, 7 Sep 2001 10:34:34 -0500, Nathan E Norman wrote:
>> Should update requests be coming from a dhcp client?
>
>Yes. Who else would they come from.
Well, the update requests could ALSO come from the dhcp server itself. Whenever
a DHCP request arrives on the DHCP server it could return an I
On Fri, Sep 07, 2001 at 08:17:04AM -0700, Dean A. Roman wrote:
> Craig,
>
> I'm a bit confused, and it is probably because I don't totally understand
> how the dynamic dns updates work.
>
> 192.168.100.100 is the windows machine that checked out the IP address from
> the dhcp
> server(srfs1-1
Craig,
I'm a bit confused, and it is probably because I don't totally understand how
the dynamic dns updates work.
192.168.100.100 is the windows machine that checked out the IP address from the
dhcp
server(srfs1-192.168.100.20).
Should update requests be coming from a dhcp client?
How is th
On Thu, Sep 06, 2001 at 11:02:00PM -0700, Dean A. Roman wrote:
> Sep 6 15:07:31 srfs1 named[1944]: denied update from [192.168.100.100].1097
> for "mydomain.com"
> Sep 6 15:07:31 srfs1 named[1944]: denied update from [192.168.100.100].1103
> for "100.168.192.in-addr.arpa"
update requests are c
17 matches
Mail list logo
