samba - Apr 2013 - Wrong local DNS responses from samba4

I'm running samba4 (compiled via git a few days ago, off 5530cc481653) on
Ubuntu, as an AD DC.

Everything works perfectly with the domain, /except/ that Samba seems to be
returning incorrect DNS entries for the local domain computers -- any
thoughts on how to debug this (or where Samba is getting its IPs from?).


As an example:

router/dhcp/upstream DNS is at 192.168.0.1
samba4 is at 192.168.0.2

aio1.corp.example.com is at 192.168.0.171 (and has been for 48+ hours)

[ask upstream router/DHCP for the IP]
$ dig +short @192.168.0.1 aio1.corp.example.com
192.168.0.171
^^ correct ^^

[ask samba4 for the IP]
$ dig +short @192.168.0.2 aio1.corp.example.com
192.168.0.168
^^ wrong ^^


The samba4 server's resolv.conf is:
nameserver 192.168.0.2
nameserver 192.168.0.1
search corp.example.com

smb.conf contains:
dns forwarder = 192.168.0.1


Any thoughts on how to debug this?


Best,
Nick

Hello,

Am 09.04.2013 02:09, schrieb Nick Semenkovich:
 > As an example:
 >
 > router/dhcp/upstream DNS is at 192.168.0.1
 > samba4 is at 192.168.0.2
 >
 > aio1.corp.example.com is at 192.168.0.171 (and has been for 48+ hours)
 >
 > [ask upstream router/DHCP for the IP]
 > $ dig +short @192.168.0.1 aio1.corp.example.com
 > 192.168.0.171
 > ^^ correct ^^
 >
 > [ask samba4 for the IP]
 > $ dig +short @192.168.0.2 aio1.corp.example.com
 > 192.168.0.168
 > ^^ wrong ^^


- If you look into the zone via the windows DNS snap-in - do you see the 
correct IP for this record there?

- 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?

- 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



Regards,
Marc