-
Couldn't load subscription status.
- Fork 367
Use ipify as default web service #41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Since many users including myself had problems with http://checkip.dyndns.org/ i suggest moving to ipify as standart service Info: https://www.ipify.org/ Pro: -No limit in requests -Verry fast and responsive -Open souce -No Logging of visitors -Works with IPv4 and IPv6 Con: -?
|
Looks like a good suggestion. I'll review your patch asap. |
|
I tested this to see if it works with ipv6 and it fails... It is fine to add it to ddclient, but it is not true to assert that it works with ipv6. David |
|
Hmm okay thanks for trying this.. I couldn't try it since i dont have an IPv6 address.. Michael |
|
I can recommend myonlineportal.net. Gerald |
|
Well i can't decide whats best to use.. Mjcaehl |
|
Gerald, thanks I did not know of myonlineportal.net. This is the first site I've found that seems to work well for both IPv6 and IPv4. Note that ddclient as published does not handle IPv6, what limited support that was added is very specific and doesn't do the job. My pull request #40 does add support for IPv6 in a manner that I think is flexible and comprehensive. But I realise that the changes are considerable -- I've requested a code review, testing and comment. The concept of Dynamic DNS / IP doesn't really have a place in the IPv6 world. And few DDNS sites support it. FreeDNS does, but I think there are problems with it too. However I do like the idea of a DDNS client that can update IPv6 addresses, even though the actual address is highly unlikely to ever change unless the server/client system itself changes. But that DDNS client needs to be able to cope with both IPv4 and IPv6 addresses for the same domain name, and that requires a lot of changes to ddclient, hence the size of pull request #40 David |
|
So if we don't support IPv6 ipify would be fine untill we do.. Michael |
|
The problem with IPv6 has already been reported. Let's all follow the bug and hope there will be a good ipv6 provider soon. See rdegges/ipify-api#3 |
|
I would observe that in IPv6 world there is really no need for web discovery of your IP address. Even behind NAT the IPv6 address assigned to your network interface is globally routable so you can obtain your IPv6 address simply by querying the network interface (eth0 or whatever). So for ddclient purposes it is unnecessary. Web discovery is useful if, for example, you want to find out what your browser is using by default. David |
|
Why not -> http://checkip.dns.he.net/ ? |
|
They seem to have added IPv6 support. Testing it here seems to indicate it works, I'll test it on a vm w/ IPv6 when I have time. |
Based on ddclient#41 Closes ddclient#41
|
@SuperSandro2000: I see you added the ipify web-service using the URL https://api.ipify.org, but you might as well want to add an ipify6 web-service using URL https://api6.ipify.org as @petersjt014 mentioned. Additionally dnspark is not working anymore as the domain name is for sale. Maybe remove that one as well? |
I just added it to my fork cause I needed some ipv6 features and decided to just merge everything good together. |
I just remembered that I listed all the dead ones I could find in #87. |
Since many users including myself had problems with http://checkip.dyndns.org/ i suggest moving to ipify as default service
Info: https://www.ipify.org/
Pro:
-No limit in requests
-Very fast and responsive
-Open source
-https
-No Logging of visitors
-Works with IPv4 and IPv6
Con:
-?