2.393/2.484/2.649/0.098 ms
> >
> > Looking forward to your reply, thank you.
> >
> > Cheers.
> >
> >
> >
> >
> > On Mon, Jul 21, 2014 at 12:18 PM, Sanjeev Neelarapu <
> > sanjeev.neelar...@citrix.com> wrote:
> >
> > > Hi,
&g
olve 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: us...@cloudstack.apache.org
> Cc: dev@cloudstack.apache.org
> Subject: RE: DNS service on VR n
or 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."
> >
> >
> > Santhosh
> >
> > From: Indra Pramana [in...@sg.or.id
Pramana [in...@sg.or.id]
> Sent: Sunday, July 20, 2014 1:48 PM
> To: us...@cloudstack.apache.org
> Cc: dev@cloudstack.apache.org
> Subject: Re: DNS service on VR not responding
>
> Hi Santhosh,
>
> Good day to you, and thank you for your email.
>
> Traceroute packets seems to
4.4, guest VMs will be running fine
and will be able to resolve domains properly."
Santhosh
From: Indra Pramana [in...@sg.or.id]
Sent: Sunday, July 20, 2014 1:48 PM
To: us...@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: DNS se
t; List running ports as well on VR, do a telnet to dns port on router from
> guest vm to verify for its response.
>
> Santhosh
>
> From: Indra Pramana [in...@sg.or.id]
> Sent: Sunday, July 20, 2014 1:06 PM
> To: us...@cloudstack.apache.org
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
.
Santhosh
From: Indra Pramana [in...@sg.or.id]
Sent: Sunday, July 20, 2014 1:06 PM
To: us...@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: DNS service on VR not responding
Hi Rafael,
Good day to you, and thank you for your reply.
Can't
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.
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
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.
11 matches
Mail list logo