Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
HD-Node:Spain
Description
Issue #456 has been reported by Toni Laine.
------------------------------
General Support #456: Filab instance Reverse DNS Lookup problems
<http://techsupport.creatifi.eu/issues/456>
- Author: Toni Laine
- Status: New
- Priority: High
- Assignee: Barcelona Tech Support (Spain&Finland)
- Category: Helsinki Hub (Finland)
- Support Type: FIWARE Lab Infrastructure
- FIWARE Jira ID:
- FIWARE Lab Region: Spain2
Hello,
Is it possible to get DNS properly working on Filab cloud instance? I
installed the instance from a CEP image. It seems the normal DNS checks all
return errors in my case.
$ host 130.206.118.112
Host 112.118.206.130.in-addr.arpa. not found: 3(NXDOMAIN)
$ nslookup 130.206.118.112
Server: 8.8.8.8
Address: 8.8.8.8#53
- server can't find 112.118.206.130.in-addr.arpa.: NXDOMAIN
$ dig x 130.206.118.112
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.5 <<>> -x 130.206.118.112
;; global options: +cmd
;; Got answer:
;; ->>HEADER<< opcode: QUERY, status: NXDOMAIN, id: 44748
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;112.118.206.130.in-addr.arpa. IN PTR
;; AUTHORITY SECTION:
206.130.in-addr.arpa. 1799 IN SOA sun.rediris.es. hostmaster.rediris.es.
2015121600 14400 7200 2592000 7200
;; Query time: 72 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Jun 9 09:56:57 2016
;; MSG SIZE rcvd: 107
The /etc/hosts/ -file seemed to have some HTML page not found -errors in
it, which would point to the installation could not properly set up all
hosts for the cluster? Could you please provide hot the hosts-file should
look after proper installation of CentOS instanse in Filab. Here is the
hosts-file after I removed the access HTML. Unfortunately I do not have the
errors anymore, but they seemed like normal response you get when trying to
wget or curl into a server that cannot be connected.
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.0.6.48 newcep.novalocal
192.168.251.33 eventmore-cep.novalocal
Thanks for your help!
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-creatifi-coaching@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-creatifi-coaching mailing list
Fiware-creatifi-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-creatifi-coaching
[Created via e-mail received from: Lino Valdivia <lino.valdivia@i2cat.net>]
Issue Links
- relates to
-
HELC-1417
FIWARE.Request.Coach.CreatiFI.General Support #456: Filab instance Reverse DNS Lookup problems
-
- Closed
-
Activity
I do not understand very well your problem. You have instantiated a server in which you have configured a DNS service and you have problem with it and you are asking to resolve those problems or to know if it is possible to have it?
It is correct?
Dear Fernando
following the accelerator reply:
*********************
Comment by lino.valdivia@i2cat.net :
Hi Silvio,
Let me follow up with Toni first before you close this ticket please.
Thanks,
Lino
***********************
*********************
Dear Fernando,
following the update from the accelerator
*********************************
Basically the problem was that DNS lookups and reverse-lookups were not working inside the instance created from the cep-r3.3.3-img image. He suspected that it might have something to do with some weird entries that he found in the /etc/hosts file, but even when he removed those entries DNS was still not working for him.
So he is now working on AWS and this doesn't seem to be a blocker for him, but it's something that other Filab users might encounter when deploying this image, so maybe it would be worth investigating a bit prior to closing the ticket?
Even when he removed the errors from the file /etc/hosts, DNS still didn't work properly. Hence he wanted to ask if you have some kind of default settings I could copy into my hosts-file? If you want to test, please install a new instance from cep-r3.3.3-img image and test if 'host' and 'nslookup' return proper answers. If all works properly then perhaps there was some network errors while I was installing my instance and everything did not setup properly.
For now he installed the necessary software to Amazon AWS server, where DNS is not a problem and software works properly.
*********************************
It is not possible to install a DNS instance inside a server due to it will produce IP collisions with external DNS instances and network communication failures in general.
Dear,
you can forward the issue to the FIWARE Spain node
BR