![]() Home network routers almost always provide a stub dns server anyway. The almost ideal solution is to have the router provide a dns resolver that supports resolving mdns requests for clients that request these addresses via regular dns. (It does support it for programmatically discovering services inside of an app, but normal web browsers don’t use it.) It also looks to me like android does not support mdns for general domain name resolution. (To have most regular apps use it, you want to install something like Apple’s bonjour service, which is bundled with iTunes and possibly some other apple software for Windows). For example windows only supports it by default in certain senarios. The device in question may not support mdns. It is possible for something to have gone wrong with the docker networking configuration such that mdns packets are making it to the hassio-multicast container. ![]() This could be because of one of the following reaons: Docker networking not correct Your real issue is that the mdns names are not resolving. Setting internal_url merely changes what home-assistant uses if it needs to generate an absolute url for something internal (for example, if sending a url for local media to a chromecast).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |