# Following the ziti router as lan gateway example **URL:** \ **Category:** General Questions\ **Created:** [September 7, 2022, 12:40am UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735 "2022-09-07T00:40:36Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 7, 2022, 12:40am UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/1 "2022-09-07T00:40:36Z")
I am trying to follow [Using an OpenZiti router as a LAN Gateway](https://www.youtube.com/watch?v=H0qGRBMGNIA&t=1s) but running into error. These are the steps I have taken - 1. Created the router with option -t 2. Enrolled the router ( success ) 3. Started systemd-resolved and symlinked /etc/resolv.conf → /run/systemd/resolve/stub-resolv.conf 4. started router, it came up fine ( tunneler binding mode=host ) Now to use it as LAN Gateway - 5. Modified router config for tunnel binding as followed ```auto listeners: - binding: tunnel options: svcPollRate: 15s resolver: udp://10.10.10.10:53 dnsSvcIpRange: 100.64.0.1/10 lanIf: eth0 ``` restarted the router and it errors out with following message - ```auto [2.650] INFO edge/tunnel/dns.NewDnsServer: dns server running at 10.10.10.10:53 [2.650] INFO edge/tunnel/dns.(*resolver).AddHostname: adding ziti-tunnel.resolver.test = 19.65.28.94 to resolver [2.652] FATAL edge/tunnel/dns.NewDnsServer: system resolver test failed: failed to resolve ziti-tunnel.resolver.test: lookup ziti-tunnel.resolver.test on 127.0.0.53:53: no such host ziti-tunnel runs an internal DNS server which must be first in the host's resolver configuration. On systems that use NetManager/dhclient, this can be achieved by adding the following to /etc/dhcp/dhclient.conf: prepend domain-name-servers 10.10.10.10:53; ``` I tried doing that ( editing /etc/dhcp/dhclient.conf ) but it didnt help. What am I missing here? TIA. ---
**Author:** ![markamind](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/markamind/32/157_2.png) [@markamind](https://openziti.discourse.group/u/markamind)\ **Post date:** [September 7, 2022, 8:46am UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/2 "2022-09-07T08:46:35Z")
> [@av-dev](#): > > `ziti-tunnel.` Do you have port 53 open on TCP and UDP? ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [September 7, 2022, 10:22am UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/3 "2022-09-07T10:22:32Z")
Looks like the self test is using 127.0.0.53 but the message told you to bind on 10.10.10.10. I wonder if there’s already a resolver on that loopback address. Try using 127.0.0.53 in the config and see what happens? If it doesn’t work can you give me the is version you’re using? ---
**Author:** ![rcsoleng](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/rcsoleng/32/842_2.png) [@rcsoleng](https://openziti.discourse.group/u/rcsoleng)\ **Post date:** [September 7, 2022, 6:17pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/4 "2022-09-07T18:17:10Z")
Hi av-dev: the demo was setup on VMs running ubuntu 22.04. Ubuntu uses systems-resolved for name resolution If you are running with similar setup you may have missed these two steps: sudo sh -c ‘echo DNS=10.10.10.10 \>\> /etc/systemd/resolved.conf’ sudo systemctl restart systemd-resolved Which injects the local lan IP in to the system-resolved global resolvers list. ---
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 7, 2022, 6:18pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/5 "2022-09-07T18:18:46Z")
I did that part. And its like chicken-egg situation. If I add that in /etc/systemd/resolved.conf then edge router does not come up ( dns resolution fails ) and if I remove it, edge router prints the message as above. I am doing this on RHEL8 with systemd-resolved as well. ---
**Author:** ![rcsoleng](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/rcsoleng/32/842_2.png) [@rcsoleng](https://openziti.discourse.group/u/rcsoleng)\ **Post date:** [September 7, 2022, 6:20pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/6 "2022-09-07T18:20:39Z")
Did you verify the DNS=10.10.10.10 entry in /etc/systemd/resolved.conf ---
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 7, 2022, 6:20pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/7 "2022-09-07T18:20:48Z")
Although one thing I noticed, when I run resolvectl the eth0 interface does not show DNS in “Current scope” of Link2 ( eth0) ---
**Author:** ![rcsoleng](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/rcsoleng/32/842_2.png) [@rcsoleng](https://openziti.discourse.group/u/rcsoleng)\ **Post date:** [September 7, 2022, 6:24pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/8 "2022-09-07T18:24:40Z")
You should see this in global section if not then DNS entry probably not in /etc/systemd/resolved.conf Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub DNS Servers: 10.10.10.10 ---
**Author:** ![rcsoleng](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/rcsoleng/32/842_2.png) [@rcsoleng](https://openziti.discourse.group/u/rcsoleng)\ **Post date:** [September 7, 2022, 6:28pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/9 "2022-09-07T18:28:33Z")
Ii noticed a typo in our commands doc its missing single quotes around _echo DNS= \>\> /etc/systemd/resolved.conf_ if you copy and pasted it would fail. ---
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 7, 2022, 6:55pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/10 "2022-09-07T18:55:32Z")
yeah I do see it in the “Global” DNS servers ---
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 7, 2022, 7:15pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/11 "2022-09-07T19:15:00Z")
@TheLumberjack If i add 127.0.0.53 in config then edge-router gives following error - ```auto [0.758] FATAL edge/tunnel/dns.NewDnsServer: dns server failed to start: listen udp 127.0.0.53:53: bind: address already in use ``` ---
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 7, 2022, 7:26pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/12 "2022-09-07T19:26:55Z")
> [@rcsoleng](#): > > Did you verify the DNS=10.10.10.10 entry in /etc/systemd/resolved.conf Yes I did and to make sure edge-router comes up I had to add my local DNS servers as subsequent entries so what I have in /etc/systemd/resolved.conf is - DNS=10.10.10.10 10.10.10.11 10.10.10.12 10.10.10.13 ---
**Author:** ![rcsoleng](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/rcsoleng/32/842_2.png) [@rcsoleng](https://openziti.discourse.group/u/rcsoleng)\ **Post date:** [September 7, 2022, 9:32pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/13 "2022-09-07T21:32:13Z")
here is output from newly installed ubuntu 22.04 server with lan ip 10.250.50.78 before and after setting DNS in resolved.conf. As you can see we see the issue that you have prior to setting the DNS= and restarting systemd-resolved but works as expected after. ziggy@testbox:~$ ip add 1: lo: \ mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid\_lft forever preferred\_lft forever inet6 ::1/128 scope host valid\_lft forever preferred\_lft forever 2: ens33: \ mtu 1500 qdisc fq\_codel state UP group default qlen 1000 link/ether 00:0c:29:5d:c7:2a brd ff:ff:ff:ff:ff:ff altname enp2s1 inet 10.250.50.78/24 metric 100 brd 10.250.50.255 scope global dynamic ens33 valid\_lft 84199sec preferred\_lft 84199sec inet6 fe80::20c:29ff:fe5d:c72a/64 scope link valid\_lft forever preferred\_lft forever ziggy@testbox:~$ ziggy@testbox:~$ ziggy@testbox:~$ resolvectl Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (ens33) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 10.250.50.254 DNS Servers: 10.250.50.254 ziggy@testbox:~$ ziggy@testbox:~$ ziggy@testbox:~$ cat /etc/systemd/resolved.conf [Resolve] #DNS= #FallbackDNS= #Domains= #DNSSEC=no #DNSOverTLS=no #MulticastDNS=no #LLMNR=no #Cache=no-negative #CacheFromLocalhost=no #DNSStubListener=yes #DNSStubListenerExtra= #ReadEtcHosts=yes #ResolveUnicastSingleLabel=no ziggy@testbox:~$ ziggy@testbox:~$ ziggy@testbox:~$ sudo ./ziti-router run config.yml * * * An update with v0.26.5 is available for ziti-router v0.25.10 from > **[Release v0.26.5 · openziti/ziti](https://github.com/openziti/ziti/releases/tag/v0.26.5)** > > Release 0.26.5 > What's New > This build has no functional changes, but does have changes to the build workflow, > because github is deprecating certain action runners. See > https://github.blog/changelog/... * * * [0.324] INFO ziti/ziti-router/subcmd.run: {configFile=[config.yml] routerId=[P5xIkiIbE6] build-date=[2022-05-24T19:19:48Z] revision=[a32a117f9472] os=[linux] arch=[amd64] version=[v0.25.10] go-version=[go1.18.2]} starting ziti-router [0.324] WARNING edge/router/internal/edgerouter.(\*Config).LoadConfigFromMap: Invalid heartbeat interval [0] (min: 60, max: 10), setting to default [60] [0.324] INFO fabric/router/forwarder.(\*Faulter).run: started [0.325] INFO fabric/router/forwarder.(\*Scanner).run: started [0.325] INFO fabric/router.(\*Router).showOptions: ctrl = {“OutQueueSize”:4,“MaxQueuedConnects”:1,“MaxOutstandingConnects”:16,“ConnectTimeout”:1000000000,“DelayRxStart”:false,“WriteTimeout”:0} [0.325] INFO fabric/router.(\*Router).showOptions: metrics = {“ReportInterval”:60000000000,“MessageQueueSize”:10} [0.325] INFO fabric/router.(\*Router).initializeHealthChecks: starting health check with ctrl ping initially after 15s, then every 30s, timing out after 15s [0.325] INFO fabric/router.(\*Router).startXlinkDialers: started Xlink dialer with binding [transport] [0.325] INFO edge/router/xgress\_edge.(\*listener).Listen: {address=[tls:0.0.0.0:443]} starting channel listener [0.325] INFO fabric/metrics.GoroutinesPoolMetricsConfigF.func1.1: {maxWorkers=[100] idleTime=[10s] poolType=[pool.listener.xgress\_edge] minWorkers=[1] maxQueueSize=[50]} starting goroutine pool [0.325] INFO fabric/router.(\*Router).startXgressListeners: created xgress listener [edge] at [tls:0.0.0.0:443] [0.325] INFO fabric/router.(\*Router).startXgressListeners: created xgress listener [tunnel] at [0.326] INFO edge/router/xgress\_edge.(\*Acceptor).Run: starting [0.558] INFO fabric/metrics.GoroutinesPoolMetricsConfigF.func1.1: {minWorkers=[0] maxWorkers=[32] maxQueueSize=[1000] idleTime=[30s] poolType=[pool.link.dialer]} starting goroutine pool [0.558] INFO fabric/metrics.GoroutinesPoolMetricsConfigF.func1.1: {maxWorkers=[128] maxQueueSize=[1000] poolType=[pool.route.handler] idleTime=[30s] minWorkers=[0]} starting goroutine pool [0.558] INFO edge/router/fabric.(\*StateManagerImpl).StartHeartbeat: heartbeat starting [0.558] INFO edge/router/xgress\_edge.(\*CertExpirationChecker).Run: waiting 8591h42m56.432572551s to renew certificates [0.559] WARNING edge/tunnel/dns.flushDnsCaches: {error=[exec: “systemd-resolve”: executable file not found in $PATH]} unable to find systemd-resolve in path, consider adding a dns flush to your restart process [0.559] INFO edge/tunnel/dns.NewDnsServer: starting dns server… [0.560] INFO edge/router/handler\_edge\_ctrl.(\*helloHandler).HandleReceive.func1: received server hello, replying [0.630] INFO edge/router/handler\_edge\_ctrl.(\*apiSessionAddedHandler).instantSync: {strategy=[instant]} first api session syncId [cl7s4i676x4uiemh017ju9ie2], starting [0.630] INFO edge/router/handler\_edge\_ctrl.(\*apiSessionSyncTracker).Add: received api session sync chunk 0, isLast=true [0.809] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {linkProtocol=[tls] routerVersion=[v0.25.13] linkId=[4WMo3WUGRhvdEY60KjKyIP] routerId=[pmBQvi6oE6] address=[tls:152.67.235.29:80]} dialing link [0.809] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {routerVersion=[v0.25.13] linkId=[7SSEoeL3dfIp5xpv6oCFnx] routerId=[cuKiosjbE6] address=[tls:150.230.46.39:80] linkProtocol=[tls]} dialing link [1.042] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {routerId=[pmBQvi6oE6] routerVersion=[v0.25.13] linkId=[4WMo3WUGRhvdEY60KjKyIP]} link destination support heartbeats [1.058] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {linkId=[7SSEoeL3dfIp5xpv6oCFnx] routerId=[cuKiosjbE6] routerVersion=[v0.25.13]} link destination support heartbeats [1.272] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {routerVersion=[v0.25.13] linkId=[4WMo3WUGRhvdEY60KjKyIP] routerId=[pmBQvi6oE6]} link destination support heartbeats [1.272] INFO fabric/router.(\*xlinkAccepter).Accept: accepted new link [l/4WMo3WUGRhvdEY60KjKyIP] [1.272] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {routerVersion=[v0.25.13] linkId=[4WMo3WUGRhvdEY60KjKyIP] routerId=[pmBQvi6oE6] address=[tls:152.67.235.29:80] linkProtocol=[tls]} link registered [1.272] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {address=[tls:162354cb-06b0-4953-bc2a-1b10267ad4f4.production.netfoundry.io:6262] linkProtocol=[tls] routerVersion=[v0.25.13] linkId=[5YE7PZL8kHQXS27K47ypF0] routerId=[5xnOn.aTq]} dialing link [1.301] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {linkId=[7SSEoeL3dfIp5xpv6oCFnx] routerId=[cuKiosjbE6] routerVersion=[v0.25.13]} link destination support heartbeats [1.301] INFO fabric/router.(\*xlinkAccepter).Accept: accepted new link [l/7SSEoeL3dfIp5xpv6oCFnx] [1.301] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {linkProtocol=[tls] routerVersion=[v0.25.13] linkId=[7SSEoeL3dfIp5xpv6oCFnx] routerId=[cuKiosjbE6] address=[tls:150.230.46.39:80]} link registered [1.508] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {linkId=[5YE7PZL8kHQXS27K47ypF0] routerId=[5xnOn.aTq] routerVersion=[v0.25.13]} link destination support heartbeats [1.631] INFO edge/router/handler\_edge\_ctrl.(\*apiSessionAddedHandler).applySync: finished sychronizing api sessions [count: 5, syncId: cl7s4i676x4uiemh017ju9ie2, duration: 121.999µs] [1.760] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {linkId=[5YE7PZL8kHQXS27K47ypF0] routerId=[5xnOn.aTq] routerVersion=[v0.25.13]} link destination support heartbeats [1.760] INFO fabric/router.(\*xlinkAccepter).Accept: accepted new link [l/5YE7PZL8kHQXS27K47ypF0] [1.760] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {address=[tls:162354cb-06b0-4953-bc2a-1b10267ad4f4.production.netfoundry.io:6262] linkProtocol=[tls] routerVersion=[v0.25.13] linkId=[5YE7PZL8kHQXS27K47ypF0] routerId=[5xnOn.aTq]} link registered [2.560] INFO edge/tunnel/dns.NewDnsServer: dns server running at 10.250.50.78:53 [2.560] INFO edge/tunnel/dns.(\*resolver).AddHostname: adding ziti-tunnel.resolver.test = 19.65.28.94 to resolver **[2.609] FATAL edge/tunnel/dns.NewDnsServer: system resolver test failed: failed to resolve ziti-tunnel.resolver.test: lookup ziti-tunnel.resolver.test: no such host** **ziti-tunnel runs an internal DNS server which must be first in the host’s** **resolver configuration. On systems that use NetManager/dhclient, this can** **be achieved by adding the following to /etc/dhcp/dhclient.conf:** \*\* prepend domain-name-servers 10.250.50.78:53;\*\* ziggy@testbox:~$ sudo sh -c ‘echo DNS=10.250.50.78 \>\> /etc/systemd/resolved.conf’ ziggy@testbox:~$ ziggy@testbox:~$ ziggy@testbox:~$ cat /etc/systemd/resolved.conf [Resolve] #DNS= #FallbackDNS= #Domains= #DNSSEC=no #DNSOverTLS=no #MulticastDNS=no #LLMNR=no #Cache=no-negative #CacheFromLocalhost=no #DNSStubListener=yes #DNSStubListenerExtra= #ReadEtcHosts=yes #ResolveUnicastSingleLabel=no DNS=10.250.50.78 ziggy@testbox:~$ ziggy@testbox:~$ ziggy@testbox:~$ ziggy@testbox:~$ sudo systemctl restart systemd-resolved.service ziggy@testbox:~$ ziggy@testbox:~$ ziggy@testbox:~$ resolvectl Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub DNS Servers: 10.250.50.78 Link 2 (ens33) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Servers: 10.250.50.254 ziggy@testbox:~$ ziggy@testbox:~$ ziggy@testbox:~$ sudo ./ziti-router run config.yml * * * An update with v0.26.5 is available for ziti-router v0.25.10 from > **[Release v0.26.5 · openziti/ziti](https://github.com/openziti/ziti/releases/tag/v0.26.5)** > > Release 0.26.5 > What's New > This build has no functional changes, but does have changes to the build workflow, > because github is deprecating certain action runners. See > https://github.blog/changelog/... * * * [0.311] INFO ziti/ziti-router/subcmd.run: {go-version=[go1.18.2] configFile=[config.yml] revision=[a32a117f9472] os=[linux] arch=[amd64] routerId=[P5xIkiIbE6] build-date=[2022-05-24T19:19:48Z] version=[v0.25.10]} starting ziti-router [0.311] WARNING edge/router/internal/edgerouter.(\*Config).LoadConfigFromMap: Invalid heartbeat interval [0] (min: 60, max: 10), setting to default [60] [0.311] INFO fabric/router.(\*Router).showOptions: ctrl = {“OutQueueSize”:4,“MaxQueuedConnects”:1,“MaxOutstandingConnects”:16,“ConnectTimeout”:1000000000,“DelayRxStart”:false,“WriteTimeout”:0} [0.311] INFO fabric/router.(\*Router).showOptions: metrics = {“ReportInterval”:60000000000,“MessageQueueSize”:10} [0.311] INFO fabric/router.(\*Router).initializeHealthChecks: starting health check with ctrl ping initially after 15s, then every 30s, timing out after 15s [0.311] INFO fabric/router.(\*Router).startXlinkDialers: started Xlink dialer with binding [transport] [0.311] INFO edge/router/xgress\_edge.(\*listener).Listen: {address=[tls:0.0.0.0:443]} starting channel listener [0.311] INFO fabric/metrics.GoroutinesPoolMetricsConfigF.func1.1: {minWorkers=[1] maxWorkers=[100] idleTime=[10s] maxQueueSize=[50] poolType=[pool.listener.xgress\_edge]} starting goroutine pool [0.311] INFO fabric/router.(\*Router).startXgressListeners: created xgress listener [edge] at [tls:0.0.0.0:443] [0.311] INFO fabric/router.(\*Router).startXgressListeners: created xgress listener [tunnel] at [0.312] INFO fabric/router/forwarder.(\*Faulter).run: started [0.312] INFO fabric/router/forwarder.(\*Scanner).run: started [0.312] INFO edge/router/xgress\_edge.(\*Acceptor).Run: starting [0.582] INFO fabric/metrics.GoroutinesPoolMetricsConfigF.func1.1: {idleTime=[30s] poolType=[pool.link.dialer] maxQueueSize=[1000] minWorkers=[0] maxWorkers=[32]} starting goroutine pool [0.582] INFO fabric/metrics.GoroutinesPoolMetricsConfigF.func1.1: {idleTime=[30s] poolType=[pool.route.handler] minWorkers=[0] maxQueueSize=[1000] maxWorkers=[128]} starting goroutine pool [0.582] INFO edge/router/fabric.(\*StateManagerImpl).StartHeartbeat: heartbeat starting [0.582] INFO edge/router/xgress\_edge.(\*CertExpirationChecker).Run: waiting 8591h39m16.736026379s to renew certificates [0.585] INFO edge/router/handler\_edge\_ctrl.(\*helloHandler).HandleReceive.func1: received server hello, replying [0.586] WARNING edge/tunnel/dns.flushDnsCaches: {error=[exec: “systemd-resolve”: executable file not found in $PATH]} unable to find systemd-resolve in path, consider adding a dns flush to your restart process [0.586] INFO edge/tunnel/dns.NewDnsServer: starting dns server… [0.657] INFO edge/router/handler\_edge\_ctrl.(\*apiSessionAddedHandler).instantSync: {strategy=[instant]} first api session syncId [cl7s4mvpvx50lemh05unarpr5], starting [0.658] INFO edge/router/handler\_edge\_ctrl.(\*apiSessionSyncTracker).Add: received api session sync chunk 0, isLast=true [0.833] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {linkProtocol=[tls] routerVersion=[v0.25.13] linkId=[70Qlj2VeYhzLiODY2pwiZb] routerId=[pmBQvi6oE6] address=[tls:152.67.235.29:80]} dialing link [0.834] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {routerVersion=[v0.25.13] linkId=[4hHaFVrii0Ye5rDnDrmdYW] routerId=[cuKiosjbE6] address=[tls:150.230.46.39:80] linkProtocol=[tls]} dialing link [1.067] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {linkId=[4hHaFVrii0Ye5rDnDrmdYW] routerId=[cuKiosjbE6] routerVersion=[v0.25.13]} link destination support heartbeats [1.076] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {linkId=[70Qlj2VeYhzLiODY2pwiZb] routerId=[pmBQvi6oE6] routerVersion=[v0.25.13]} link destination support heartbeats [1.295] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {routerVersion=[v0.25.13] linkId=[4hHaFVrii0Ye5rDnDrmdYW] routerId=[cuKiosjbE6]} link destination support heartbeats [1.295] INFO fabric/router.(\*xlinkAccepter).Accept: accepted new link [l/4hHaFVrii0Ye5rDnDrmdYW] [1.295] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {routerVersion=[v0.25.13] linkId=[4hHaFVrii0Ye5rDnDrmdYW] routerId=[cuKiosjbE6] address=[tls:150.230.46.39:80] linkProtocol=[tls]} link registered [1.295] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {linkId=[5q2jdteIEC7dEMJO07qBu5] routerId=[5xnOn.aTq] address=[tls:162354cb-06b0-4953-bc2a-1b10267ad4f4.production.netfoundry.io:6262] linkProtocol=[tls] routerVersion=[v0.25.13]} dialing link [1.300] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {linkId=[70Qlj2VeYhzLiODY2pwiZb] routerId=[pmBQvi6oE6] routerVersion=[v0.25.13]} link destination support heartbeats [1.300] INFO fabric/router.(\*xlinkAccepter).Accept: accepted new link [l/70Qlj2VeYhzLiODY2pwiZb] [1.300] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {address=[tls:152.67.235.29:80] linkProtocol=[tls] routerVersion=[v0.25.13] linkId=[70Qlj2VeYhzLiODY2pwiZb] routerId=[pmBQvi6oE6]} link registered [1.532] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {linkId=[5q2jdteIEC7dEMJO07qBu5] routerId=[5xnOn.aTq] routerVersion=[v0.25.13]} link destination support heartbeats [1.658] INFO edge/router/handler\_edge\_ctrl.(\*apiSessionAddedHandler).applySync: finished sychronizing api sessions [count: 5, syncId: cl7s4mvpvx50lemh05unarpr5, duration: 11.085µs] [1.768] INFO fabric/router/handler\_link.(\*bindHandler).BindChannel: {linkId=[5q2jdteIEC7dEMJO07qBu5] routerId=[5xnOn.aTq] routerVersion=[v0.25.13]} link destination support heartbeats [1.768] INFO fabric/router.(\*xlinkAccepter).Accept: accepted new link [l/5q2jdteIEC7dEMJO07qBu5] [1.768] INFO fabric/router/handler\_ctrl.(\*dialHandler).handle |link, linkDialer|: {address=[tls:162354cb-06b0-4953-bc2a-1b10267ad4f4.production.netfoundry.io:6262] linkProtocol=[tls] routerVersion=[v0.25.13] linkId=[5q2jdteIEC7dEMJO07qBu5] routerId=[5xnOn.aTq]} link registered **[2.587] INFO edge/tunnel/dns.NewDnsServer: dns server running at 10.250.50.78:53** \*_[2.588] INFO edge/tunnel/dns.(resolver).AddHostname: adding ziti-tunnel.resolver.test = 19.65.28.94 to resolver_ \*_[2.619] INFO edge/tunnel/dns.(resolver).RemoveHostname: removing ziti-tunnel.resolver.test from resolver_ **[4.652] INFO edge/tunnel/intercept.SetDnsInterceptIpRange: dns intercept IP range: 100.64.0.1 - 100.127.255.254** ---
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 7, 2022, 9:45pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/14 "2022-09-07T21:45:57Z")
Thanks @rcsoleng I will try on another host and see if that makes a difference. Also if the lan ip is a public ip would it make a difference? Since in the end state, I would like to use this edge router as a way to get onto ziti network where others servers from RFC1918 address space would be able to use this router without needing Network Address Translation. ---
**Author:** ![rcsoleng](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/rcsoleng/32/842_2.png) [@rcsoleng](https://openziti.discourse.group/u/rcsoleng)\ **Post date:** [September 7, 2022, 10:01pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/15 "2022-09-07T22:01:02Z")
If you were going to run a public Ip I would suggest using two interface the private one facing your private Lan clients and the public one facing the internet (This is a similar config to most home router/firewalls. Using a public IP would not change the DNS operation discussed above. ---
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 12, 2022, 8:16pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/16 "2022-09-12T20:16:07Z")
@rcsoleng I tried on a diff host and ran into the same problem. Would it be possible for you to do this using CentOS 8 by any chance? I am wondering if this is some behavior difference of systemd-resolved on Ubuntu vs CentOS/RHEL. I am neither able to see Current Scopes: DNS on my network interface nor any DNS Servers for it. I am not sure how I can configure DNS resolver at the network interface level. TIA. ---
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 14, 2022, 12:24am UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/17 "2022-09-14T00:24:41Z")
I was able to configure link level resolver explicitly using ```auto sudo resolvectl dns ``` while having router’s own ip in /etc/systemd/resolved.conf and router came up as intended. ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [September 14, 2022, 12:43am UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/18 "2022-09-14T00:43:30Z")
I’m following along, but I’m not sure, does this mean you got it all figured out now? If not, I was gonna reach out to @rcsoleng and see if he had additional guidance ---
**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\ **Post date:** [September 14, 2022, 12:58am UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/19 "2022-09-14T00:58:11Z")
Getting there 🙂 I was not able to get the router up and running, now with the change mentioned below - > [@av-dev](#): > > I was able to configure link level resolver explicitly using > > ```auto > sudo resolvectl dns > > ``` > > while having router’s own ip in /etc/systemd/resolved.conf and router came up as intended. router is up and running. Now I am following rest of the setup to use this router to talk to my service. ---
**Author:** ![rcsoleng](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/rcsoleng/32/842_2.png) [@rcsoleng](https://openziti.discourse.group/u/rcsoleng)\ **Post date:** [September 14, 2022, 2:16pm UTC](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735/20 "2022-09-14T14:16:25Z")
> [@av-dev](#): > > router is up and running. Now I am following rest of the setup to use this router to talk to my service. Hi av-dev just checking in. Do you have any pending questions/issues or are you ok for now? [Next page](https://openziti.discourse.group/t/following-the-ziti-router-as-lan-gateway-example/735.md?page=2)