From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 12EAC94B5 for ; Tue, 26 Apr 2022 09:29:28 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F38D118454 for ; Tue, 26 Apr 2022 09:28:57 +0200 (CEST) Received: from ip1-isp1-algemesi.verdnatura.es (ip1-isp1-algemesi.verdnatura.es [195.77.191.178]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 517AA18449 for ; Tue, 26 Apr 2022 09:28:56 +0200 (CEST) Received: from webmail.verdnatura.es (swarm-worker3.static.verdnatura.es [10.0.2.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ip1-isp1-algemesi.verdnatura.es (Postfix) with ESMTPSA id 7F65CA00A1; Tue, 26 Apr 2022 09:28:54 +0200 (CEST) MIME-Version: 1.0 Date: Tue, 26 Apr 2022 09:28:54 +0200 From: nada To: Proxmox VE user list In-Reply-To: References: User-Agent: Roundcube Webmail/1.4.11 Message-ID: X-Sender: nada@verdnatura.es Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.015 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com, hpe.com] Subject: Re: [PVE-User] Virtual Hosts Cannot Resolve Domain Names X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2022 07:29:28 -0000 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