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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a localized lab that I work in. The setup is pretty simple - I have a router that forwards DNS requests to the "outside world", and behind it about 30 some odd machines that have a mix of static and DHCP addresses.
The lab boxes use the router for primary DNS, 192.168.0.1. The router also does NAT and DHCP.
What I'd like to do is build up a Debian DNS server in the lab for local addresses only. So if I have a machine named "server1" that has a NAT address, I can type "ping server1" from within my lab and get the address of the machine.
The problem is that the actual machine name needs to be a company mandated (XXSerialnumber-PC.mydomain.xxx). So what I hope to do is assign my new internal Debian DNS box a set of static name mappings, and thenset that server as secondary DNS for the windows and linux boxes inside.
Does that make sense? Eg:
192.168.0.15 - > maps to -> "server1"
Basically I want to make up my own names for the machines and be able to ping them (eg "ping mailserver" "ping fileserver") instead of having to know the machine's actual domain name in order to hit it with either a ping, or a \\188.8.131.52 in Windows.
Does it seem sensical that I could set a Debian DNS box as seconday, then edit (something I'm not sure of) to add my own A records in?
You add the information to the /etc/hosts file. This will only work for static addressing. If you are using dhcp assigned addresses it gets very complicated. Basically on Linux boxes you would setup the host names with their ip address in the hosts file. M$ also use the hosts file but I am not sure that it can be used for name resolution.
If you have control of the primary DNS server, then you could just use a split-view on that server. That way the outside world only sees what you want it too and you can add the internal stuff to the other view which you set to only be viewable within the LAN. Then you can keep a seaparate zone file for the domain with whatever naming scheme you want in the internal view.
If you don't have control over the primary, then sure you could setup your own DNS server for the domain and use it to resolve the names for you. Either way should work fine, I'd think.
Distribution: #1 PCLinuxOS -- for laughs -> Ubuntu, Suse, Mepis
I am afraid ti's not that simple .. DNS servers are not "routers" .. they only resolve names .. and they need to talk to each other ..
If you can connect to 1 .. you don't don't connect to the second .. the 1st one is supposed to give you answers or get it for your.
DNS servers also don't behave when they are hidden behind "firewalls". So it may not work for you at all.
What you are looking for are aliases to ping around with .. your DNS solution will be a huge undertaking.
my suggestion is
: write a script that pings thes the host by IP numbes and collect your "hostname" data ..
now use that host name data and map it into "your names" and.
now you can write a wrapper on ping to translate "your name" to the "actual hostnames" .. which is what you want to do .. not the
full bang DNS server.