Stay up to date with the latest from the Knowledge Center. See all new and updated Knowledge Center articles published in the last month and re:Post’s top contributors.
Can I use an external DNS server for name resolution when connecting Amazon Kendra to SharePoint?
Hello.
Can I use an external DNS server for name resolution when connecting Amazon Kendra to SharePoint?
If you look at the following document, Kendra SharePoint Connector can connect to VPC.
https://docs.aws.amazon.com/kendra/latest/dg/data-source-v2-sharepoint.html
So, I am wondering if it is possible to forward to external DNS by using Amazon Route 53 Resolver Outbound Endpoint.
For example, can "sharepoint.com," which is a domain for SharePoint, and "login.microsoftonline.com," which is used for EntraID authentication, be forwarded to an external DNS using a Route53 Resolver Outbound Endpoint?
- Newest
- Most votes
- Most comments
My hunch is yes. Looking at all the connectors available, the documentation states hostname every where. Now if your connecting to an On Prem or VPC instance and your using hostnames, it must use the Resolver and rules in the VPC.
Im going to assume its the same as lambda, it runs in its own VPC and works natively up until you connect it to your own VPC and then you have full control of what it can and cant do including name resolution.
If your resolving a public internet name when connected on the VPC, it will use the default resolver which can resolve xxxx.sharepoint.com without an outbound end point
Yes, you can use an external DNS server for name resolution when connecting Amazon Kendra to SharePoint by using Amazon Route 53 Resolver Outbound Endpoints. This setup forwards DNS queries for specific domains to an external DNS server, that is useful for resolving names not available in internal Route 53 hosted zones
Thank you for your reply! I'll try testing it anyway.
To be sure, you shouldn't need any Route 53 configuration at all. The DNS names you mentioned, login.microsoftonline.com and tenantname.sharepoint.com are available on the public internet both in terms of network connectivity and DNS names. The names can be resolved by any DNS resolver, including the default Route 53 Resolver in your VPC.
Yes, name resolution is actually possible with the default Route53 resolver in the VPC. I didn't write any background in the question, but I'm investigating because there was a request to use an external DNS server for name resolution as a requirement.
Relevant content
AWS OFFICIALUpdated 10 months ago- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
Thank you for your reply! I'll try testing it anyway.