PTR resolve from different servers in the domain?

Question

Domain Name System

There are 2 DCs (different subnets, routes to each other are on the router, of course, everything pings, port 53 is available) - DC1 (192.168.0.100) and DC2 (192.168. of course both DNS servers record 192.168.0.200 and dns: pc1.domain.local

Question: if we are connected via RDP to DC1 and ask him for nslookup about pc1.domain.local and about 192.168.0.200 = everything resolves everything is OK, but if we change the server while on DC1 in the nslookup utility to DC2 - server DC2, then direct entry pc1.domain.local will resolve to 192.168.0.200, and the reverse entry on request 192.168.0.200 does not give pc1.domain.local of course PTR for both subnets is on both controllers, of course it is available. Also, if you go to DC2, then it resolves without problems what belongs to its subnet, but you should specify the DC1 server in nslookup, the direct zone resolves, the reverse is not = Non-existent domain

What kind of miracles and where to look for the problem, root zones are all there are all DCs, redirects also work, DNS servers are registered on DC1 = DC2, DC1 and vice versa on DC2, all of them according to the canon... The replica occurs, there are no errors.

Answer 1

check DNS logs and what is distributed to clients.
and check all zones, with PTR often different fun