As of 5/3/2016 Verizon has made a change to dynamic dns. I am no longer able to update dnydns.com from either the router, or a device behind the router. I reset the HBA and HBR to factory defaults and not change.
I have changed the connection mode from mixed and direct with no change.
If anyone else is able to resolve this, please post the solution.
> As of 5/3/2016 Verizon has made a change to dynamic dns.
That would be a side effect of not having a public facing static IP address.
What is the error dyndns gives?
Does the router’s WAN IP address start with 10 or 100?
I have a public facing IP's on both instances. Fusion does not do NAT'ing.
I am able to port forward to my camera system behind the router. If it was a private IP address, I would not be able to route. I just am not able to update the DNS from either the router, or the linux device. A week ago, it was working on both instances.
I called Verizon 2x today and get stuck on hold.
Ah, that is good news! Verizon appears to have changed how they distribute static IP addresses and when you posted your remarks it made me think LTE Internet (Installed) previously Home Fusion, was part of that change. Thanks for confirming it is not!
I agree this appears to be something Verizon has caused and all I can say is keep pressing the issue with Verizon. Good luck and keep us updated.
Verizon has done this to me on two other occasions since my original post. Surprisingly after I open up a network ticket, it gets resolved. These are tickets that they are suppose to call you back on - yet I never hear a peep from them.