Skip to main content

How to Setup Local Host Resolution Without DNS

IssueOverview

TheIn probleman Element Enterprise On-Premise environment, hostnames must resolve to the appropriate IP addresses. If you have a proper DNS server with records for these hostnames in theplace, user'sthen words.you Whatwill isbe good to go.

In the customerevent tryingthat toa doDNS or whatserver is not working?available for proper hostname resolution, you may use /etc/hosts and host_aliases. This article will walk you through that.

Formatting:If Useyou bulletchoose pointsto foruse everythis statementmethod, do note that federation outside of your local environment will not be possible. Further, using the mobile applications will not be possible as they must be able to access your environment, which typically requires DNS.

Further, this assumes that you include.are using the single node installer based on microk8s.

EnvironmentSteps

WhatFor function,single process,node products,installations platforms,with etc.microk8s, doesif we were setting up was synapse and element and these ran on the customerlocal havedomain anwith issuethe with?

IP

Formatting:of Use192.168.122.39, bulletwe pointswould forset everythe linefollowing entries in this section./etc/hosts:

Resolution

192.168.122.39 element.local 
192.168.122.39 synapse.local
192.168.122.39 local

What isand the answerfollowing toin thehost_aliases issuein or the steps required to resolve the issue?parameters.yml:

Formatting:

host_aliases:
  This- canip: be"192.168.122.39"
    freehostnames:
      form.

-

Root"element.local" Cause

-

What"synapse.local" is- the"local" root

cause for the issue?

Formatting: This can be free form.