# Fritz!Box no local connection issue - solved **URL:** \ **Category:** Questions & Help\ **Created:** [May 31, 2019, 6:13pm UTC](https://community.homey.app/t/fritz-box-no-local-connection-issue-solved/13872 "2019-05-31T18:13:02Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mapulu](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@mapulu](https://community.homey.app/u/mapulu)\ **Post date:** [May 31, 2019, 6:13pm UTC](https://community.homey.app/t/fritz-box-no-local-connection-issue-solved/13872/1 "2019-05-31T18:13:02Z")
Hello, There is an issue with the Fritz!Box which causes that you can’t connect Homey local (ssl) by a webapp like homeydash. DNS rebinding protection does not allow [homeylocal.com](http://homeylocal.com) to point to your local homey IP. To see if your connection is over the cloud or local go to [https://developer.athom.com/tools/system](https://developer.athom.com/tools/system) To solve this issue you need first the IP of your Homey. That’s for example **192.168.178.123** then you go into your Fritz!Box and enable “advanced view”. Next go to Home Network -\> Network and on the top menu on Network setting. On the bottom of the page you should find a box which called something like “DNS-Rebind-Protection”. There you have to enter the domain which homey uses for local connection. It starts with your IP which is seperated with dashes instead of dots followed with .homey.homeylocal.com In our example it would be **[192-168-178-123.homey.homeylocal.com](http://192-168-178-123.homey.homeylocal.com)** Dont forget to click on apply. If it was successfull you should see now on [https://developer.athom.com/tools/system](https://developer.athom.com/tools/system) Connection Local (Secure). Maybe you need to clear the cache first. Hope this was helpful for some users. ---
**Author:** ![Nick\_Van\_gerwen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nick_van_gerwen/32/43860_2.png) [@Nick\_Van\_gerwen](https://community.homey.app/u/Nick_Van_gerwen)\ **Post date:** [December 10, 2021, 8:48am UTC](https://community.homey.app/t/fritz-box-no-local-connection-issue-solved/13872/2 "2021-12-10T08:48:30Z")
I think I have the same issue and it started when I got Synology DSM 7 on my NAS and decided to start using a local DNS … Unfortunately my ZIGGO connect modem doesn’t have a DNS-REbind-Protection option ☹ But at least I have now something to investigate further! ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [December 10, 2021, 9:02am UTC](https://community.homey.app/t/fritz-box-no-local-connection-issue-solved/13872/3 "2021-12-10T09:02:25Z")
You should be able to find out if this issue is causing your problems by trying to resolve a hostname like `127-0-0-1.homey.homeylocal.com`; it should resolve to `127.0.0.1`, if it doesn’t (or it returns an error), DNS rebind protection is probably active. ---
**Author:** ![Nick\_Van\_gerwen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nick_van_gerwen/32/43860_2.png) [@Nick\_Van\_gerwen](https://community.homey.app/u/Nick_Van_gerwen)\ **Post date:** [December 10, 2021, 12:21pm UTC](https://community.homey.app/t/fritz-box-no-local-connection-issue-solved/13872/4 "2021-12-10T12:21:25Z")
> [@Nick\_Van\_gerwen](#): > > DNS-REbind-Protection ![20211210_100111](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/7/b7badb81cb5035452dea736f4741464fee6ae09d.jpeg) Correct the query was for 192.168.0.240 - which is the reserved ip in the Synology DHCP server for Homey’s MAC-address. Out of curiousity I did a portscan on my homey and port 53 was open, don’t know if that matters… ![IMG-20211210-WA0001](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/c/acfd0580bea19aca0458833acfc6417537a3c68f.jpeg) Anyway I did some experimenting with DNS and my desktop is now able to find homey using the [192-168-0-240.homey.homeylocal.com](http://192-168-0-240.homey.homeylocal.com) name… ![Schermopname (2)](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/5/25cf44213b178b2331dd27415864bcc626fe06bc.jpeg) I’ll repeat the recovery setup later - hope this works… BTW but homey is still reported by [athom](https://developer.athom.com/tools/system) as being offline, just like the app… only portscan and ping seems to work fine. ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [December 10, 2021, 12:26pm UTC](https://community.homey.app/t/fritz-box-no-local-connection-issue-solved/13872/5 "2021-12-10T12:26:54Z")
> [@Nick\_Van\_gerwen](#): > > Out of curiousity I did a portscan on my homey and port 53 was open, don’t know if that matters… Homey runs its own DNS server, for whatever reason… 🤔 ---
**Author:** ![Nick\_Van\_gerwen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nick_van_gerwen/32/43860_2.png) [@Nick\_Van\_gerwen](https://community.homey.app/u/Nick_Van_gerwen)\ **Post date:** [December 10, 2021, 12:41pm UTC](https://community.homey.app/t/fritz-box-no-local-connection-issue-solved/13872/6 "2021-12-10T12:41:36Z")
If I use nslookup and use 192.168.0.240 as the dns server I only get timeouts… ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [December 10, 2021, 12:44pm UTC](https://community.homey.app/t/fritz-box-no-local-connection-issue-solved/13872/7 "2021-12-10T12:44:15Z")
Yes, it’s only for local (software running on Homey) use. Why they chose to expose the port is beyond me.