I needed to automatically get my own WAN-IP-adress from my router. I found this question and, among others, a solution with dig was proposed:
dig +short myip.opendns.com @resolver1.opendns.com
It works perfectly, but now i want to understand what it is doing. Here is what I (hope to) understand so far (please correct me, if I am wrong):
+shortjust gives me a short output
@resolver1.opendns.comis the dns server, which is asked which ip adress belongs to the given domain
What's not clear to me is
myip.opendns.com. If I would write
www.spiegel.de instead, I would get the ip adress of the domain www.spiegel.de, right?
myip.opendns.com I get the WAN-IP of my router. So is
myip.opendns.com just emulating a domain, which is resolved to my router?
How does it do it? Where does it get my ip from? And how is it different to what webpages, like e.g. www.wieistmeineip.de, are doing? They also try to get my ip.
In the answer of Krinkle on the question I mentioned, it is stated, that this "dns-approach" would be better than the "http-approach"? Why is it better and what is the difference?
There has to be a difference, because the WAN-IP, I get from
dig +short myip.opendns.com @resolver1.opendns.com (ip1) is the one I can also see in the web interface of my router, whereas
www.wieistmeineip.de (and other similar sites too) is giving me another ip adress (ip2).
I could imagine that my ISP is using some kind of sub-LAN, so that my requests to webservers are going through another (ISP-) router which has ip2, so that
www.wieistmeineip.de is just seeing this adress (ip2). But, again, what is
myip.opendns.com doing then?
Additonally: Opening ip1 from within my LAN is giving me the test website from my raspi, opening it from the outside of my LAN (mobile internet) does not work. Does it mean, that ip1 is no proper "internet ip" but more like a LAN ip?