Posted on 2008-06-12
I have a DNS Delegation question I want to clarify before I test it out. We have an external BIND DNS namespace called corp.com and our internal AD domain is named lan.corp.com. Users don't really know that they are on the lan.corp.com, so they often put in the FQDN of server.corp.com when it actually resides in lan.corp.com.
So, I was planning on creating two internal DNS Active-Directory Integrated zones called corp.com and lan.corp.com (name of the domain), and create a delegation on the corp.com zone to lan.corp.com zone. My understanding is that this would allow a user to type in server.corp.com and still have DNS resolve this record even though the actual A-host record resides in lan.corp.com. Is this how it should work using a delegation. I believe it should first go to corp.com and it will then see than server.corp.com does not exist, but with the delegation to lan.corp.com, it will automaitcally resolve it since there would be a A-host record for server in lan.corp.com... So, even though they enter a FQDN for a record that is not in corp.com, it will still resolve it in lan.corp.com.