Quick and Dirty:
typically DNS servers in a DMZ [meaning behind the perimeter firewall and in front of the local network firewall, typically are for authoritative name servers for a FQDN. These authoritative name servers provide public address to FQDN resolution for Internet WhoIs queries. These DNS servers can also provide alias support for the local network in translating a public name to a private name eg .com to a .local
DNS servers behind the local network firewall provide local network name to address resolution for local network queries. Typically in an Active Directory or Directory Services environment.
When the local DNS server can not answer queries they forward that query to other name servers for resolution. Example, a web site using your FQDN .com can't be answered by your internal DNS servers because they can only resolve a private name .local to an address. So it forward those to the Internet root-hint servers. These servers put out a WhoIs query eg. WhoIs .com if your DMZ DNS servers are the authoritative DNS servers for your domain name, they answer the query .com = your public IP address. Therefore the answer to the query is your public IP address. Traffic is then sent to that address over the specific protocol port. example you host your web site .com on a web server in your DMZ. Traffic would be sent to your public IP address over port 80. you forward that port traffic [port 80] through your perimeter router to your web server which will then provide the web page.
So this is why in my original post I asked, are you sure? DNS servers in a DMZ play a role if those DNS servers are the authoritative DNS for your public domain name. They provide name to public address resolution for your FQDN. Without that, no one would know that FQDN domain.com is your public IP address and then send traffic to you such as email.