Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, November 13, 2018 5:48 PM
We need to create a service record for Jabber that will return a different IP based on which AD site the user is located.
_cisco-uds._tcp.internal.domain
I've tried creating the record _cisco-uds within the _tcp containers in the different sites, different DNSDomain sites and different DNSForest sites to no avail.
Is it possible to have AD DNS return a different IP for a service record based on the AD site the workstation is located?
All replies (7)
Friday, November 16, 2018 7:11 AM âś…Answered
Hello,
With DNS policy you will be able to kind of achieve what you want, it will not really be based on AD Site but on subnet like Eric is saying (If your design is good normally each of your AD site got a subnet attached to it).
DNS polices is server based and not replicated so if you don't control which DNS they will use, you will have to configure it on each DNS server.
Last but not least as you saw in the link of Eric DNS policies is a new feature of Windows server 2016, so if you have 2008 or 2012 DNS they won't be able to use that feature.
Best Regards,
Wednesday, November 14, 2018 7:30 AM
Hi,
Thanks for your question.
Unfortunately, according to DNS policy, your requirement may not be realized.
You can use DNS policy to realize traffic management based on geo-location.
You can refer to:
/en-us/windows-server/networking/dns/deploy/primary-geo-location
Best Regards,
Eric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, November 14, 2018 4:42 PM
Do all DNS servers have to be on Server 2016 for this however?
Thursday, November 15, 2018 9:11 AM
Hi,
Thanks for your reply.
DNS policy is a new in Windows Server 2016.You can use DNS Policy for Geo-Location based traffic management, intelligent DNS responses based on the time of day, to manage a single DNS server configured for split-brain deployment, applying filters on DNS queries, and more.
Best Regards,
Eric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, November 15, 2018 5:30 PM
I guess the question is more that we have 6 DNS servers and only 1 is 2016. So I assume that if a client is talking to a 2008 or 2012 DNS server that the DNS policies would not be in affect?
Friday, November 16, 2018 8:17 AM
Hi,
Just checking in to see if the information provided was helpful.
Please let us know if you would like further assistance.
Best Regards,
Eric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, November 21, 2018 9:09 AM
Hi,
Was your issue resolved?
If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
If no, please reply and tell us the current situation in order to provide further help.
Best Regards,
Eric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].