I just updated samba4 to git master from a few hours ago (69b3d1944501f), and the problem persists.
> - If you look into the zone via the windows DNS snap-in - do you see the > correct IP for this record there? > No, it shows the incorrect record. > > - If you comment out the 'dns forwarder' line in smb.conf (+ restart > samba), what does > > $ dig +short @192.168.0.2 aio1.corp.example.com > tells you now? > The same, incorrect record. > > - Does the following output shows you the correct IP for this record? > $ samba-tool dns query 192.168.0.2 corp.example.com aio1 ALL > Sadly, it's also the incorrect record. With the original configuration (dns forwarder is in smb.conf), it shows: $ /usr/local/samba/bin/samba-tool dns query 192.168.0.2 corp.example.comaio1 ALL -U Administrator Password for [CORP\Administrator]: Name=, Records=1, Children=0 A: 192.168.0.168 (flags=f0, serial=110, ttl=1200) Any thoughts? The machine (aio1) is definitely at .171 (not .168) and has been for days, per the DHCP server logs. Same situation for the ~10 other Windows 8 clients connected to the AD DC. - Nick -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba