vpn should not be tied to requiring a dynamic dns service bug

Just to pile on, here's another case where tying VPN service to dynamic DNS being set up on the router doesn't make sense: I actually do use dynamic DNS, but my preferred DDNS provider isn't supported by my router's firmware. This is probably not uncommon: even recent NightHawk firmware only supports three DDNS providers, so anyone using something other than Netgear, No-IP, or Dyn will fall into this category. Instead of setting up a DDNS client on my router, I use a update script that runs on my home fileserver to keep DDNS up to date. However, since I haven't set up a DDNS client on the router itself, it refuses to let me start a VPN server....even though I clearly have a reliable DNS record.