My view: DHCP server and DNS server are L3. If I'm in charge of L3 part of network infrastructure (i.e. address space allocation, perhaps some LAN DNS services[*]), then I'll request to deal with those services exclusively (doesn't matter if it's service running on top of some core router or dedicated server). If L3 part is somebody else's responsibility it's up to them to decide do they want my hand or not. If not, then I just request a handful of addresses for LAN management purpose (if a separate management VLAN exists, then ... it's all mine ).
[*] If there's internal DNS hierarchy to be served, then it's likely it is too complicated for MT's implementation of DNS server, so there'll be a dedicated server (could be some rack-mounted Athom box running linux) and I'll try to (ab)use it for other infastructure-related stuff (e.g. DHCP server) ...
You should absolutely not push to control DNS in a Windows Active Directory environment. Not sure why you would want the headache. DNS is very important for Outlook clients for example. Do you know how to setup the resolution for Autodiscover? There are other topics no doubt too that we don't understand. Your job is to support their services and have everything in place to prove you're not the point of failure. Script the MikroTik to prove their infrastructure failures and become even more trusted.
Thanks for this. I also control and manage the network and specialize in Wi-Fi and do Vo-WiFi designs frequently. I also provide routers, switches, VoIP, APs, etc.... but I stop short of servers,radius or server support. AD/server support puts me too close to users which is not my forte.I manage all aspects of a network. Routers, switches, servers, video, VoIP, and pretty much anything else that gets an IP address.
If there is a real server (or servers) on the network, one or more will be handling DNS, DHCP, and pretty much any other client/server type of service.
Routers are quite capable at routing. That's what I prefer to use them for. The auxiliary services like DNS, DHCP, and anything else on the router are only necessary when a more appropriate host is not available.
Not just for outlook clients, if your DNS is not good in AD setup, it will brake replication, etc. In an AD environment, use Windows for DHCP and DNS, they integrate with each other and serve a much bigger picture than just IP Addressing and Name resolution to browse the web, etc