Does anybody know how can I update a top domain for the DynDNS service?
I am using my own domain name, which is being handled by DynDNS - btw, it's a little frustrating that I had to transfer it from no-ip because Cisco only supports DynDNS.
So, going to the Dynamic DNS configuration page I select: DynDNS.org and for the host name I have three fields. The documentation sais:
The problem is that I don't want to update a hostname but the whole domain (e.g. mydomain.net not gateway.mydomain.net).
- leaving the first field empty ->error, cannot save
- using * for the first field - saves but gives the following error: No internet connection or DDNS service is disabled
- using @ for the first field - saves but gives the following error: No internet connection or DDNS service is disabled
I uploaded three images:
1. Working fine with host = gateway
2.Not being able to save without host name:
3. Not working if using host name = * or @
Btw, I should have mentioned I am using the latest firmware: Firmware Version:v1.1.1.06 (2013-12-06, 11:02:37)
Thanks for taking the time,
That is very unusual, I looked at the interface of all of the other SMB routers except the RV0xx series and none of them have three spaces to enter the host name. I would guess that this is something that was added to the RV320 and RV325 only.
I recommend that you contact support and open a case for this issue. That way a feature request can be added to change the firmware so that the DDNS address can be entered correctly in one space.
If you contact support, please reference this thread.
Unfortunately I'm a simple end user that hasn't purchased support from Cisco so it seems I cannot file a case.
Thank you for your help Marty,
Phone and Chat Support is included for the first year after purchase. Hours are 9am-6pm M-F your time. After the first year you can get support for another 3 years by purchasing a contract.
Thanks! I didn't know that. I filed a case with the support people.
They didn't seem to know that you can have your own domain handled by DynDNS - probably this is where this three field split came from in the first place, because if you are using one of the DynDNS free subdomains you have at leas three fields.
Also, in their defence, probably not many small business product users have dynamic IPs .
Anyway, I will hear from them again on monday.
I have been using the free DynDNS service for almost 5 years and it has worked flawlessly. I have also helped many customers with DDNS issues over the years and I had no idea that you could "have your own domain handled by DynDNS" until you started this thread. I guess I should pay more attention to all of the emails they send me...
I have nearly the same problem. I have a free DynDNS Service from a other provider in Germany. But my RV320 supports NO other DynDNS Provider as DynDNS.org or 3322.org.
Cisco is a company with a lot of customer and with high cost products. But all SmallBusiness Router products didn't support customer spec. settings. Cheap Router in low cost sector brings a hand full DynDNS out of the box in list menu and a "other provider" setting. Poor Cisco.
I kick my cisco product(s) [RV220W] in the dustbin and buy low cost products, that I'm flexible of new services, as with expensive Cisco products.
If you search in the support database, many, many people have the same problem and open a support ticket.
A new Firmware can fix this problem. But Cisco takes not care about the issues / problems / request of they customerer.
I switched from a NoIP paid account to a DynDNS paid account with all the costs involved in order to be able to update my dynamic IP from the router, just to have the issue described in this topic.
In 8 months the huge update of joining three edit boxes into one and leaving the host validation to the DynDns server as it is supposed to be, hasn't arrived.
If this is your only issue with the router, try changing the firmware to a different version (lower is fine) and see if it work better.
Huntsville's Premiere Car and Bike e-magazine: www.huntsvillecarscene.com
I thought about that, but usually there is a good reason for firmware updates so if I can, I will stick with the latest one.
Also I'm pretty sure this affects all RV320 firmware versions.
Thanks for the suggestion though,
I agreed with using the latest firmware, especially with newer devices as they tend to have the most issues.
Do you have anything else on the LAN that can handle DDNS properly? I have several IP cameras, a NAS, surveillance DVR, etc. that support DDNS. I have found that most of my devices that support DDNS have many more options than my RV220W and all of them have only one space for the Host Name. You can also run the free DynDNS updater on any PC that runs 24/7, I have a friend that does that because his ISP router doesn't support DDNS at all.
This might be a good workaround for now.
I do have a Synology NAS that does the update for now but I would like the router to do it, because it would be done automatically each time the router re-connects to the ISP.
I would think that the Synology would update just as reliably as the router. I used an IP camera to update for at least a year when I had a router that did not support DDNS properly. I never had any issue reaching my network from a remote location, the camera kept DynDNS.org updated reliably. Does your WAN IP change frequently?
There is usually a good reason for firmware updates. Unfortunately, in the smb router space, most of these firmwares (by almost any manufacturer) break things as they fix them. Therefore, it's best to treat a firmware as a 'software feature set' and load the one that works for your application. Newer isn't always better.
Huntsville's Premiere Car and Bike e-magazine: www.huntsvillecarscene.com
There are always good intentions behind firmware updates. But the reality is that a newer firmware can break a feature that was working fine. A lot of times you have to find the firmware that has everything you need working flawlessly and just stick to that firmware. And this is with almost any brand in the smb router space, so it's not solely a Cisco issue.
One thing I would suggest is factory defaulting your unit and the rebuilding your config from scratch. DO NOT use any method of saving the settings and restoring them. I've seen doing this cause problems like fields not being there on the interfaces.
At this point I will give up this issue as I'm pretty dissapointed with the Cisco support.
After a long discussion with them, starting from explanations on how I have my own domain handled by DynDNS, to links in wikipedia to explain the format of a FQDN and how it is NOT limited to third level subdomains, their conclusions are:
2. they cannot understand why I'm so fixated on updating
A big thank you to all the people that took the time to try to help.
I'm sorry about the issues you are having with support.
I read the case notes and it appears that the engineer handling your case does not fully understand that other devices (including the entire Cisco SMB router lineup with the exception of the RV320/325) have a single line to enter the hostname. I am not aware of any other Cisco SMB product that uses the DDNS format of the RV320/325.
Please request that your case be escalated for a feature request to change the RV320 DDNS options to look and function like the rest of the SMB routers. If the development team knows that you (and likely others) are having a problem because of the way that the web UI is designed they will likely change it in a future firmware. If the case does not get escalated the development team will never know that you had this issue and certainly will not try to fix it.
You may also find that you can communicate your issue easier if you call support. Chat can be very good for simple questions but I think it would be better for you to speak with someone in this case. You can call and reference your case number during normal business hours (9am-6pm M-F). You will find a number for your country at the following page:
I would also like to note that when I copied and pasted your serial number from the "Certificat de Garantie" document attached to your case, I was able to find the details in our system. It appears that you posted the wrong SN in the initial chat so you may wish to update the case owner.
just a small note to your problem.
Have you tried to set your own subdomain at hosting provider in case you have any?
I have also my domain and wanted to add a record which defines my public IP of the router.
As I had found that DynDNS is not for free already, I have looked at hosting provider administration site and found, I can add a record that redirects the request to my public IP.
I am sure every hosting provider does have something like that as there is an email and web redirection etc. to certain IPs.
So everytime I type remote.mydomain.com, a WEB UI of router or NAS appears. Voala, no need to use DynDNS or the router setting.
Hope this helps.
Use Wildcards" feature is not available on the rv320.
(this feature is only supported on RV120w, RV180x, and RV220W)
so, your case is being prepared for escalation.
Is it possible to get an update on the current status? I am running into the same issue, and cannot figure out a way around it.
If this feature is something you critically need, try upgrading/downgrading the firmware and see if you can find one that works. This might be a good solution until (if) Cisco fixes the issue.
I have the same problem, just purchased this router. Any solution found yet?
As suggested I might have to use my Synology NAS to do the work. On there no more surprises like this one :-)
I have same problem with my custom DNS.
RV325 doesn't support custom DNS of Dyndns for the second level domain.
It's very serious. Cisco must fix this problem for SOHO.