Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
like you allready know it's for mapping ip's to hostnames.
it's an service every tcp/ip machine will use to do so and is for general (not related to another service).
if a request that should be send to, let's say, willie.the.pimp the tcp layer will send a request to an dns-server to resolve this to an valid ipaddress and then use this address to actually connect to willie.
dns was developed from the early ARPAnet (~ '69) where a simple hosts.txt (think of i like the /etc/hosts file) did the translation from machine names to their corresponding (a 32bit binary number) address.
in the eighties there where more and more computers connected and maintaing hosts.txt-files became a horror. dns was born.
i'd say:
every service that's working with a tcp/ip network and is able to speak with a resolver (rather think of the resolver more like a library) may use this function with the aim to do what you allready know: get a ip-address for the (for humans easier to recognize) na.m.e of that host.
the only application really works with the specific mechanism (dns) is
-the server (named/bind,dns-forwarders) on the knowing side and
-the client (nslookup/dig/host,resolver) on the other.
a lot of programs like mta's, browsers,... use dns but actually only communicate with the local resolver - they don't connect the dns-server directly.
google for "dns" and you'll sure find lot of information.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.