samba - Feb 2017 - gpupdate use wrong url

I use bind on the same maschine as samba (bind_dlz). there is no
additional bind9 in my test network. the default gw (kvm host) do nat.
and bind of this network does know nothink about zone "foo".

I think that is a problem of the windows nslookup.
I installed bind nslookup on the PC just for test and this can resolve
"foo" and "foo."

c:\s_tools
(nslookup win)

nslookup foo

Server:  UnKnown

Address:  192.168.122.7

#############################

nslookup foo.

Server:  UnKnown

Address:  192.168.122.7



Name:    foo

Addresses:  192.168.122.7  # DC1

	  192.168.122.232  # DC2

#############################



c:\s_tools\bind
(nslookup bind)

nslookup foo

Server:		192.168.122.7

Address:	192.168.122.7#53



Name:	foo

Address: 192.168.122.7

Name:	foo

Address: 192.168.122.232

#############################

nslookup foo.

Server:		192.168.122.7

Address:	192.168.122.7#53



Name:	foo

Address: 192.168.122.232

Name:	foo

Address: 192.168.122.7

Am 07.02.2017 um 16:24 schrieb Rowland Penny via samba:
> On Tue, 7 Feb 2017 16:00:30 +0100
> basti via samba <samba at lists.samba.org> wrote:
> 
>> my named.conf look like
>>
>> dlz "foo" {
>>     # For BIND 9.10
>>     database
>> "dlopen
/usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_10.so"; };
>>
>>
>> Am 07.02.2017 um 15:26 schrieb Rowland Penny via samba:
>>> On Tue, 7 Feb 2017 15:04:30 +0100
>>> basti via samba <samba at lists.samba.org> wrote:
>>>
>>>> Windows-IP-Konfiguration
>>>>
>>>>
>>>>
>>>>    Hostname  . . . . . . . . . . . . : wks-1080
>>>>    Prim„res DNS-Suffix . . . . . . . : foo
>>>>    Knotentyp . . . . . . . . . . . . : Hybrid
>>>>
>>>>    IP-Routing aktiviert  . . . . . . : Nein
>>>>
>>>>    WINS-Proxy aktiviert  . . . . . . : Nein
>>>>
>>>>    DNS-Suffixsuchliste . . . . . . . : foo
>>>>
>>>>
>>>>
>>>> Ethernet-Adapter Ethernet 2:
>>>>
>>>>
>>>>
>>>>    Verbindungsspezifisches DNS-Suffix:
>>>>
>>>>    Beschreibung. . . . . . . . . . . : Red Hat VirtIO Ethernet
>>>> Adapter
>>>>
>>>>    Physische Adresse . . . . . . . . : 52-54-00-17-AF-1D
>>>>
>>>>    DHCP aktiviert. . . . . . . . . . : Nein
>>>>
>>>>    Autokonfiguration aktiviert . . . : Ja
>>>>
>>>>    Verbindungslokale IPv6-Adresse  . :
>>>> fe80::14d8:9214:1432:6ff2%8(Bevorzugt)
>>>>
>>>>    IPv4-Adresse  . . . . . . . . . . :
192.168.122.84(Bevorzugt)
>>>>
>>>>    Subnetzmaske  . . . . . . . . . . : 255.255.255.0
>>>>
>>>>    Standardgateway . . . . . . . . . : 192.168.122.1
>>>>
>>>>    DHCPv6-IAID . . . . . . . . . . . : 122835968
>>>>
>>>>    DHCPv6-Client-DUID. . . . . . . . :
>>>> 00-01-00-01-1F-45-EF-7F-52-54-00-17-AF-1D
>>>>
>>>>    DNS-Server  . . . . . . . . . . . : 192.168.122.7
>>>>
>>>>    NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>>>
>>>>
>>>>
>>>> primary dns suffix is the same as in smb.conf
>>>>
>>>> 	netbios name = foo-srv-031
>>>> 	realm = FOO
>>>> 	server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc,
>>>> drepl, winbindd, ntp_signd, kcc, dnsupdate
>>>> 	workgroup = FOO
>>>> 	server role = active directory domain controller
>>>> 	idmap_ldb:use rfc2307 = yes
>>>>
>>>> I know that is not fqdn but i cant change it, for historical
>>>> reason. I don't know what is will break in my LAN to change
the
>>>> domain to a fqdn.
>>>>
>>>> And I think it is a bit overkilled to do all the changes just
for
>>>> the win10 clients.
>>>>
>>>
>>> I think you need to post your named.conf files.
>>> Also using the same name for your dns domain and workgroup
isn't a
>>> good idea.
>>>
>>> Rowland
>>>
>>
> 
> Not the Samba one, your main Bind9 one.
> 
> Rowland
>

On Tue, 7 Feb 2017 16:59:39 +0100
basti via samba <samba at lists.samba.org> wrote:
> I use bind on the same maschine as samba (bind_dlz). there is no
> additional bind9 in my test network. the default gw (kvm host) do nat.
> and bind of this network does know nothink about zone "foo".
If you are using Bind9 on the same machine as you are running the DC
on, there will be a named.conf file (or on debian, there will be
multiple subfiles), can you please post the named.conf files from the
DC in question.

Rowland

Hello Rowland,

here is my named.conf*

named.conf

include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";


named.conf.default-zones

zone "." {
        type hint;
        file "/etc/bind/db.root";
};

zone "localhost" {
        type master;
        file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
        type master;
        file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
        type master;
        file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
        type master;
        file "/etc/bind/db.255";
};


named.conf.local

dlz "foo" {
    # For BIND 9.10
    database "dlopen
/usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_10.so";
};


named.conf.options

options {
        directory "/var/cache/bind";
        dnssec-validation auto;
        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { any; };
        // samba
        // see /var/lib/samba/private/named.txt
        tkey-gssapi-keytab "/var/lib/samba/private/dns.keytab";
        allow-update    { 127.0.0.1/32; };
};


On 07.02.2017 17:27, Rowland Penny via samba wrote:
> On Tue, 7 Feb 2017 16:59:39 +0100
> basti via samba <samba at lists.samba.org> wrote:
> 
>> I use bind on the same maschine as samba (bind_dlz). there is no
>> additional bind9 in my test network. the default gw (kvm host) do nat.
>> and bind of this network does know nothink about zone "foo".
> 
> If you are using Bind9 on the same machine as you are running the DC
> on, there will be a named.conf file (or on debian, there will be
> multiple subfiles), can you please post the named.conf files from the
> DC in question.
> 
> Rowland
> 
> 
>