Unable to access local server until I remove the 127.0.0.1 in DNS and refresh it to our local IPs
It's hard to explain in the subject but here is a rundown.
We have a locally hosted Unifi server. Ever since I installed the roaming client I haven't been able to access it unless I remove the 127.0.0.1 IP under DNS on my Mac, which then shows me the correct DNS servers. I apply and quickly refresh the unifi server page and it loads. a few seconds later the DNS on my NIC goes back to 127.0.0.1. If I try and reload the page it will hang again until I apply the workaround to remove the default DNS server. In DNSFilter I have added our local search domains and the IPs of the DNS servers. Any thoughts on how to get this to work correctly (where I don't have to open my network settings, clear the DNS info, apply, and refresh the page each time I want to reload the page). Thanks!
-
Hi Matthew Bartel , thanks for reaching out! It sounds like you're on the right path and this likely has something to do with how the local domains and resolvers are setup, but the team would like to investigate your diagnostic logs to see if anything else shows up. I'm going to create a Support Request for you shortly and if you could reply to the thread with the results from the tool they can review and offer some troubleshooting steps!
0 -
I know this is kind of old, but any update at all to this? We are seeing the same behavior.
-1 -
Hi Billy , happy to help out! I took a look through Matthew's related ticket, and though they had to shelve the issue and didn't fully resolve it with our support team, I believe the same suggestions can work for you.
By examining a HAR capture from an impacted device, the team saw two things that could cause the issue:
- Several related domains the Unifi server is trying to ping that are not immediately obvious, likely hosting Javascript or related CDNs. Try using the browser dev tool to surface these related domains, add them to your local domain list, and see if that fixes it up!
- IPv6 enabled on the network adapter. If it's enabled in your environment, try disabling and restart the agent.
0
Please sign in to leave a comment.
Comments
3 comments