Different IP address between dynhost and redirection

Domains and Hosting
1

Hello, I have two subdomains that give access to different locations.

I connect frequently to one, unlike the other.

This morning I tried to connect to that other location. Unable to connect to the data servers.

I log in to OVH to check the redirects and DynHost. Both show the same IPv4 address, but it is different from my current IPv4 address (a month ago everything worked fine).

I enter the new IPv4 address in the redirect settings of the correct subdomain, but it refuses to save it. I then go to DynHost and the IPv4 address there is correct.

I try to connect to the server via my phone after turning off Wi‑Fi and I can access the server normally.

I have a Livebox and I know the IP address isn’t static. I only got fiber a month ago; before that I had a VDSL Livebox and never had any IPv4 change issues.

Is there anything I can do so that OVH follows the IPv4 address changes of the Livebox? There were network works 4–5 days ago. Could that be related?

Thanks for your advice.

2

Hi @DominiqueP10

Could you check the update URL of your Livebox and let me know if you have this one?:
https://dns.eu.ovhapis.com/nic/update

Regards,
Sergio Turpín

3

Hello @DominiqueP10

Which version of the box do you have?
Which internet provider are you with?

Two days ago I set up a DynDNS solution for a friend’s Livebox 5 using a subdomain I created.

4

Hello everyone and thanks for the follow-up,

I am with Sosh.

I just tried to connect to the server but it's impossible.

I check my IP, it's still 90.27.xxx.xx

I went to the dynhost of the subdomain and the IP became 86.xx.xxx.xx again. The same as the one I had before modifying it the first time.

I just set it back to 90.xx.xxx.xx

I'll see how long it holds.

At the beginning of August I'm moving to Red, I know I'll need to request a full‑stack IPv4 pass.

5

Hello @DominiqueP10

After registering the DYNDNS with OVH, did you get the following screen?

Link to use https://nn.nn.nn.nn:PORT
https://[aaaa.bbbb.ccc.dddd.eeee.ffff.gggg.hhhh:9640]:PORT

IP address nn.nn.nn.nn
aaaa.bbbb.ccc.dddd.eeee.ffff.gggg.hhhh

6

What technical considerations lead you to make this choice?

7

Hello everyone. @Gaston there are no purely technical considerations, I just noticed that the advertised bandwidth wasn’t fully reached and the price of the other provider (which I use on another site) is cheaper.

Otherwise, after registering the DYNDNS with OVH I didn’t receive any specific information.

Thanks for the help

8

Right after you redo your dynhost record at OVH, open a terminal window on your PC and try the tracert subdomain command.

You should see the destination address displayed as the IP address you configured at OVH.

Note: if OVH doesn't provide the four lines I mentioned, it's likely that the requested configuration hasn't been applied.

Did you specify a port when you set up the configuration at OVH?

9

Hello everyone, this morning I was unable to connect to the server. I checked, DynHost reclaimed the address starting with 86... I set the IPv4 back to 90...

appears on the screen

image
image821×100 2.55 KB

I can connect to the server...

the change also appears in the redirection section.

Obviously there is something I'm not doing correctly for it to revert to the original state one day after the changes.

Waiting for advice, thanks in advance

10

Hello @DominiqueP10

Did you run this command?

11

hello @Gaston I just ran the command today and the result is the following:

image
image1154×371 11.9 KB

the IP is correct but I worked on the OVH dynhost this morning

I’ll try again tomorrow and the day after.

thanks for the help

12

All you have left to do is perform the operation regularly.:wink:

13

Thanks @Gaston for the advice :cold_face: .

There's something illogical. For about (I'm not quite sure, but) a decade there were no issues. I switched to fiber with the same provider and it no longer works as it should :enraged_face:

14

Hello, when moving from VDSL to fiber, did you receive a new box? Is the old one properly disconnected?

Or did you have a DynDNS client on a device other than your old box?

  1. In April there were complaints but I don’t think we ever got the final word on that. Dynhost dysfonctionnel

  2. I don’t think you can view the update logs at OVH.

15

Hi @fritz2cat. I have a new box and the old one is unplugged. Behind the box I have a Synology NAS. I only reconnected the router to the box, went to the OVH site and changed the IP address to that of the new box. I didn’t notice the problem right away; it was when I tried to connect to the server, which isn’t something I do daily. Shortly after getting the new box, Orange did some work on the network causing a cut that lasted maybe 2 h. And it was only after that that I noticed the issue, but I doubt it’s related. I think I had another IP address before the work (starting with 86… and then I got the 90). I don’t think that’s related.

I’ll see how it goes over time.

16

Hello everyone,

Well, this morning here's what it looks like

image
image989×926 18 KB

The IP address has reverted to 86 again...

I don’t have this issue with the other subdomain that points to another location and whose ISP is SFR.

I’ll check my setup to see if something might be causing this, but I don’t think so since everything was fine before... stay tuned.

17

Hello @DominiqueP10

No need to wait for the end of the traceroute.
Only the first line is sufficient; it instantly gives you the IP address managed in your sub‑domain associated with a Dyndns setting.

18

Please stop masking unnecessarily

image
image1098×105 4.25 KB

I keep thinking that you have a device at home that is performing erroneous updates.

And what is that IP address that doesn’t belong to you, which you have kindly masked?

image

Suggestion: change the API access codes for your DynDNS.

19

Hello everyone.

I was with Orange. I had this problem and another which was the inability to communicate properly with the rt2600 router. I had a network disruption message. I checked everything over and over, there was nothing that could cause a malfunction while the signal was fine. In particular, I couldn't perform a firmware update of the router.

I just switched ISPs, I go to the router's system settings and the firmware update is offered to me.

With RED, the new ISP, I'm told I have to wait one week for the activation to be complete in order to go full stack and be able to connect to the servers. I'll see about that then. I'll keep you posted as soon as possible.

j