[Samba] no DNS functionality on second subnet

Rowland penny
Fri, 30 Aug 2019 12:09:36 -0000

On 30/08/2019 12:59, L.P.H. van Belle via samba wrote:
> Ah, you gave the solution yourselve..
>
>> client on "different" subnet:
>>
>>     Host Name . . . . . . . . . . . . : pitter35
>>     Primary Dns Suffix  . . . . . . . :			<<< your missing ..
>>     DNS Suffix Search List. . . . . . : ier.ux.uis.no
>> client on same subnet as DC:
>>
>>     Host Name . . . . . . . . . . . . : geoah
>>     Primary Dns Suffix  . . . . . . . : ier.ux.uis.no
>>     DNS Suffix Search List. . . . . . : ier.ux.uis.no
>>                                         ux.uis.no
> Add Primary Dns Suffix for the other domain.
> Then try again.
>
> Greetz,
>
> Louis
>
>
>
>> -----Oorspronkelijk bericht-----
>> Van: Andreas Habel [mailto:andreas.habel at uis.no]
>> Verzonden: vrijdag 30 augustus 2019 13:51
>> Aan: L.P.H. van Belle
>> Onderwerp: RE: [Samba] no DNS functionality on second subnet
>>
>>> -----Original Message-----
>>> From: samba <samba-bounces at lists.samba.org> On Behalf Of
>> L.P.H. van Belle
>>> via samba
>>> Sent: fredag 30. august 2019 12:20
>>> To: samba at lists.samba.org
>>> Subject: Re: [Samba] no DNS functionality on second subnet
>>>
>>> What for OS is the server and windows clients?
>> DC: Ubuntu 18.04 with samba 4.7.6-Ubuntu
>> Client: W10 1903
>>
>>> The VPN tunnel, are you lowering MTU sizes?
>>> Something like:
>>> -A FORWARD -m policy --pol ipsec --dir in -s 192.168.0.0/24
>> -o eth1 -p tcp
>>> -m tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 1361:1536 -j
>> TCPMSS --set-
>>> mss 1360
>> There is no VPN tunnel.
>>
>>> On the client PC's, have you checkout the windows firewall
>> and are you
>>> allowing the remote subnets.
>> The Windows firewall on the client is currently switched off.
>>
>>> The samba server on the remote site, check if replicatiosn
>> is correct.
>>> Are the "remote" zones in the AD-DC's DNS configured?
>> The A records of the clients from the new subnet are in the
>> same zone as the A records of the clients that are in the
>> DC's subnet. A new reverse lookup zone has been created for
>> the reverse records.
>>
>>
>>> Try adding
>>> option edns0 to resolv.conf
>> It's already there.
>>
>>> So few things more to checkout.
>>>
>>> I also suggest on a pc local and remote.
>>> Run: ipconfig /all
>>> Checkout the primary dns suffix and search suffixes
>> client on "different" subnet:
>>
>>     Host Name . . . . . . . . . . . . : pitter35
>>     Primary Dns Suffix  . . . . . . . :
>>     Node Type . . . . . . . . . . . . : Hybrid
>>     IP Routing Enabled. . . . . . . . : No
>>     WINS Proxy Enabled. . . . . . . . : No
>>     DNS Suffix Search List. . . . . . : ier.ux.uis.no
>>
>> client on same subnet as DC:
>>
>>     Host Name . . . . . . . . . . . . : geoah
>>     Primary Dns Suffix  . . . . . . . : ier.ux.uis.no
>>     Node Type . . . . . . . . . . . . : Hybrid
>>     IP Routing Enabled. . . . . . . . : No
>>     WINS Proxy Enabled. . . . . . . . : No
>>     DNS Suffix Search List. . . . . . : ier.ux.uis.no
>>                                         ux.uis.no

It looks like the OP sent the above directly to Louis and not to the
list and it backs up what I said, this is a dns problem ;-)

Rowland