CentOS7 - Apache Virtual Hosts
-
@Aaron-Studer said:
Can I make it just not resolve?
Again, why? Sure, you can make it error out, point it to nothing. But what is driving you to put in effort to make your site not as nice?
-
@Aaron-Studer said:
Can I make it just not resolve?
You can make it go to a blank page I suppose but why? What are you trying to prevent?
-
@Aaron-Studer said:
Can I make it just not resolve?
Yeah, just make it call either a file which does not exist (it will log in your error log though) or make it return the 404 header and the 404 html document that comes with Apache, that's essentially the same thing as "not resolving," assuming that's what you meant.
-
What s the reasoning of wanting to block the ip address?
-
You have some strong motivation here that you are not sharing. The Google thing isn't valid, that's not how search engines behave. It's not about being good for end users. It's not helpful to you. It's not a best practice. There is something you think you are accomplishing here that you are not willing to share with us. Do you believe this to be some kind of security problem?
-
It just don't make since in my head to have a IP address resolve.... Only a domain. Maybe my head is the issue
-
@Aaron-Studer said:
It just don't make since in my head to have a IP address resolve.... Only a domain. Maybe my head is the issue
Why? Most do. http://216.58.217.142/
-
@Aaron-Studer said:
It just don't make since in my head to have a IP address resolve.... Only a domain. Maybe my head is the issue
It does make sense and that's why I've never heard of someone not wanting it to do this. It's the only logical thing for it to do. And remember, originally, this was the ONLY way we had websites. You are thinking of DNS as more ubiquitous than it should be.
-
@Aaron-Studer said:
It just don't make since in my head to have a IP address resolve.... Only a domain. Maybe my head is the issue
You're only used to HTTP/1.1, but a long time ago in 1.0 it was something to consider, but now you don't have to worry about it. The only scenario is if someone manually does it, in which case you typically just want to return your main page anyway or 404, otherwise it will return the default virtual host if it exists. The way Apache works is, if no host is sent in the GET/POST/PUT/etc request then it will try to find the default virtual host (if virtual host module is enabled) and if that fails it will load whatever is in the default document path.
This is also for reverse compatibility with HTTP/1.0, and while pretty unlikely something will use that, it's such a simple configuration issue why not just support it?
-
Or more importantly.... why put in extra effort to break it?
-
@scottalanmiller said:
There is nothing to know, really. You just tack the configuration on to the end of the httpd.conf file. Single file is the CentOS default. You need no guide, just edit the file.
So just copy the conf file on the end of httpd.conf, and delete the other conf file I created as part of the guide?
-
Looks like I should undo everything from steps 4 and 5
Wish I knew this before I followed this guide... Bummer.
Might just fire up a fresh VM.... At least I am learning
My mistake for blindly following the guide without researching more....
-
@Aaron-Studer said:
@scottalanmiller said:
There is nothing to know, really. You just tack the configuration on to the end of the httpd.conf file. Single file is the CentOS default. You need no guide, just edit the file.
So just copy the conf file on the end of httpd.conf, and delete the other conf file I created as part of the guide?
Yes, that should be all that you need.
-
All fixed! Thanks everyone!!!
