Open cormacrelf opened 8 years ago
I was experiencing #61 as well, and making this change manually has fixed the issue for me. 👍
I was using the following locally and it was working great for me:
dig TXT +short o-o.myaddr.l.google.com @ns1.google.com | awk -F'"' '{ print $2 }'
I figure Google is the least likely to go away, and it might help the "Great Firewall" problem, too, though I'm not sure how to test that. Google does like to move stuff around sometimes and change names from time to time, though.
dig TXT +short o-o.myaddr.l.google.com @ns1.google.com | awk -F'"' '{ print $2 }'
also works fine for me, and has been working for a long time.
I've been afk for a few weeks, will test the Google solution and amend the PR on Monday if all goes well.
What's the status on this? I apologize, IIRC I'm the one that originally submitted the change to use eth0.me since it was much faster than the previous method. DNS is superior if it can be used, but as you've noted many of the larger (and thus faster) DNS networks are blocked in some countries.
If nobody else has found a solution, I will reach out to some friends of mine in China to have them test some ideas I have and I will submit another PR that works globally to fix this.
i'm using curl -sS ifconfig.me
for the IP Adress
Pretty sure
dig
works on most if not all versions of macOS.Fixes #61.