.. you will need to refresh your leases on your w/s's in order for the SME box to track the system name/ip allocation.
This contrib has worked for me on 30 plus systems without fail!
Hrm. I think this might be a slightly different problem.
I mean, even the dhcp/dns server itself does not resolve (and I'm doing this while logged into that server) :
[x@truth ~]$ host truth
truth.x.x has address 192.168.x.1
[x@truth ~]$ dig truth
; <<>> DiG 9.2.1 <<>> truth
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56927
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;truth. IN A
;; Query time: 1 msec
;; SERVER: 192.168.x.1#53(192.168.x.1)
;; WHEN: Wed Dec 29 04:11:36 2004
;; MSG SIZE rcvd: 23
I used to use dnsmasq to do this when I was running on Fedora Core, and I don't recall the same problem - though I don't often use 'dig'.
I don't know what this issue is, but I don't think it is the cause of my 'woes', so I'll let it drop.
It does seem to have solved the strange hostnames it was giving the clients, so that is it's purpose, I think.
I'll take my printing woes to another thread.
Thanks for solving that problem at least

Max.