first is the DNS servers that provide AD name resolution services for the domain. The second is DNS servers that are authoritative name servers for FQDN and provide that type of name resoultuion.
The first part is, that Active Directory must have a DNS server to function properly. This DNS server does not have to be an authorativatie name server for the FQDN. In fact MS recommends you don't use the Internet naming connvention for domain names for a private network. Thus domains have a .local or .lan extension for the domain name. You can replicate Active Directory DNS zones via zone transfers to other DNS servers if you allow it. These can then be used as alternate DNS servers should the first in the list be unavailable. Note: for user login, you need the global catalog role on the alternate DNS server as well as replicated sysvol and netlogon shares. In most instances, network admins restrict zone transfers in an AD environment using the Intergrated mode. Here is a MS Technet series of articles on DNS in Active Directory.
http://technet.microsoft.com/en-us/library/cc776929(WS.10).aspx
just follow the links at the end of the articles.
For authoritative name servers for a FQDN, you again allow zone transfers to other DNS servers, but these DNS servers only provide Internet name to IP resolution for web servers, mail servers or any other publically accessible services. Simply, these DNS servers provide the public IP address associated with a domain name.