# Ignition architecture question DEV to PROD

**URL:** <https://forum.inductiveautomation.com/t/ignition-architecture-question-dev-to-prod/70182>\
**Category:** Ignition\
**Created:** [February 22, 2023, 7:14pm UTC](https://forum.inductiveautomation.com/t/ignition-architecture-question-dev-to-prod/70182 "2023-02-22T19:14:10Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [February 22, 2023, 9:13pm UTC](https://forum.inductiveautomation.com/t/ignition-architecture-question-dev-to-prod/70182/10 "2023-02-22T21:13:36Z")

</div>

> [@pturmel](#):
>
> I recommend using a DNS name in the connection URL that resolves to the correct DB for the environment.

That makes a lot of sense 🙂 Our Ignition gateways are hosted on Windows Server 2019. For anyone else that finds this thread, You can add a local DNS name in the `C:\Windows\System32\drivers\etc\hosts` file and use that name in Ignition's DB configuration. Do this on both production and development servers with the correct associated IP for easier gateway exports/imports. Thanks, Phil.

```auto
<db_ip_address_here> my_db_dns_name

```

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-architecture-question-dev-to-prod/70182)._