Do I need to create separate DNS zones for each VLAN?

Question

Domain Name System

There is a server on Windows 2012 R2.
If I plan to split the network into VLANs, do I need to create DNS zones for each VLAN or can I somehow create one common one?

Answer 1

The structure of direct zones depends entirely on your tasks. If you need separate zones for each subnet, create separate zones.
Reverse zones (PTR) will have to be created separately for each subnet.

Answer 2

DNS is just a service that converts a name into an ip address, computers access the dns server already by ip, dns ip is learned either from dhcp or static,
otherwise how would you contact Google's 1.1.1.1 and 8.8.8.8?
But DHCP, yes, it is desirable that each vlan has its own addressing, otherwise you are tormented with routing to L3
For dns to work, it is only necessary that the computer sees the dns server by ip (pinged and had the necessary ports open on the entire route)

Answer 3

If I plan to split the network into VLANs, do I need to create DNS zones for each VLAN, or can I somehow create one common one?

No, it is not necessary, if we mean the name *.firma.loc by DNS zones.
If we are talking about a DNS server, then you can also use 1 DNS server or install additional caching ones, it depends on the structure.
Well, if we are talking about subdomains in AD, then usually this is only necessary for another division that will be serviced by other people, but which should be in a single structure.

Answer 4

A forward zone allows you to create DNS records whose IP addresses are either in the same class A / B / C subnet, even scattered around the world. For example, servers distributing FreeBSD have a name like "www.country.freebsd.org" - the rest is obvious; I recommend to look at this DNS zone for general development.
The reverse zone is created for a network of class A/B/C, by choice. Actually, its syntax, as it were, hints at it a little openly.