I would like to set up a caching nameserver to meet some requirements in the datacenter. Some of these requirements make me to put this caching nameserver between my servers and AD (e.g. collecting some statistics, managing whole dns things at one spot etc)
When I run some tests like joining a windows server to AD domain while the server is looking to this caching nameserver (lets say 10.10.10.10) and its forwarding (or replying from cache) that domain (lets say my.domain.com) to AD DNS, it actually works but partially.
Server can join AD domain, I can login to server with my domain user, there is no trust issues, I can see the computer object in AD users and computers console, however, there is no DNS record created. I can't get an answer from nslookup. Whats going on during the join process?
The caching name server I use is unbound btw.