Hi Chad,
>> Why are you overriding the nameserver? If you control the dhcp server
>> then the better option is to have it provide the desired information
>> there instead of having clients override it.
>
>
> I don't want to override it. I want to add additional nameservers that "know"
> about a domain that I need to resolve. My networking knowledge is kind of
> thin,
> but I suspect that this requirement for the other nameservers has something
> to
> do with the details of intranet segregation in our corporation . . . does
> that make sense?
>
Yes it makes perfect sense, but like others told you, it does not work the way
you think.
We have a domain tio.nl for which the public part is hosted at our ISP. It only
knows about our public servers.
However, when I work at home and want to work on our internal servers/machines
I need to resolve the complete tio.nl zone including all sub domains.
That is the reason I run bind on my Linux router/gateway and via DHCP I tell
all clients in my network to use that dns server.
In my bind config I have told it that any request to *.tio.nl has to be
forwarded to one of our internal dns servers.
That same bind server knows about my internal machines so I can use dns to find
them as well.
Anything else is simply resolved the way dns is supposed to work, it asks a
higher level dns server.
In my /etc/bind/named.conf.local I have:
zone "tio.nl" IN {
type forward;
forward only;
forwarders {172.16.128.40; 172.16.208.10;};
};
zone "staf.tio.nl" IN {
type forward;
forward only;
forwarders {172.16.128.40; 172.16.208.10;};
};
zone "student.tio.nl" IN {
type forward;
forward only;
forwarders {172.16.128.40; 172.16.208.10;};
};
zone "test.tio.nl" IN {
type forward;
forward only;
forwarders {172.16.128.40; 172.16.208.10;};
};
You do not have to use bind, there are more dns servers but it was easy to set
up and there can be lot of info found about it on the internet.
Using a small Linux machine as my router for my internal network solves a lot
of problems, it knows which traffic to send where. It sets up the VPN, sets up
my IVPv6 tunnel, does DHCP, is my firewall, my router, my dns server etc. And
all my machines in my home network only need to know about that machine.
Bonno Bloksma
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/89d1798a7351d040b4e74e0a043c69d7352a4...@hglexch-01.tio.nl
