From: nada <nada@verdnatura.es>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Virtual Hosts Cannot Resolve Domain Names
Date: Tue, 26 Apr 2022 09:28:54 +0200 [thread overview]
Message-ID: <e04dccb6bb5c3e328542434aa37f84ce@verdnatura.es> (raw)
In-Reply-To: <CACeO1tDgtAguQOFLt1Bh4eDRO0Xu43yR_-mZBM2JyrmonPB4Fg@mail.gmail.com>
hi Brenda
a month ago we had similar problem at one Proxmox node.
Virtuals CT/QM with static IP were connected
but CT/QM with DHCP IP were not connected because of DHCP offer timeout.
The problem was with Mellanox netcards which were configured as bond via
LACP (802.3ad).
There was "illegal loopback" error at syslog
Situation here was solved by
* temporal reconfig bond from LACP to active-backup and CT/QM were OK
* check firmware for Mellanox netcard related to HPE Proliant server
*
https://support.hpe.com/hpesc/public/docDisplay?docId=a00100988en_us&docLocale=en_US
* new firmware installation
* network reconfig back to LACP
* testing reboot, QM/CT, connectivity OK
You may check your syslog at proxmox node, at DNS/DHCP server and at
relevant switch
to find out where is your problem
all the best
Nada
On 2022-04-26 08:50, Brenda Nyangweso wrote:
> Hi,
> For some reason, some of my virtual machines seem to have developed a
> DNS
> issue. The host can resolve domain names, but some of the VMs cannot.
> The
> network settings of those that can resolve are similar to those that
> can't.
> Any clues as to what might be happening?
>
> Kind Regards,
>
> *Brenda *
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2022-04-26 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 6:50 Brenda Nyangweso
2022-04-26 7:28 ` nada [this message]
2022-04-26 9:25 colonellor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e04dccb6bb5c3e328542434aa37f84ce@verdnatura.es \
--to=nada@verdnatura.es \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox