Congratulation. Big achievement!!
Cees Doets
06-1601 4980
Op 16 jul. 2014 om 15:41 heeft "Anne Claire Pourchasse"
mailto:apourcha...@ikoula.com>> het volgende geschreven:
Hello,
A great news for Ikoula that I would like to share with you all !
Our Ikoula Cloud solution, based on the CloudStac
Dear all,
All our guest VMs are having our virtual router (VR)'s IP address on
/etc/resolv.conf. In the past two weeks, I just realised that the DNS
service on the VR is not working, and doesn't respond to DNS queries from
the DNS clients on the guest VM.
I have tried to stop and start back the V
Have you taken a look at dnsmasq.log in the VR ?
What do you mean with not responding? The addresses are not being resolved
to ip addresses?
On Sun, Jul 20, 2014 at 11:53 AM, Indra Pramana wrote:
> Dear all,
>
> All our guest VMs are having our virtual router (VR)'s IP address on
> /etc/resolv.
Hi Rafael,
Good day to you, and thank you for your reply.
Can't find anything wrong on dnsmasq.log / daemon.log, just some log
entries related to DHCP, nothing on DNS. I masked the IP addresses since
they are public.
===
Jul 20 16:21:51 r-2606-VM dnsmasq[3519]: DHCPDISCOVER(eth0) X.X.X.X
06:62:a
Run trace route from guest vms, the result will yield to the point where packet
drop is happening, could be a network acl rule issue, but tracert command can
lead to some answers.
List running ports as well on VR, do a telnet to dns port on router from guest
vm to verify for its response.
Sant
Good day to you too,
Sure I guess I point a way, so you can start troubleshooting.
1. Check if the VMs can reach the VR.
2. Check if the VMs are really configured to use VR as the DNS server.
3. Change the DNS server to be any other such as 8.8.8.8 and 8.8.4.4
(just to see if there is
Hi Rafael,
Good day to you, and thank you for your reply.
1. Yes, the guest VMs can reach the VR. Able to ping.
64 bytes from X.X.X.2: icmp_req=4 ttl=64 time=2.00 ms
64 bytes from X.X.X.2: icmp_req=5 ttl=64 time=0.291 ms
64 bytes from X.X.X.2: icmp_req=6 ttl=64 time=0.384 ms
^C
--- X.X.X.2 ping
Hi Santhosh,
Good day to you, and thank you for your email.
Traceroute packets seems to be dropped, I think it's by default. See result
below:
# traceroute X.X.X.2
traceroute to X.X.X.2 (X.X.X.2), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
However, I am able to ping, and there i
Do a traceroute to an external domain say google.com from guest vm, as you
mentioned below, both by commenting out vr ip and not, in resolv.conf, you may
see the difference.
"Yes, if I remove or comment out the first nameserver entry for the VR's
IP, and only leaving 8.8.8.8 and 8.8.4.4, guest V
4. May I know how to enable the dnsmasq debug? Any documentation / steps on
how to do it? I believe I have to do it on the VR itself?
Sure you have to do that on VR itself.
You should edit the file /etc/dnsmasq.conf
Now I am not able to access my VR to see which property you should enable.
But, if
Hi,
Yes, if I remove or comment out the first nameserver entry for the VR's
IP, and only leaving 8.8.8.8 and 8.8.4.4, guest VMs will be running fine
and will be able to resolve domains properly."
Are you able to ping the first DNS server IP address that you commented out?
Regards
Vihar K
On Jul
Dear all:
I/O speed of our guest VMs are so slow when uploading or downloading file
from them.
I have tried Basic and Advanced network, but I got the same result.
Our environment is :
CloudStack 4.2.1 + KVM Host(with rhel6.3 running on it).
But if I use CentOS 6.4 instead of rhel
Hi,
Can you check if the VR is able to resolve the domain names by pinging from VR
?
-Sanjeev
-Original Message-
From: Vihar [mailto:vih1...@gmail.com]
Sent: Monday, July 21, 2014 5:43 AM
To: users@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Subject: RE: DNS service on VR not
IIRC, virtio wasn't the default until EL6.4.
--David
On Sun, Jul 20, 2014 at 10:12 PM, evanitsharp wrote:
> Dear all:
> I/O speed of our guest VMs are so slow when uploading or downloading
> file from them.
> I have tried Basic and Advanced network, but I got the same result.
>
> Our
Hi Vihar,
Yes I can.
Looking forward to your reply, thank you.
Cheers.
On Mon, Jul 21, 2014 at 8:13 AM, Vihar wrote:
> Hi,
>
> Yes, if I remove or comment out the first nameserver entry for the VR's
> IP, and only leaving 8.8.8.8 and 8.8.4.4, guest VMs will be running fine
> and will be abl
Hi Rafael,
Can I confirm it's this one?
# For debugging purposes, log each DNS query as it passes through
# dnsmasq.
#log-queries
Looking forward to your reply, thank you.
Cheers.
On Mon, Jul 21, 2014 at 1:59 AM, Rafael Weingartner <
rafaelweingart...@gmail.com> wrote:
> 4. May I know how t
Hi Sanjeev,
Good day to you, and thank you for your reply.
Yes, I can resolve domains without any issues from within the VR itself.
root@r-2606-VM:/etc# ping yahoo.com
PING yahoo.com (98.139.183.24): 56 data bytes
64 bytes from 98.139.183.24: icmp_seq=0 ttl=47 time=250.473 ms
64 bytes from 98.13
Hi ,
I would like you to comment second and third IP address I.e 4.2.2.2 and
8.8.8.8 and uncomment the first IP which is allocated to DNS and try to
resolve the internet. It might be resolving the queries from external DNS
server.
If you are not able to resolve the names from VR, check if the DNS
18 matches
Mail list logo
