Unifi AP issues

[pceinc]

We often set them up onsite using a client PC or server that does not have the discovery tool installed. Run an IP scanner, then connect with putty and set the inform url. Done and dusted.

Previously we would set them up on a shop PC then take to client site. We found that if setup on the same subnet as the controller, they would never check in when taken offsite. Even though the inform url was set to a plublic domain pointing to the controller. It's as if the AP knew it was on the same subnet and used a local IP instead. Weird.

 

[Moltuae]

Even though the inform url was set to a plublic domain pointing to the controller. It's as if the AP knew it was on the same subnet and used a local IP instead. Weird.

That sounds to me more like a LAN domain resolution and/or NAT loopback configuration issue. Did you try pinging the domain from inside the LAN to see where it's pointing to?

 

[pceinc]

That sounds to me more like a LAN domain resolution and/or NAT loopback configuration issue. Did you try pinging the domain from inside the LAN to see where it's pointing to?

It's a public subdomain of our regular domain so pinging unifi.mydomain.com resolves to my public IP address. The AP's will adopt and show in the controller and work perfectly while at my office. As soon as I take them to another site, they still work, they just don't connect back to the controller. I've not taken a lot of time to figure out what the issue is. Adopting outside of my office LAN, no issues. It could be that DNS is internal and the AP is resolving directly to the controller VM which is joined to our domain. I'm going to try using a public DNS server to see if it makes a difference.

 

[YeOldeStonecat]

It's a public subdomain of our regular domain so pinging unifi.mydomain.com resolves to my public IP address. The AP's will adopt and show in the controller and work perfectly while at my office. As soon as I take them to another site, they still work, they just don't connect back to the controller. I've not taken a lot of time to figure out what the issue is. Adopting outside of my office LAN, no issues. It could be that DNS is internal and the AP is resolving directly to the controller VM which is joined to our domain. I'm going to try using a public DNS server to see if it makes a difference.

So you created the "unifi" subdomain within your own local DNS...not a public DNS record?

The Unifi controller I built up at RackSpace...I made the "unifi" A-record in our public DNS for one of our nickname domains (not our formal domain name but a shortened one that we use for our services...easier to type). So anywhere you ping that unifi.catspad.org for example...you get a reply from the public IP of the server instance up at Rackspace.