[DOCS-11464] "Set up VPC Peering Connection" DNS hostnames and DNS resolution should be required Created: 19/Mar/18  Updated: 04/Jan/23  Resolved: 03/Oct/18

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mark Helmstetter Assignee: Robert Justice (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.atlas.mongodb.com/security-vpc-peering/#optional-enable-dns-hostnames-and-dns-resolution-in-aws


Participants:
Days since reply: 5 years, 47 weeks, 2 days ago
Epic Link: DOCSP-3142
Story Points: 0.2

 Description   

This page:
https://docs.atlas.mongodb.com/security-vpc-peering/#optional-enable-dns-hostnames-and-dns-resolution-in-aws

States "Optional: Enable DNS hostnames and DNS resolution in AWS". This should be Required. Without DNS resolution enabled, traffic will go through the public internet (which would defeat the purpose of creating VPC peering in the first place.)


Generated at Thu Feb 08 08:02:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.