← Back to team overview

cloud-init team mailing list archive

Re: DNS name resolution not working


Larry Menard <larry.menard@xxxxxxxxx> wrote:
    > ; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.amzn2.5.2 <<>> @
    > microsoft.com ; (1 server found) ;; global options: +cmd;; connection
    > timed out; no servers could be reached

    >    I've also uploaded this VM into AWS S3, imported it into an EC2 AMI
    > and launched an EC2 Instance of it, and the command actually works
    > there.

    >    So then I ran the command on my VMware host (a Windows 10 laptop)
    > and it actually works there too.

    >    So I wonder why only the local copy of the VM seems to be affected?

No idea, but it seems that it's not the VM, it's something about how port-53
is routed (or not) in whatever your "local" VM system is.

Attachment: signature.asc
Description: PGP signature