← Back to team overview

cloud-init team mailing list archive

Re: DNS name resolution not working


  Hi Michael.

   It returns:

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.amzn2.5.2 <<>> @
; (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?


On Thu, May 19, 2022 at 7:13 PM Michael Richardson <mcr@xxxxxxxxxxxx> wrote:

> Larry Menard <larry.menard@xxxxxxxxx> wrote:
>     >    The result is the same regardless of what I put in
> /etc/resolv.conf,
>     > even if it is absolutely correct, so I don't think the problem is the
>     > contents of that file... I suspect for whatever reason, it is not
> being
>     > processed at all.
> Does, for instance, "dig @ microsoft.com a" do anything?
> It sounds to me like you have something blocking your outgoing DNS.
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        | network
> architect  [
> ]     mcr@xxxxxxxxxxxx  http://www.sandelman.ca/        |   ruby on
> rails    [

Larry Menard
"Defender of Geese and of All Things Natural"
E-mail: larry.menard@xxxxxxxxx

Follow ups