Roman Rusakov

> if you define dc then it works fine is there a special option for it when launching container? or you use docker exec after it is running? ok I...

Oh, thank you! The problem as I see it, is that we are not able to override this default behaviour for consul client nodes (not server nodes) So have this...

We were having the same issue here https://github.com/kubernetes/dns/issues/387 I've removed `force_tcp` flag from forwarder config in node-localdns but I definetly still see TCP requests and responses to the upstream AWS...

I also have a response from AWS Support team on my case: ``` We have identified that you were using TCP DNS connections to the VPC Resolver. We have identified...

I think the only option may be to add it to the docker file like this https://github.com/aws/session-manager-plugin/issues/12#issuecomment-972880203 - trying to evaluate it, or switch from packer:light to other docker, like...

This worked for my case - but only in fork of this repo, as I'm changing the base Docker image https://github.com/skeggse/docker-packer-ssm/blob/main/Dockerfile

I only started to look into this provider, but I don't understand how the remote git can change if the version is pinned? I assume this is almost default way...

+1 tag plus script would be very usful to implement custom DNS response logic