What I understand about how DNS works is like this: first let's assume mydomain.com
has the IP address 12.34.56.78
. Now when I put the url mydomain.com in the browser, the browser sends a dns lookup to its local dns server, asking, hey, do you know the ip address for mydomain.com. If the local dns server does not know about it, it will ask the parent dns servers, if the parent also does not know, then it keeps asking all the way up until the root dns server. The root dns server will ask some server in charge of the .com
tld. The dns server in charge of the .com
will have knowledge about mydomain.com
because mydomain.com
is the .com
family. Then the answer will be returned back to the initial asker. Also the answer quite likely will be cached in the dns servers involved in the asking process. Would anyone correct my understanding if it is wrong.
So my real question is about how reverse dns lookup works. Let's say if I want to find out what domain name is for the ip 12.34.56.78
. I run the command dig -x 12.34.56.78
. If my local dns server does not know the answer, which server does it further ask? Is it 12.in-addr.arpa.
, or 34.12.in-addr.arpa.
? If this is the case, are these names like 12.in-addr.arpa.
valid domain names? And where should they be deployed so that the reverse lookup requests will know whom to ask?
Best Solution
How a reverse DNS lookup is accomplished:
Source here.