Hello!
First post here, though I've been finding this forum and community very helpful and you have my thanks.
I'm trying to set up a web server through docker containers. Everything's looking okay so far, though it's been a journey to get to this point, even, seeing as I'm a software engineer and all this network admin stuff is out of my comfort zone.
So I created a noip container and put the config file in a shared folder.
It seems to be communicating with the noip servers and getting a response, but is for some reason pointing to a different ip address!
In the config file I set up eth0 as the controller. The ip address returned is nothing that I can recognize.
I'd love to give more information, please point me at the right direction!
Many thanks in advance.
This project is for a good cause!
noip (CS) DUK wrong ip
- dolbyman
- Guru
- Posts: 35276
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: noip (CS) DUK wrong ip
well is the IP returned a public or a private one ?
-
- New here
- Posts: 3
- Joined: Tue Jun 28, 2022 1:34 am
Re: noip (CS) DUK wrong ip
It's a public IP. I just tracked it and it points to the nearby town.
So we're not that far off :P
This is probably important. :)
So we're not that far off :P
This is probably important. :)
- dolbyman
- Guru
- Posts: 35276
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: noip (CS) DUK wrong ip
Weird.. is this a normal home internet connection or some shared/dorm thing ?
I just use the DDNS updater of my router, I never had to resort to anything like that (DDNS updater script)
I just use the DDNS updater of my router, I never had to resort to anything like that (DDNS updater script)
-
- New here
- Posts: 3
- Joined: Tue Jun 28, 2022 1:34 am
Re: noip (CS) DUK wrong ip
Thank you, I wasn't aware of that option! I was just operating on the manual supplied by noip.
It would have still been an open question had I no access to my router admin panel, but I do, so I just set it up through my router as you suggested and the issue was avoided.
It would have still been an open question had I no access to my router admin panel, but I do, so I just set it up through my router as you suggested and the issue was avoided.