Ooma confuses router's dynamic DNS support...how to fix?

[CharlesW]

Hello,

My router (D-Link DIR-825) has built-in support for various dynamic DNS services. I use DynDNS, and it's always worked great.

Unfortunately, with Ooma between the cable modem and router, the router thinks its external IP address is the Ooma's internal IP address.

Does that make sense? Any ideas on a workaround?

-- Charles

[murphy]

Do what DynDNS recommends and run their client on your computer. Most of the routers with built in DynDNS support never bothered to get their router approved by DynDNS. Yours definitely wasn't because they are using the IP address they see for the WAN port instead of contacting the DynDNS equivalent of whatismyip.com that DynDNS runs specifically for that purpose.

[BCNeuman]

Do what DynDNS recommends and run their client on your computer. Most of the routers with built in DynDNS support never bothered to get their router approved by DynDNS. Yours definitely wasn't because they are using the IP address they see for the WAN port instead of contacting the DynDNS equivalent of whatismyip.com that DynDNS runs specifically for that purpose.

That works fine when your computer is on, but doesn't do much when the devices you wish to contact are embedded devices like home automation controllers, security cameras, etc. Of course it would be better if our routers did the right thing, or alternatively if the Ooma device supported DynDNS itself or even if it assumed only a single device on the "inside" and passed the external IP through to the router.

[koehn]

Just swap the Ooma and the router, so that the hookup is modem -> router -> Ooma. Done, unless you need the Ooma in front of your router, for QOS management.

It's worth noting that you can only manage the Ooma through its "computer" ethernet port.