In a rapidly growing company, we have a number of mostly linux servers (ubuntu and debian ), and we are moving to AD for user management, access control, etc.. I've set a test server up to authenticate against AD using realmd/sssd. As part of this process, following a guide/wizard, the AD server became an authoritative DNS server for our main public domain example.com (I hope I'm saying that correctly, it's new to me). But it created a DNS server for our main domain example.com with an SOA; I think it does this because it needs to send out an SRV record). However, we already have a dns server (using dnsmasq) that we use internally, and it has its own SOA, of course. Our domain internally is our main public domain.
Is this strictly necessary, and if not, how can I configure AD to forward all DNS requests for example.com to our internal nameserver, while still creating and broadcasting the SRV record, which I'm pretty sure is what makes realmd and/or sssd work.