Yet another "Challenge failed for domain..."

Help
21

No I missed it (now twice).
On which post?

1 Like
22
1 Like
23

OK I see your point.
Then this should do the trick:

1 Like
24

There's not really anything to replace in the Apache configuration files. I believe the following is happening:

If you omit the ServerName directive from any name-based virtual host, the server will default to a fully qualified domain name (FQDN) derived from the system hostname. This implicitly set server name can lead to counter-intuitive virtual host matching and is discouraged.

From Name-based Virtual Host Support - Apache HTTP Server Version 2.4

I would suggest actually adding the proper ServerName directives in stead of relying on the systems FQDN.

1 Like
25

That would be ideal but may only fix this one vhost.
Replacing all occurrences of the wrong name would also help.

1 Like
26

I'm guessing here @rg305, but I don't think there is anything to change.. All the vhosts have the strange ns1 subdomain which is probably the systems FQDN which is inherited by Apache.

1 Like
27

Hostname for one.

1 Like
28

Ah, with all you meant literally everything on the system :stuck_out_tongue: I can agree with that. But only if it's applicable.

1 Like
29

He no longer owns the other name.
I would say that makes it apply (everywhere).

That is, for whatever reason, now someone else's domain name.
[or maybe I read too much into the "no longer hosted"]

1 Like
30

I think you shouldn't just remove the "e" for every instance, but also look at what you're changing. For example, if the FQDN ns1.medicalxpress.ro doesn't make any sense, you might have succesfully removed the "e" from the previous hostname, but now you have a nonsensical FQDN for your system..

1 Like
31

And that is already the case - LOL
But yeah - two wrongs don't make a right!

1 Like
32

Funny:

medicalxpress.ro.       3600    IN      A       5.2.151.201
medicalxpress.ro.       3600    IN      NS      ns2.medicalexpress.
ro.
medicalxpress.ro.       3600    IN      NS      ns1.medicalexpress.
ro.
; ;  Received 144 bytes from 5.2.151.201#53(ns2.medicalexpress.ro) in
 56 ms

The DNS for the new hostname is operated by the previous?

33

It seems there may have been some "legal" battle over the use of that name.
And now has it without the "e".
But I'm only guessing here.

1 Like
34

Would you rely on your "enemies" DNS system for your own, new website?

Or if OP manages the DNS of the "enemies" website, that's a lot of power.. :thinking:

1 Like
35

He didn't let go of the name.
He merely might not be able to use it for a competitive business.

1 Like
36

Ah, like that, I see. Both are from OP. I thought it was some kind of internal battle within a company or something like that :stuck_out_tongue:

In that case the FQDN of the system is probably fine.

@za_sly I suggest you add a proper ServerName and ServerAlias to your Apache vhost:

ServerName medicalxpress.ro
ServerAlias www.medicalxpress.ro

And see how Apache functions after that.

2 Likes
37

OK, thanks for all the input guys...
Let me explain it a bit more... as it is confusing for me also...
I did host the medicalexpress domain and site on the ns1 and ns2.
Now, the site is hosted externally, I only added a CNAME to the table, to redirect the request to an external server. I still keep, and have control over the domain, as I am still hosting the email server for it...
Then, a second domain (medicalxpress) has been bought and I am hosting it locally. There is a request for https on this domain (medicalxpress)....
So, medicalexpress resolves to my ns server (5.2.151.201) but redirects http traffic to an external server. mail.medicalexpress.ro resolves to the same IP, and it is processed by the local email server.
medicalxpress resolves to the same IP (5.2.151.201) and I want to offer https on it, but not email (yet)...
Phew... this is confusing... :slight_smile:

38

It indeed is, because I still don't get it.. You're saying medicalexpress and medicalxpress are hosted on different servers, right? The first one "remote" and the second one "local"?

If that's the case, how come both hostnames resolve to the same IP address?

2 Likes
39

Yes, medicalexpress and medicalxpress resolve to the same ip/ns.
http traffic to medicalexpress is redirected to an off-site server, via a CNAME.
mail remains local
http traffic to medicalxpress remains local..
If this is not how it should be, or is not correct, tell me what is there to be done to make it right...

1 Like
40

Well, it actually isn't a CNAME but just an A record to your external servers IP address. But that doesn't really matter, as we're interested in your other site.

I would still like to suggest you "clean up" your Apache configuration and add a proper virtualhost with a ServerName directive for your new site, as previously discussed.

1 Like