1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Dynamic DNS in RV0xx routers after closing DynDns.org free accounts.

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Sfor, Apr 11, 2014.

  1. Sfor

    Sfor Network Guru Member

    Well. First of all the RV082 v1 DDNS function DynDns.org setting is using the same protocol, as the dnsdynamic.org. The only problem is to redirect the update calls to dnsdynamic.org.

    The RV082 v1 does update DynDns.org accounts through members.dyndns.org address. Ater adding an entry to the local DNS database redirecting members.dyndns.org to 84.45.76.100 I was able to sucessfuly switch the services to dnsdynamic.org.

    A little warning, however. Dnsdynamic.org account allows logins longer than RV082 lets to enter. So, it is wise to use moderate length e-mail adresses with Dnsdynamic.org.

    While this hack works with RV082v1 it will not work with old RV042 and RV016, as they do not have local DNS database function. I was not able to test it with new RV0xx v3 series, but it could be worth a try.
     
  2. Sfor

    Sfor Network Guru Member

    I tried to use the same idea with RV042v1 and RV016v1. I was planning to use a LAN or Internet DNS Proxy acting as DNS server. The proxy would replace the queries to members.dyndns.org with dnsdynamic.org IP. It should work in principle, but it would do me no good, as well. All my dynamic IP installations are working with PPPoE settings. The RV0xx do not allow to enter DNS server IP in such a case. So, the DNS servers are always set to the ones ISP provided.

    Such a workaround could be used in many situations with many types of routers, but in my case it is useless.
     
  3. Sfor

    Sfor Network Guru Member

    The Dnsdynamic.org service is still working, but all the domains it was offering expired. So, this service is useless, now.

    I was playing with afraid.org services, but failed to use them in an RV082 v1. Apparently the RV082 password length and domain length restrictions do not allow to use token needed for IP updates.

    However, I was able to use the old hack with noip.com service. So, after setting the members.dyndns.org to 8.23.224.120, the IP got updated with noip.com service successfuly.
     

Share This Page