# Redirection issue after changing the nameserver

**URL:** https://meta.discourse.org/t/redirection-issue-after-changing-the-nameserver/101089
**Category:** Support
**Created:** [November 1, 2018, 8:14pm UTC](https://meta.discourse.org/t/redirection-issue-after-changing-the-nameserver/101089 "2018-11-01T20:14:41Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![JKBaseer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jkbaseer/32/80471_2.png) [@JKBaseer](https://meta.discourse.org/u/JKBaseer)
#### Post date: [November 7, 2018, 3:40pm UTC](https://meta.discourse.org/t/redirection-issue-after-changing-the-nameserver/101089/4 "2018-11-07T15:40:33Z")

</div>

> [@JKBaseer](#):
>
> Redirect single/multiple domain(s) to your Discourse instance

Thanks Stephen. The reason why i want to share it might not be to do with DNS is because [(Superseded) Redirect additional domain(s) to your Discourse instance](https://meta.discourse.org/t/redirect-single-multiple-domain-s-to-your-discourse-instance/18492) according to this link, the redirection setup was done on discourse app.yml and not the DNS setup.

To be exact am sharing here the code in app.yml for the redirection

```
 - file:
        path: /etc/nginx/conf.d/discourse_redirect_1.conf
        contents: |
          server {
            listen 80;
            server_name example.org;
            return 301 $scheme://forum.example.org$request_uri;
          }

```

In this case, is it still nothing to do with app.yml?

---

_[View the full topic](https://meta.discourse.org/t/redirection-issue-after-changing-the-nameserver/101089)._