NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

david128's avatar
david128
Tutor
May 15, 2021

Netgear DDNS failure

My D7000V2 is failing to register to the DDNS service (that is actually provided by no-ip) - it has been working for more than a year, but now the router reports 

Unable to complete the job, reason: Unable to locate hostname in your account

 

Using the no-ip client on a windows machine, the hostname does exist and works

BUT - the no-ip client uses a username, not the email address that the D7000 router uses

I'm running firmware V1.0.0.64_1.0.1 on the D7000V2

 

Note that if the email/password is entered wrong, it reports a different error, so I believe these are ok

 

I've raised a support ticket with no-ip, and they suggest it's a router issue

I suspect that they no longer support email/password access to the hostname (although it's not failing authentication, as mentioned above)

 

Can anyone confirm that the netgear DDNS still works with the firmware I'm running

 

 

 

 

3 Replies

  • michaelkenward's avatar
    michaelkenward
    Guru - Experienced User
    May 16, 2021

    Have you noticed the recent changes over at no-ip?

     

    The Netgear deal with a permanent free account is dead.

     

    You now have to confirm your address every month.

     

     

     

     

    • david128's avatar
      david128
      Tutor
      May 16, 2021

      Hi Michael,

       

      Thanks for the reply

      Yes, I was aware that no-ip had changed to a 30 day expiry - I'd previously had them recover my hostname as they had expired it

      But I can show, using their own client, that the hostname is active (and thats what I'm currently using whilst the router DDNS isn't working)

      It's just my netgear router that doesn't seem to be able to register to that hostname

      I did try setting up another hostname (as you get 3 free), and the router also fails on that hostname as well

       

      Regards

      David

      • david128's avatar
        david128
        Tutor
        May 16, 2021

        Ok

        Thinking about what I could try

        In the DDNS menu I changed the service provider from netgear to no-ip, and then entered the hostname (....mynetgear.com), username & password that I was using

        Lo and behold, this now works...

         

        This confirms my suspicion that it's the fact that using 'netgear' as the provider, and then having to use the email address (not user name) is the problem here

         

        It's not the perfect solution - and I wouldn't consider the issue closed, but it's a work around thats ok with me right now