1 Answer
- Newest
- Most votes
- Most comments
0
It turns out that adding the forwarder as described in the link above worked. The part I was missing was joedaws comment, "I would also remove the existing 169.254.169.253 entry so that only the 10.201.0.2 ip address is in the list".
Of course, my IPs are different, but once I removed the preexisting forward so that my x.x.x.2 IP was the only one in the list (I did this for both of the AD DNS servers) the instance was discoverable by SSM.
So, I would make a minor change to the list that saugy wrote:
- On a domain joined windows instance, log in with AD domain Admin user
- Open DNS manager
- Connect to one of the DNS IP addresses for the AWS AD
- Select forwarders
- Add VPCs DNS IP
- Remove the existing IP (so you VPCs IP is the only one)
- Click Apply
- Repeat from step 3 with the other DNS IP address for the AWS AD
Also, as mentioned in the other post. This only has to be done once and the settings persist in the AD DNS.
answered 3 years ago
Relevant content
- Accepted Answerasked 2 months ago
- Accepted Answerasked 4 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago