NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FVS336Gv2: NoIP Dynamic DNS support?
I just finished setting up my FVS336Gv2, replacing my old V1 box. Is there any way to add NoIP (www.noip.com) dynamic DNS support?
My main reason for upgrading was to get the DMZ features so I could move my web server back behind my firewall. NoIP's dynamic DNS client (software) can't figure out the correct WAN network address to use when it is behind the FVS. The FVS's Dynamic DNS feature looks like it would solve all of my problems, but it doesn't include NoIp support (just Dynamic DNS, DNS TZO, DNS Oray, and 3322 DDNS).
If support is coming in a near future patch, that's great (I'm running firmware 4.3.1-18, which I think is the latest). Or if there is some way to otherwise bend the FVS336 to my will, I would appreciate hearing about it. Thanks!
My main reason for upgrading was to get the DMZ features so I could move my web server back behind my firewall. NoIP's dynamic DNS client (software) can't figure out the correct WAN network address to use when it is behind the FVS. The FVS's Dynamic DNS feature looks like it would solve all of my problems, but it doesn't include NoIp support (just Dynamic DNS, DNS TZO, DNS Oray, and 3322 DDNS).
If support is coming in a near future patch, that's great (I'm running firmware 4.3.1-18, which I think is the latest). Or if there is some way to otherwise bend the FVS336 to my will, I would appreciate hearing about it. Thanks!
2 Replies
I just finished setting up my FVS336Gv2, replacing my old V1 box. Is there any way to add NoIP (www.noip.com) dynamic DNS support?
NO on router interfaceNoIP's dynamic DNS client (software) can't figure out the correct WAN network address to use when it is behind the FVS
If you are using DDNS software on Server itself then it should pickup. From the server if you use browser and check the whats my ip still should see your WAN IP.
If you are using BOTH WAN then you have configure the Inbound/Outbound rules to the right WAN- Thanks, June.
I didn't explain my complete issue. One of my WAN ISPs doesn't support inbound HTTP / HTTPS traffic. I put my server in the DMZ and created an inbound rule (Security=> DMZ WAN rules) that seemed to do the trick, the DMZ WAN inbound rules don't permit "binding" inbound traffic to a particular WAN port. I'm guessing that's why the NoIP DDNS client couldn't figure out the correct inbound NATed address- it kept finding the wrong ISP.
I *think*, however, I figured it out. I added protocol binding (Network Configuration=> protocol binding) for all outbound traffic from my server to go over WAN 2. After doing that, the NoIP client seems to be consistently identifying the correct (WAN 2) NATed address.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
