two bind on same machine - is it possible?
Jim Reid
jim at rfc1035.com
Mon Apr 30 09:09:07 UTC 2001
>>>>> "Fred" == Fred Lofler <henne at firemail.de> writes:
Fred> I got two IPs, say 10.0.0.1 and 10.0.0.3 on the same
Fred> machine. There is a domain already running on this server,
Fred> 10.0.0.1 got ns.bind1.net
Fred> Now I want to install a second one, 10.0.0.3 as ns.bind2.net
Fred> The zones got to be completely different - every ns got it´s
Fred> own zones. ns.bind1.net is connected to port 53 - the
Fred> second one would get port e.g. 54.
This is utterly wrong and pointless. Unless you can make the whole
world send queries to a non-standard port number just so they can
query your name server. This will never happen.
Fred> Every ns get´s it´s own named.conf, so as I got the idea, it
Fred> should work.
Correct. Each named process has its own named.conf file.
Fred> My question is - does this work?
No. See above. You could make your name server do this but the rest of
the world will ignore it. Everyone else's name server software has no
way of knowing which non-standard port number you happen to have bound
to a name server.
Fred> Or is there another way to
Fred> get two bind running on the same machine?
Yes. Use the listen-on clause in the options{} statement to make each
name server process only listen for queries on a specific network
interface.
More information about the bind-users
mailing list