Use omshell/omapi to set hostname for ddns?
Steve van der Burg
steve.vanderburg at LHSC.ON.CA
Fri May 9 15:07:16 UTC 2008
Hi, I'm using a failover pair of 3.0.5 servers with omshell and am trying to find a way to get a printer that, for some reason, can't work with the servers to do ddns. Other hosts (PCs) on the same subnet are able to get their A records published, but the printer, which is supplying a client-hostname but no uid, doesn't work.
I have scoured the docs and the mailing list, but to no avail. Reading the server docs suggests to me that the ddns TXT and A recs are not getting generated because the printer is not sending a uid, but I don't know if that is correct. So, I either need some way to generate a uid for it via server config, or some way to set a name in its host container (we only allow known MACs, so each machine has a host object dynamically sent to the dhcp server via omshell) that will then get picked up and used for ddns.
I'd like to think that there's a way to make ddns work for this printer, but I'm at a loss for where to turn next, after testing setting 'ddns-hostname' and 'ddns-domainame' in the host object, via omshell (doesn't work).
Can anyone suggest a method that might work?
Thanks.
...Steve
# printer's lease - doesn't work for ddns
lease 10.x.y.a {
starts...
ends...
...
binding state active;
next binding state expired;
hardware ethernet 00:07:4d:2a:69:aa;
client-hostname "test-prn";
}
# typical PC lease on same subnet - does work for ddns
lease 10.x.y.b {
starts...
ends...
...
binding state active;
next binding state expired;
hardware ethernet 00:1a:4b:37:c8:44;
uid "\001\000\032K7\310D";
set ddns-txt = "314cae1b5024961b617eaa038471c542aa";
set ddns-fwd-name = "HVH294.dyn.lhsc.on.ca";
client-hostname "HVH294";
}
--------------------------------------------------------------------------------
This information is directed in confidence solely to the person named above and may contain confidential and/or privileged material. This information may not otherwise be distributed, copied or disclosed. If you have received this e-mail in error, please notify the sender immediately via a return e-mail and destroy original message. Thank you for your cooperation.
More information about the dhcp-users
mailing list