> if anything goes wrong calls will be coming in.
Interesting approach.
--
Greg J. Zartman, P.E.
Vice-President
Logging Engineering International, Inc.
1243 West 7th Avenue
Eugene, Oregon 97402
541-683-8383fax 541-683-8144
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL
I just came in to work, and the first thing I did was update the dhcp server,
to dhcp-3.0. I will let you know at the end of the day how things went. This
is a high school with 400+ computers, if anything goes wrong calls will be
coming in.
>= Original Message From "Filippo Carletti" <[EMA
> >I'm curious as to how simply installing the DHCP 3.0.??? RPM on a SME
> >machine will get you up and going with DDNS.
>
> I'm not sure, but does WINS have to do anything with this? I saw that the
> e-smith-dhcp-3.0-1.noarch.rpm setup the SME server as the Primary WINS
server
> in dhcpd.
No. Th
> Way back when Filippo first raised the subject, he did mention an
> alternative interface script, which interacted with tinydns rather than
> Bind. At the time I warned him that we were leaning towards using tinydns
> (from the djbdns package), so work which depended on bind9 might become
> orph
> > Do hostnames resolve correctly ?
>
> I'm curious as to how simply installing the DHCP 3.0.??? RPM on a SME
> machine will get you up and going with DDNS. This version of DHCP went
You need to install dhcp-3 from redhat and my e-smith-dhcp-3.
My rpm modifies dhcp and bind configuration to mak
> > Do hostnames resolve correctly ?
>
> I tested this on my 2 computer-home-network. I change the computer name a
> couple of times and rebooted. I was able to ping the machine by its name.
Please, check also reverse resolution (host ip.ad.dr.ess).
Thanks
Ciao,
Filippo
--
Please report bug
> Not a simple task. But I think that it is what Filippo's intention is.
I found it much easier to get DDNS working reliably using BIND8. DDNS
under BIND9 (as of a few months ago) didn't seem to be 100% reliable.
Maybe it was just a config issue on my part, but I couldn't nail down the
prob
>I'm curious as to how simply installing the DHCP 3.0.??? RPM on a SME
>machine will get you up and going with DDNS.
I'm not sure, but does WINS have to do anything with this? I saw that the
e-smith-dhcp-3.0-1.noarch.rpm setup the SME server as the Primary WINS server
in dhcpd.
--
Please repor
> Do hostnames resolve correctly ?
I'm sorry if you get this messages a couple of times but I kept on getting
errors about sending.
I tested this on my 2 computer-home-network. I change the computer name a
couple of times and rebooted. I was able to ping the machine by its name.
I'll test thi
On Sat, 2 Feb 2002, Greg Zartman wrote:
> Maybe I'm not seeing the entire picture here, but seems that one would
> need to insure that the correct version of BIND was installed and that
> both it and DHCP were reconfigured to take advantage of DDNS (not an
> simply task).
Not a simple task. But
> Do hostnames resolve correctly ?
I'm curious as to how simply installing the DHCP 3.0.??? RPM on a SME
machine will get you up and going with DDNS. This version of DHCP went
through a great deal of re-design in the last 8 months or so. As part of
this redesign, a set of new technologies f
> could not find dhcp-3.0-4.i386.rpm so used dhcp-3.0-6.i386.rpm
Rawhide develps really quickly. It happened the same to me, -6 works.
> I got this message below but seems to install fine.
>
> [root@slash DNS3]# rpm -Uvh dhcp-3.0-6.i386.rpm
> Preparing...#
>= Original Message From "Filippo Carletti" <[EMAIL PROTECTED]> =
>I need some testers for ISC DHCP Version 3 on e-smith/Mitel SME5.
>It offers dynamic dns updates natively.
>
>Quick HOWTO
>
>rpm -Uvh
>ftp://ftp.rpmfind.net/linux/rawhide/1.0/i386/RedHat/RPMS/dhcp-3.0-4.i386.rpm
>rpm -Uvh
>
You should install dhcp-3.0 before.
I will add to the require section of the rpm
Ciao,
Filippo
> I was trying to install you package and I got the following error message.
> "
> [root@sme /tmp]# rpm -Uvh e-smith-dhcp-3.0-1.noarch.rpm
> Preparing...
Hi Filippo,
I was trying to install you package and I got the following error message.
"
[root@sme /tmp]# rpm -Uvh e-smith-dhcp-3.0-1.noarch.rpm
Preparing...### [100%]
1:e-smith-dhcp ### [
15 matches
Mail list logo
