Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I'm now currently using Mandrake 9.0 and Vector 3.2 SOHO. I was finally able to get my network hooked up in Vector, and the reason why I was having so many problems with Vector was I found out that it doesn't set up the resolv.conf file. I had to copy what was in that file from my Mandrake system, then enter the same info into the Vector system. My question is, if Vector doesn't automatically configure that file, and let's say I didn't have my Mandrake system to reference, where would I get the data needed to be entered into that file?
Your ISP will give you your domain. They will also probably run DNS, so will have an easily accessible nameserver or two to use, though in a sense, any nameservers will do. Read "man resolver" for a list of options (though I would disagree with the statement that a normally configured system would have its own nameserver).
Any name server *will not* do. A properly configured name server will only provide it's dns'ing service to those on it's own network. Not to mention, if I were to take a public name server half way across the world, the resolve time would be very high.
Best thing to do is call your ISP. Your ISP *will* have name servers for you to use.
ISP: Internet Service Provider. DNS Service is provided by all modern day ISPs. (Except in Mexico for some reason? ;)
Certainly it is more practical to use nameservers easily accessible on the network. However, it also makes sense to add one or two servers further from home, perhaps in divergent directions for redundancy. The algorithm for choosing nameservers will pick the one with the fastest response time. Therefore it is pretty likely that the nameservers provided by your very own ISP will be used. My ISP runs a microsoft server, so DNS ain't always up.
This redundancy and sharing of resources is what makes the internet work. Perhaps that is to be depreciated as well.
I'm sorry, I should have said this in the first post. I'm running a LAN behind a Linksys router running DHCP. So I'm splitting my DSL connection. I would think from reading your replies that I would be able to get this info from my network info from the router then?
It is quite unlikely your router is running DNS. Copying the information from your Mandrake system is certainly the way to go. If you did not have that information, the first step is to contact your ISP and find out the IP number(s) for their nameserver(s). They should have provided this information when you signed up, many have them listed on their websites.
If you like redundancy, find some other servers and add them to your resolv.conf as well. You can check service with a variety of commandline tools, including for example "host", "nslookup", "dig", and the number of hops using "traceroute".
I definately agree you should use name servers on separate networks for dependability/reliability. That's why any good ISP (and I say this because I've done this at all 3 of the ISPs I've admin'd ;) will have multiple backbones out to the internet. And this, most often, includes access to that provider's DNS servers.
there is a problem with that.....some isp's only provide a primary and secondary dns server addy. (thats two for thier entire subscription base) usually these are small mom and pop - ran isps, but nonetheless it happens. you also may want to call your friendly isp tech support line for this information.....and here is a hint: when you call immediately ask to speak to a supervisor, because if you talk to a low level tech, chances are they dont know their dns from a hole in the ground.
Shoot, I'm using SBC Ameritech and mandrake created the resolv.conf file and there were only two addresses listed. I may give them a call and see if there are others that they provide, you'd think so being such a big company and such.