http://bugzilla.suse.com/show_bug.cgi?id=944866
http://bugzilla.suse.com/show_bug.cgi?id=944866#c6
--- Comment #6 from Bruno Friedmann ---
David, I don't run the erase, not knowing if it cause any troubles.
The servers which I have access are all production ;-)
Yesterday I discover another things, one network has still some xp32 vm running
and thoses are correctly resolved
22910 chm g_w-domusr loulou-xp32 (ipv4:192.168.50.167:1026)
NT1
xp or win7 are all sharing the same infrastructure, where dhcp leases are all
static reservation for the windows 7 workstation and it is the dchp server
which create the dns name.
with this kind of configuration
host test2017 {
hardware ethernet e8:40:f2:0a:13:78;
fixed-address 192.168.50.250;
ddns-hostname test2017;
}
the name is correctly registered in the dynamic zone, and works
dig test2017
test2017.disney.interne. 3600 IN A 192.168.50.250
dig -x 192.168.50.250
250.50.168.192.in-addr.arpa. 3600 IN PTR test2017.disney.interne.
Now the xp workstation get a free dynamic lease, but the dns is registered the
same way and also name resolution works identically.
I was still not able to understand why in the tdb it fail for the win7 and work
for xp32 for example.
I can provide you whatever information you need to have.
--
You are receiving this mail because:
You are on the CC list for the bug.