The reason that your static IP machines are being given a dynamic IP address
is that the pool of IP address that is being allocated also includes the
static IP address.
Example:
Static IP Address - 192.168.1.10
Dynamic Pool - 192.168.1.8 - 192.168.1.100
The PC realises that is has one static address previously and that it should
have a new dynamic address (make sure that it is not a DHCP client) and
makes a request to the server for the same IP address, which it is then
given. To give it a static IP address you have to move the IP address to
outside of the pool or change the pool.
Example:
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
> 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 filed. Under SuSe i need to set the
> lease file parameter (-lf /etc/dhcpd.leases) manualy , for getting
> it to work. I don´t know, how it is under debian.
>
> Hope that helps a little.
>
> Stefan
>
> > -----Ursprüngliche Nachricht-----
> > Von: Alex Malinovich [mailto:demonbane@;the-love-shack.net]
> > Gesendet: Dienstag, 12. November 2002 07:41
> > An: debuser
> > Betreff: dhcp-dns problem
> >
> >
> > I've been working on setting up dhcp-dns on my system so that
> > I can get
> > automatic name entries from DHCP. I've run into a problem, however.
> > First, on the DHCP side.
> >
> > Some of the computers on the network have static leases set up so that
> > they'll always get the same IP address. Since installing
> > dhcp-dns, they
> > now appear to be getting a dynamic IP along with their static
> > IP, though
> > it is the same IP. While this is not a problem per se, it is
> > clogging up
> > my syslog with lots of repetitive errors. Also, and I'm not
> > sure if this
> > is related to the fact that these machines have static IP's,
> > the dynamic
> > IP's are not getting any hostnames associated with them.
> > These machines
> > are, coincidentally, the only Linux machines on the network
> > and are all
> > running dhclient, so it could be a misconfiguration on my part. Any
> > ideas?
> >
> > The other problem is with the actual DNS updating. As far as
> > I can tell
> > after reading /usr/share/doc/dhcp-dns/README and making sure that
> > everything is set up right (including editing /etc/dhcp-dns.conf), I
> > have everything configured properly. But I'm still not getting any
> > updates in the DNS tables. Unfortunately, I can't seem to find any
> > record of dhcp-dns running or any errors from bind. Any suggestions as
> > to where I might be able to look for these?
> >
> > 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 to me a lot like DHCP with some
> > options being passed. I don't HAVE to have all the machines in my
> > network listed in DNS, I just need to have them SOMEHOW accessible to
> > each other by name instead of just by IP. So if BOOTP (or any other
> > protocol) can handle this for me with a minimum amount of
> > hassle I'd be
> > very happy to give it a shot. TIA for any help.
> >
> > -Alex
> >
> >
> >
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
