issuing non ad intrigrated DNS servers as secondary dns to clients part of a win server domain
Posted on 2011-03-14
i know this is not best practice but i was wondering if someone can give me a detailed explanation why.
question has been posed by a work colleague and i really didn't have a good enough answer other then "dont do it"
i understand that the client may have trouble resolving dc srv records im guessing it could cause issues with ad/dns replication but i am unable to explain it in a clear fashion.
issue came about with dns in an 2008sbs domain (actual fault was with the forwarder which i resolved)
someone else had looked at it first and implemented a "work around" by adding the router ip to dhcp as the secondary dns. i told him that you should never add a external dns to a server or client in a windows domain. but couldn't give a good enough reason why.
any help clearing this up would be appreciated :)