-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for custom DNS resolutions #19
Comments
hey @dlm31 , can you confirm that you've trying to resolve the "tapo.lan" FQDN from a machine having its DNS server set to the IP address of the HomeAssistant instance hosting the dnsmasq-dhcp addon ? Typically you can run Moreover the config snippet that you provided... it does not look like a valid dnsmasq-dhcp config syntax:
In other words a valid dnsmasq-dhcp config for your case would look like:
|
hey @dlm31 , |
Hi, Not exactly. All those local devices i specify under the dhcp_ip_address_reservations key, do resolve properly, when I try yo resolve their ip from anaother pc on the nerwork. What still does not work is if I try to define oher name resolutions, or override public ones. Regards, |
Ok thanks, that's more clear now what you're asking for. |
Having issues resolving dns names. I've declard a host named "tapo or tapo.lan", but when I try to resolve either tapo or tapo.lan I get unresolved. Trying this configuration with the original dnsmasq works, but not with this addon.
The text was updated successfully, but these errors were encountered: