Multi vLAN and different domain name resolution not working

[wojciehm]

Multi vLAN and different domain name resolution not working I have following networking setup:

• vLAN 251 with range 192.168.251/24 - DHCP pool 192.168.251.10 - 19.2168.251.254, domain homelab01.local

• vLAN 252 with range 192.168.252/24 - DHCP pool 192.168.252.10 - 19.2168.252.254, domain homelab02.local

• vLAN 253 with range 192.168.253/24 - DHCP pool 192.168.253.10 - 19.2168.253.254, domain kubelab01.local

• vLAN 255 with range 192.168.255/24 - DHCP pool 192.168.255.10 - 19.2168.255.254, domain home.local

• eth0 IP 192.168.255.5 vLAN 255

• eth1 IP 192.168.251.5 vLAN 251

• eth2 IP 192.168.252.5 vLAN 252

• eth3 IP 192.168.253.5 vLAN 253

Zentyal main IP is 192.168.255.5 vLAN 255 and domain home.local.

Each of the respective DHCP pools is configured with its respective domain.

I have full network connectivity and I can ping all configured IP's. From zentyal or home.local I can resolve all home.local dns entries. I can't resolve anything from homelab01.local, homelab02.local. Only kubelab01.local works "for any uknown reason".

All domains are configured as dynamic domain.

Each DHCP range is configured with respective search domain. Example eth0 from vLAN 255.

To Reproduce Steps to reproduce the behavior: Configure zentyal with multiple interfaces and different dns zones. Try to resolve dns entries from different zones.

Expected behavior DNS resolution works.

Screenshots If applicable, add screenshots to help explain your problem.

Zentyal OS (please complete the following information):

• Version: 6.2
• Version of the module which has the bug: unknown
• Modules installed [e.g. DNS, DC, Jabber]

Other OS (please complete the following information):

• OS: macOS, Windows 10
• Version: 11.1 for macOS, Windows 10 latest

[Neustradamus]

@mrPsycho, @unquietwiki, @patphobos, @raskery, @metzgerd, @pakair, @retrofreak83, @jfaubin: What do you think about this ticket?

[raskery]

From a brief reading of the docs (https://doc.zentyal.org/en/dns.html) it looks like Zentyal has a fixed idea about the configuration for the home.local domain and maybe that it is the only internal domain. The documentation only talks about adding external domains not internal domains/sub-domains (.local) so this may not be a supported configuration.

Can you try creating your internal domains as sub-domains of home.local (e.g. homelab1.home.local, homelab2.home.local etc) to see if the scripting sets up the DNS resolution correctly?

[mrPsycho]

i can't say anything. I do not use zentyal in networks with VLANs

[retrofreak83]

I stopped using Zentyal quite some time ago.

[Neustradamus]

@brunolorente, @djoven89: Any news about it?