reverse lookup failure during overt engine configuration
--_000_D0F1754F1616Bkfaradayverisigncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, I am trying to configure ovirt(ver 3.5). The fqdn I provide during the step= "Host fully qualified DNS name of this server=94 is reverse resolvable. I = am able to verify that with nslookup of the IP address. But, I keep getting the following error: Host fully qualified DNS name of this server [localhost.localdomain]: xyz.x= yz.xyz.com [ ERROR ] Host name is not valid: The following addresses: 10.xx.xx.xx did = not reverseresolve into xyz.xyz.xyz.com How is ovirt-engine trying to reverse lookup the domain? If I know that, I = could probably fix the issue. Thanks, Kripa =93This message (including any attachments) is intended only for the use of= the individual or entity to which it is addressed, and may contain informa= tion that is non-public, proprietary, privileged, confidential and exempt f= rom disclosure under applicable law or may be constituted as attorney work = product. If you are not the intended recipient, you are hereby notified tha= t any use, dissemination, distribution, or copying of this communication is= strictly prohibited. If you have received this message in error, notify se= nder immediately and delete this message immediately.=94 --_000_D0F1754F1616Bkfaradayverisigncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <FA94EC580C44704B9A0087CA1BCA7549@verisign.com> Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin= e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami= ly: Calibri, sans-serif;"> <div>Hi,</div> <div>I am trying to configure ovirt(ver 3.5). The fqdn I provide during the= step "Host fully qualified DNS name of this server=94 is reverse reso= lvable. I am able to verify that with nslookup of the IP address. </di= v> <div><br> </div> <div>But, I keep getting the following error:</div> <div>Host fully qualified DNS name of this server [localhost.localdomain]: = xyz.xyz.xyz.com</div> <div>[ ERROR ] Host name is not valid: The following addresses: 10.xx.xx.xx= did not reverseresolve into xyz.xyz.xyz.com</div> <div><br> </div> <div>How is ovirt-engine trying to reverse lookup the domain? If I know tha= t, I could probably fix the issue.</div> <div><br> </div> <div>Thanks,</div> <div>Kripa</div> <h5><font color=3D"gray">=93This message (including any attachments) is int= ended only for the use of the individual or entity to which it is addressed= , and may contain information that is non-public, proprietary, privileged, = confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If yo= u are not the intended recipient, you are hereby notified that any use, dis= semination, distribution, or copying of this communication is strictly proh= ibited. If you have received this message in error, notify sender immediately and delete this message immedi= ately.=94 </h5> </font> </body> </html> --_000_D0F1754F1616Bkfaradayverisigncom_--
Hi Kripa, When you set up the oVirt engine it looks like it tries to resolve the fqdn of the machine (which in this case looks like you either haven't updated /etc/sysconfig/network to match the fqdn you provided in the setup or you have and haven't rebooted / reset your network stack). I found the same thing after providing the fqdn it was intended to be in oVirt 3.4 setup (I haven't built a 3.5 engine from scratch, yet) but hadn't updated /etc/sysconfig/network so it tried to resolve against localhost.localdomain. Hope this helps. -C On Saturday, January 31, 2015, Faraday, Kriparam <kfaraday@verisign.com> wrote:
Hi, I am trying to configure ovirt(ver 3.5). The fqdn I provide during the
step "Host fully qualified DNS name of this server” is reverse resolvable. I am able to verify that with nslookup of the IP address.
But, I keep getting the following error: Host fully qualified DNS name of this server [localhost.localdomain]:
xyz.xyz.xyz.com
[ ERROR ] Host name is not valid: The following addresses: 10.xx.xx.xx did not reverseresolve into xyz.xyz.xyz.com
How is ovirt-engine trying to reverse lookup the domain? If I know that, I could probably fix the issue.
Thanks, Kripa
--_000_52DCB4AD9A6B476F935D1F8C51E35774verisigncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi C, Thanks for the response. I did check the /etc/sysconfig/network file. In fact, in this server the 'h= ostname' and 'hostname -f' commands return the same fqdn as well. There must be some other means by which ovirt-3.5 is trying to reverse reso= lve the IP. Still pondering what it is. -Kripa On Jan 31, 2015, at 3:25 AM, Cam Wright <cwright@cuttingedge.com.au<mailto:= cwright@cuttingedge.com.au>> wrote: Hi Kripa, When you set up the oVirt engine it looks like it tries to resolve the fqdn= of the machine (which in this case looks like you either haven't updated /= etc/sysconfig/network to match the fqdn you provided in the setup or you ha= ve and haven't rebooted / reset your network stack). I found the same thing after providing the fqdn it was intended to be in oV= irt 3.4 setup (I haven't built a 3.5 engine from scratch, yet) but hadn't u= pdated /etc/sysconfig/network so it tried to resolve against localhost.loca= ldomain. Hope this helps. -C On Saturday, January 31, 2015, Faraday, Kriparam <kfaraday@verisign.com<mai= lto:kfaraday@verisign.com>> wrote:
Hi, I am trying to configure ovirt(ver 3.5). The fqdn I provide during the st=
ep "Host fully qualified DNS name of this server=94 is reverse resolvable. = I am able to verify that with nslookup of the IP address.
But, I keep getting the following error: Host fully qualified DNS name of this server [localhost.localdomain]: xyz=
.xyz.xyz.com<http://xyz.xyz.xyz.com>
[ ERROR ] Host name is not valid: The following addresses: 10.xx.xx.xx di= d not reverseresolve into xyz.xyz.xyz.com<http://xyz.xyz.xyz.com>
How is ovirt-engine trying to reverse lookup the domain? If I know that, = I could probably fix the issue.
Thanks, Kripa
--_000_52DCB4AD9A6B476F935D1F8C51E35774verisigncom_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body dir=3D"auto"> <div>Hi C,</div> <div>Thanks for the response. </div> <div>I did check the /etc/sysconfig/network file. In fact, in this server t= he 'hostname' and 'hostname -f' commands return the same fqdn as well. = ;</div> <div><br> </div> <div>There must be some other means by which ovirt-3.5 is trying to reverse= resolve the IP. Still pondering what it is.</div> <div><br> -Kripa</div> <div><br> On Jan 31, 2015, at 3:25 AM, Cam Wright <<a href=3D"mailto:cwright@cutti= ngedge.com.au">cwright@cuttingedge.com.au</a>> wrote:<br> <br> </div> <blockquote type=3D"cite"> <div> <p dir=3D"ltr">Hi Kripa,</p> <p dir=3D"ltr">When you set up the oVirt engine it looks like it tries= to resolve the fqdn of the machine (which in this case looks like you eith= er haven't updated /etc/sysconfig/network to match the fqdn you provid= ed in the setup or you have and haven't rebooted / reset your network stack).</p> <p dir=3D"ltr">I found the same thing after providing the fqdn it= was intended to be in oVirt 3.4 setup (I haven't built a 3.5 eng= ine from scratch, yet) but hadn't updated /etc/sysconfig/network = so it tried to resolve against localhost.localdomain.</p> <p dir=3D"ltr">Hope this helps.</p> <p dir=3D"ltr">-C</p> <p dir=3D"ltr">On Saturday, January 31, 2015, Faraday, Kriparam <<a href= =3D"mailto:kfaraday@verisign.com">kfaraday@verisign.com</a>> wrote:<br> </p> <blockquote> <p dir=3D"ltr">><br> > Hi,<br> > I am trying to configure ovirt(ver 3.5). The fqdn I provide during the= step "Host fully qualified DNS name of this server=94 is reverse reso= lvable. I am able to verify that with nslookup of the IP address. <br> ><br> > But, I keep getting the following error:<br> > Host fully qualified DNS name of this server [localhost.localdomain]:<= a href=3D"http://xyz.xyz.xyz.com"> xyz.xyz.xyz.com</a><br> > [ ERROR ] Host name is not valid: The following addresses: 10.xx.xx.xx= did not reverseresolve into<a href=3D"http://xyz.xyz.xyz.com"> xyz.xyz.xyz= .com</a><br> ><br> > How is ovirt-engine trying to reverse lookup the domain? If I know tha= t, I could probably fix the issue.<br> ><br> > Thanks,<br> > Kripa</p> </blockquote> </div> </blockquote> </body> </html> --_000_52DCB4AD9A6B476F935D1F8C51E35774verisigncom_--
Does 'dig fqdn' from the oVirt engine server return the IP address your expecting, and does 'dig -x ipaddress' from the oVirt engine server return the fqdn you're expecting? If not, then it's possibly not the oVirt system that's having the issue and instead may be something in DNS land. It might also be worth checking search domains and name servers in /etc/resolv.conf for sanity. -C On Saturday, January 31, 2015, Faraday, Kriparam <kfaraday@verisign.com> wrote:
Hi C, Thanks for the response. I did check the /etc/sysconfig/network file. In fact, in this server the 'hostname' and 'hostname -f' commands return the same fqdn as well.
There must be some other means by which ovirt-3.5 is trying to reverse resolve the IP. Still pondering what it is.
-Kripa
On Jan 31, 2015, at 3:25 AM, Cam Wright <cwright@cuttingedge.com.au <javascript:_e(%7B%7D,'cvml','cwright@cuttingedge.com.au');>> wrote:
Hi Kripa,
When you set up the oVirt engine it looks like it tries to resolve the fqdn of the machine (which in this case looks like you either haven't updated /etc/sysconfig/network to match the fqdn you provided in the setup or you have and haven't rebooted / reset your network stack).
I found the same thing after providing the fqdn it was intended to be in oVirt 3.4 setup (I haven't built a 3.5 engine from scratch, yet) but hadn't updated /etc/sysconfig/network so it tried to resolve against localhost.localdomain.
Hope this helps.
-C
On Saturday, January 31, 2015, Faraday, Kriparam <kfaraday@verisign.com <javascript:_e(%7B%7D,'cvml','kfaraday@verisign.com');>> wrote:
Hi, I am trying to configure ovirt(ver 3.5). The fqdn I provide during the
step "Host fully qualified DNS name of this server” is reverse resolvable. I am able to verify that with nslookup of the IP address.
But, I keep getting the following error: Host fully qualified DNS name of this server [localhost.localdomain]:
xyz.xyz.xyz.com
[ ERROR ] Host name is not valid: The following addresses: 10.xx.xx.xx did not reverseresolve into xyz.xyz.xyz.com
How is ovirt-engine trying to reverse lookup the domain? If I know that, I could probably fix the issue.
Thanks, Kripa
-- Cam Wright | IT Support Officer / SysAdmin / Trawler of Logs *CUTTING**EDGE* 90 Victoria St, West End, Brisbane, QLD, 4101 T +61 7 3013 6434 | M +61 420 827 007 E cwright@cuttingedge.com.au | W www.cuttingedge.com.au */SYD /BNE /MEL /TYO*
Hi Kripa, When you set up the oVirt engine it looks like it tries to resolve the fqdn of the machine (which in this case looks like you either haven't updated /etc/sysconfig/network to match the fqdn you provided in the setup or you have and haven't rebooted / reset your network stack). I found the same thing after providing the fqdn the engine was intended to be in oVirt 3.4 setup (I haven't built a 3.5 engine from scratch, yet) but hadn't updated /etc/sysconfig/network so it tried to resolve against localhost.localdomain. Hope this helps. -C On Saturday, January 31, 2015, Faraday, Kriparam <kfaraday@verisign.com> wrote:
Hi, I am trying to configure ovirt(ver 3.5). The fqdn I provide during the step "Host fully qualified DNS name of this server” is reverse resolvable. I am able to verify that with nslookup of the IP address.
But, I keep getting the following error: Host fully qualified DNS name of this server [localhost.localdomain]: xyz.xyz.xyz.com [ ERROR ] Host name is not valid: The following addresses: 10.xx.xx.xx did not reverseresolve into xyz.xyz.xyz.com
How is ovirt-engine trying to reverse lookup the domain? If I know that, I could probably fix the issue.
Thanks, Kripa “This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”
-- Cam Wright | IT Support Officer / SysAdmin / Trawler of Logs *CUTTING**EDGE* 90 Victoria St, West End, Brisbane, QLD, 4101 T +61 7 3013 6434 | M +61 420 827 007 E cwright@cuttingedge.com.au | W www.cuttingedge.com.au */SYD /BNE /MEL /TYO*
----- Original Message -----
From: "Kriparam Faraday" <kfaraday@verisign.com> To: users@ovirt.org Sent: Saturday, January 31, 2015 12:52:17 AM Subject: [ovirt-users] reverse lookup failure during overt engine configuration
Hi, I am trying to configure ovirt(ver 3.5). The fqdn I provide during the step "Host fully qualified DNS name of this server” is reverse resolvable. I am able to verify that with nslookup of the IP address.
But, I keep getting the following error: Host fully qualified DNS name of this server [localhost.localdomain]: xyz.xyz.xyz.com [ ERROR ] Host name is not valid: The following addresses: 10.xx.xx.xx did not reverseresolve into xyz.xyz.xyz.com
( BTW, there is a bug here - missing space between 'reverse' and 'resolve'. Now pushed [1] for this to master branch. [1] http://gerrit.ovirt.org/37424 )
How is ovirt-engine trying to reverse lookup the domain? If I know that, I could probably fix the issue.
You can see the code doing this check in /usr/share/ovirt-engine/setup/ovirt_engine_setup/hostname.py You can check the log, mentioned by engine-setup, in /var/log/ovirt-engine/setup, to try and see what failed. Generally, by default, the check above is ran only when configuring all-in-one. It looks up the input fqdn, and for each result address, looks up its reverse mapping (the PTR record) using 'dig -x', and checks that the result is equal to the input fqdn. Best, -- Didi
participants (3)
-
Cam Wright -
Faraday, Kriparam -
Yedidyah Bar David