* Re: [PVE-User] Virtual Hosts Cannot Resolve Domain Names
@ 2022-04-26 9:25 colonellor
0 siblings, 0 replies; 3+ messages in thread
From: colonellor @ 2022-04-26 9:25 UTC (permalink / raw)
To: Brenda Nyangweso; +Cc: pve-user
On Apr 26, 2022 8:50 AM, Brenda Nyangweso <nyangwesob@aua.ac.ke> 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?
>
Some suggests:
Local DNS cache ?
File host ?
> Kind Regards,
>
> *Brenda *
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PVE-User] Virtual Hosts Cannot Resolve Domain Names
2022-04-26 6:50 Brenda Nyangweso
@ 2022-04-26 7:28 ` nada
0 siblings, 0 replies; 3+ messages in thread
From: nada @ 2022-04-26 7:28 UTC (permalink / raw)
To: Proxmox VE user list
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PVE-User] Virtual Hosts Cannot Resolve Domain Names
@ 2022-04-26 6:50 Brenda Nyangweso
2022-04-26 7:28 ` nada
0 siblings, 1 reply; 3+ messages in thread
From: Brenda Nyangweso @ 2022-04-26 6:50 UTC (permalink / raw)
To: pve-user
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 *
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-04-26 9:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-26 9:25 [PVE-User] Virtual Hosts Cannot Resolve Domain Names colonellor
-- strict thread matches above, loose matches on Subject: below --
2022-04-26 6:50 Brenda Nyangweso
2022-04-26 7:28 ` nada
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox