The question surrounds using Microsoft DNS or an external (BIND) DNS for use with our internal Active Directory - for use with 365.
We are a BIND shop. My network guy would rather stay that way. When I installed AD, I did not switch to the localhost, but did install DNS (my 365 FastTrack Engineer told me I would need to do that). He later said we could remove Microsoft DNS. We don't know if there are any specific reasons why we would want to move to Microsoft or reasons why we would want to stay other than 'that's the way we've always done it.'
And to make an oddball question even a little more odd...
After installing AD/DNS, the IP address on the primary DNS on the IPv4 properties page was set to 127.0.0.1, which was the first step in the directions (which I skipped). So I don't know why Microsoft would tell me to set it manually to localhost, allow me to skip it, and then set it to localhost anyway. But it did. In my testing, I couldn't perform nslookups, so I changed the DNS to our primary and secondary machines. It appeared to work just fine across the IPv6 connection. We shutoff the IPv6 (we don't use it yet) and it works on the IPv4 connection. If we shutoff the DNS service, it still works on the IPv4 to our local (BIND) DNS hosts.
So here's where I am with all this: we would like to know if there are benefits to switching to Microsoft DNS? I know I read somewhere there are a few things you can't do using an external DNS host. But they seemed like things we wouldn't need to do - which is why I forget what they are. If someone who actually knows and understands 365 has some good reasons for switching to Microsoft DNS, we will. We want to do this right. But, if we are going to stay with BIND, then given what we've done thus far, is there something special we should do in order to use external (BIND) DNS.
- Installed AD/DNS
- Modified IPv4 DNS IP addresses to those of our internal BIND DNS servers
- Shut off DNS Service
If we are staying with BIND, should I just remove the DNS role?