Anyone on here familiar with setting up dhcpd to communicate with
bind? Can I pick your brain for a bit? I have, what I believe to be a
working configuration. Clients get IPs from the dhcp server and all.
The mystery is that only some of them will trigger an update to bind,
whereas others don't. More specifically, all the PeeCees (running
WinXP) will trigger a ddns update, whereas none of the Macs (running
various flavors of OS X) will do that.
Anyone have any ideas? PeeCees will, Macs won't. What gives? As a
comparison, here's a PeeCee lease data:
lease 192.168.1.100 {
starts 1 2007/10/08 19:09:59;
ends 1 2007/10/08 23:09:59;
tstp 1 2007/10/08 23:09:59;
binding state active;
next binding state free;
hardware ethernet 00:16:17:17:22:8e;
uid "\001\000\026\027\027\"\216";
set ddns-rev-name = "100.1.168.192.in-addr.arpa.";
set ddns-txt = "314aab3fdf5ed7eb054a0cc63549b31a52";
set ddns-fwd-name = "Freehill.pcraft.com";
client-hostname "Freehill";
}
And here's one from a Mac client:
lease 192.168.1.230 {
starts 1 2007/10/08 19:12:20;
ends 1 2007/10/08 19:14:20;
tstp 1 2007/10/08 19:14:20;
binding state active;
next binding state free;
hardware ethernet 00:05:02:49:af:93;
uid "\001\000\005\002I\257\223";
}
--
W | It's not a bug - it's an undocumented feature.
+--------------------------------------------------------------------
Ashley M. Kirchner <mailto:ashley@xxxxxxxxxx> . 303.442.6410 x130
IT Director / SysAdmin / Websmith . 800.441.3873 x130
Photo Craft Imaging . 3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
