-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Configuration with self-hosted Unifi application application #63
Comments
Hey @mkoval, unfortunately it does not look like the dockerized version of the unifi controller supports DNS functionality. "UniFi OS" refers to the special operating system available with UniFi's cloud keys/gateways listed here. The USG-Pro-4 lacks this functionality unfortunately. The USG-Pro-4 was released in 2014 and some of its predecessor's have already been marked as EOL, I would recommend upgrading if possible. Alternatively, external-dns supports a "wide range" of dns services. You can get around using an additional dns server on the network like pihole, dnsmasq or powerdns, forwarding your dns from the USG-Pro-4 to the extra dns server. |
I see. You appear to be correct, given that the device greets me over SSH with the following welcome message: "Welcome to EdgeOS on UniFi Security Gateway!" I was mislead because the device is branded as the Unifi Security Gateway, rather than the Edge Security Gateway, but oh well -- it is a decade old now. I notice that the CloudKey+ is listed on that page, which should theoretically be able to manage my existing USG Pro 4. I am not sure if that configuration would work. It might depend on (a) which device the DNS server runs on and (b) whether the DNS feature is enabled when using an older router. Do you know if this configuration would work? If I were to upgrade to a newer router, I would probably opt for the Dream Machine Pro (UDM-Pro). Do you know if the UDM-Pro runs UnifiOS? I assume that it would, but it is listed under UniFi Cloud Gateways rather than the CloudKeys & Gateways page you linked it. It is not clear to me why these are different. Thanks for the quick response and your help. |
I believe it has to be a feature set that is enabled on the device itself. Switching to the CloudKey+ would provide the API, but I fear that the feature set is not implemented on the USG Pro 4. You can check to see by going to
It would. I have tested this with the UDM Pro Max + UXG-MAX (requires separate controller). Other user's have reported similar success with the devices listed on the CloudKeys & Gateways page. Feel free to inquire in the Home Operations discord or here. |
I cant get it working on https://store.ui.com/us/en/category/all-cloud-keys-gateways/products/uxg-max, no option to create local user. |
You'll need to use a controller device with it in order for it to work. The UXG Max does not have a Unifi Controller built into it. It's only the router. On the network console menu go to settings, users and create a user. Select restrict to local access only. |
Thanks for quick response, is it possible to directly interact with unifi network server and add DNS entries on that? |
Unfortunately this project can only exist due to Ubiquiti adding API support for managing DNS records which requires a device that can act as a UniFi controller and has the full UniFi OS. |
@kashalls I think we could make that clearer on the README. |
@onedr0p I understand but this is from my unifi network server running on ip One thing to note, I only have unifi gateway max, I dont have any other unifi device. I dont know how this behaviour will change if I get more unifi devices. Query all DNS records using get Now if we make a post request to To remove entry just send delete verb to same url If incase this is something supported, we would need an env variable to toggle between if its unifi controller or network server. |
Create a new PR #65 |
Bug Description
I am trying to configure
external-dns-unifi-webhook
for my network, which consists of:The first step in the README says to:
I am not sure what this means in my case. The "local user [...] in your UniFi OS" refers to a user on my USG-Pro 4 device (e.g. over SSH), which would not have access to the "Unifi Network appliance."
I tried two different configurations for the
UNIFI_HOST
,username
, andpassword
options:UNIFI_HOST
set to the IP address of my USG-Pro 4 router, withusername
andpassword
set to the SSH login credentials -- configured in the "Device SSH Authentication" section of my Unifi Network Server.UNIFI_HOST
set to the hostname of my Unifi Network Server, with theusername
andpassword
I use to login to its web interface.Neither worked. The USG-Pro 4 configuration succeeds at logging in, but repeatedly fails to query
/proxy/network/v2/api/site/default/static-dns
with an HTTP 404 error. The Unifi Network Server configuration repeatedly fails to query/api/auth/login
with an HTTP 401 error.ExternalDNS Configuration
Helm values
For External DNS Helm chart version 1.14.5, installed in the
network
namespace:Secret
ExternalDNS Logs
With
UNIFI_HOST
set to the USG-PRO-4 hostname:With
UNIFI_HOST
set to the Unifi network application hostname:Webhook Logs
With
UNIFI_HOST
set to the USG-PRO-4 hostname:With
UNIFI_HOST
set to the Unifi network application hostname:UniFiOS Version
4.4.57.5578372
UniFi Network Version
8.3.32
ExternalDNS Version
v0.14.2
Search
Code of Conduct
The text was updated successfully, but these errors were encountered: