Suppose that you've assigned 192.0.2.1 to
www.example1.dom and 192.0.2.2 to
www.example2.dom. Furthermore, suppose that
- example2.dom has control of their own DNS. With this
- config you have put example2.dom into a position where
- they can steal all traffic destined to example1.dom. To
- do so, all they have to do is set www.example2.dom to
- 192.0.2.1. Since they control their own DNS you can't stop them
- from pointing the www.example2.dom record wherever they
+ example1.dom has control of their own DNS. With this
+ config you have put example1.dom into a position where
+ they can steal all traffic destined to example2.dom. To
+ do so, all they have to do is set www.example1.dom to
+ 192.0.2.2. Since they control their own DNS you can't stop them
+ from pointing the www.example1.dom record wherever they
wish.
Requests coming in to 192.0.2.1 (including all those where +
Requests coming in to 192.0.2.2 (including all those where
users typed in URLs of the form
- http://www.example1.dom/whatever) will all be served by
- the example2.dom virtual host. To better understand why
+ http://www.example2.dom/whatever) will all be served by
+ the example1.dom virtual host. To better understand why
this happens requires a more in-depth discussion of how httpd
matches up incoming requests with the virtual host that will
serve it. A rough document describing this