AD needs some specific DNS records for clients to be able to reach a domain controller and authenticate. Specifically, the SRV RR records.
If you tried to use your ISP's DNS servers instead of running DNS on an AD server (or a DNS server set up just for AD), than your clients will not be able to find a domain controller, unless you got your ISP to put in the DNS records your AD domain will need.
And your ISP will say no to this request.
So, here is what you should do. Install DNS on the AD server (run the DNS install DURING the AD install, IMHO). During this, a single DNS zone will be built for your AD domain. It will contain the correct records for the global catalog, domain controllers, LDAP records, etc.
You then configure the DNS server on your AD box to use Forwarders, and put the IP addresses of your ISP's DNS servers in.
Then, you configure your clients to use the IP address of this DNS/AD server as their single DNS server.
When your clients try and resolve SOMETHING.YOURDOMAIN.COM it will resolve using the internal DNS on your AD box. That is good.
Then, when your clients resolve SOMETHING.SOMEWHEREELSE.COM, this request will hit your DNS/AD box, which will Forward it onto the ISP DNS server. The reply will then come back from the ISP, to your server, and then onto the client.
It works.
hope this helps