# Deny access on domain name
**URL:** https://meta.discourse.org/t/deny-access-on-domain-name/52532
**Category:** Self-hosting
**Tags:** hosting
**Created:** [November 5, 2016, 1:07am UTC](https://meta.discourse.org/t/deny-access-on-domain-name/52532 "2016-11-05T01:07:25Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@adamhesim](https://meta.discourse.org/u/adamhesim)
#### Post date: [November 5, 2016, 1:07am UTC](https://meta.discourse.org/t/deny-access-on-domain-name/52532/1 "2016-11-05T01:07:25Z")
Hello,
(please excuse my bad english)
I’ve just setup my instance on a new dedicated server and it seems like Discourse is showing on every domain pointing to my server’s IP.
This is a problem because I think this IP was used by an other site back in time and now when I search “[mysite.com](http://mysite.com)” in Google, there are a lot of results from “[oldsite.com](http://oldsite.com)” which is indeed pointing to my Discourse instance.
How can I redirect users which arrive on the server with [oldsite.com](http://oldsite.com) domain name, or show an error page ? I know how to do this whith Apache vhosts but Docker and RoR server are new for me.
Thank you for your help.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [November 5, 2016, 2:02am UTC](https://meta.discourse.org/t/deny-access-on-domain-name/52532/2 "2016-11-05T02:02:01Z")
https is the only effective / simple answer to this scenario at the moment.
---
### Author:  [@adamhesim](https://meta.discourse.org/u/adamhesim)
#### Post date: [November 6, 2016, 11:54pm UTC](https://meta.discourse.org/t/deny-access-on-domain-name/52532/3 "2016-11-06T23:54:46Z")
Ok, thank you for your help
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 7, 2016, 3:08pm UTC](https://meta.discourse.org/t/deny-access-on-domain-name/52532/4 "2016-11-07T15:08:10Z")
Search for “using apache” to find information about configuring another web server to work with your discourse install.