Maybe I’m misinterpreting, but if your gateway from your ISP is also routing and handing out IPs, this is known as a double NAT and can cause all sorts of weird issues. If you’re going from your ISPs gateway to your own router, their device should be bridged so it acts like a static modem.
post
It sounds like your ubiquity and your ISP router are on the same LAN segment, which is not a good config.
You should never have multiple DHCP servers configured unless you're intentionally split braining your vlan (only ever done that for HA purposes and using half of the pool on each). Im pretty sure you need to have your ISP connected to your cloud gateway, and all of your gear connected to the ubiquity. Your ISP router should only see your ubiquity, and that's likely a good part of the reason you can't see all the DHCP leases on your ubiquity gear.
Were I in your position, I'd probably disconnect everything and slowly reconnect stuff one piece at a time until you trip over what's causing your issue. I doubt this is the case, but you could also have another DHCP server running on something you forgot about causing issues. Seen that many times before when doing small business network overhauls.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DHCP | Dynamic Host Configuration Protocol, automates assignment of IPs when connecting to a network |
| HA | Home Assistant automation software |
| ~ | High Availability |
| IP | Internet Protocol |
| NAT | Network Address Translation |
[Thread #994 for this comm, first seen 12th Jan 2026, 03:05] [FAQ] [Full list] [Contact] [Source code]
The best solution would be to remove the ISP's router from the equation. What ISP do you have? Where do you live? In places like Italy it's trivial to change the router, not so much in France/others
all 8 comments