On Nov 2, 2020, at 12:51 PM, Patrick Bégou <Patrick.Begou@xxxxxxxxxxxxxxxxxxxx<mailto:Patrick.Begou@xxxxxxxxxxxxxxxxxxxx>> wrote:
Did you notice the address ? It is not the same IP.
Right - this doesn't look like a web server issue, if the quoted text has no typos. the real question is why doing "host" on the name returns 192.168.1.8 but doing "curl -v" with the name appears to return 198.168.1.8 (note 198, not 192, for the first of the dotted quad) (according to the text below).
Also, I'm not sure that a FQDN in the .com domain should ever resolve to a non-routable address (192,168.x.x). It's at least weird.
Patrick
Le 02/11/2020 à 17:48, Jerry Geis a écrit :
So I have two CentOS 7 machines running.
if I am on my server and I do "curl http://192.168.1.8"; I get data.
If I do "host devgeis.LayeredSolutionsInc.com<http://devgeis.LayeredSolutionsInc.com>" I get the correct address
192.168.1.8
if I goto another machine with CentOS 7.
I do "curl http://192.168.1.8"; I get data.
I do "host devgeis.LayeredSolutionsInc.com<http://devgeis.LayeredSolutionsInc.com>" I get the correct address
*192.*168.1.8
BUT then I do "curl http://devgeis.LayeredSolutionsinc.com"; I get "nothing"
BUt then doing the -v with "curl -v http://devgeis.LayeredSolutionsinc.com";
* About to connect() to devgeis.LayeredSolutionsinc.com<http://devgeis.LayeredSolutionsinc.com> port 80 (#0)
* *Trying 198.*168.1.8...
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
