Jeremy Begg
2007-06-09 12:36:58 UTC
Hi,
I am reconfiguring a machine running MultiNet 5.1 on OpenVMS Alpha
V7.3-2.
The machine is the nameserver for a group of PC clients which will
query
it for names in a variety of domains. I need Multinet to answer
queries from its own zone files where it can, or to refer to other
nameservers when it cannot. The MultiNet zone files contain
"doctored" results: the addresses it contains are the NATted addresses
the PC clients must use to contact the respective servers.
For example, I have a zone file which for the 'ab.xyz' domain which has
one 'A' record in it, for 'alpha.ab.xyx'. If a PC issues a query for
'alpha.ab.xyz' it will get the answer I want it to get. This answer
is different from what the corporate nameserver would return for the
same query.
However, the 'ab.xyz' domain is much larger than the contents of my
zone file and I would like my MultiNet nameserver to query the
corporate nameservers if it gets a query for any node in 'ab.xyz'
which isn't in MultiNet's own zone file.
Can this be done?
Thanks,
Jeremy Begg
I am reconfiguring a machine running MultiNet 5.1 on OpenVMS Alpha
V7.3-2.
The machine is the nameserver for a group of PC clients which will
query
it for names in a variety of domains. I need Multinet to answer
queries from its own zone files where it can, or to refer to other
nameservers when it cannot. The MultiNet zone files contain
"doctored" results: the addresses it contains are the NATted addresses
the PC clients must use to contact the respective servers.
For example, I have a zone file which for the 'ab.xyz' domain which has
one 'A' record in it, for 'alpha.ab.xyx'. If a PC issues a query for
'alpha.ab.xyz' it will get the answer I want it to get. This answer
is different from what the corporate nameserver would return for the
same query.
However, the 'ab.xyz' domain is much larger than the contents of my
zone file and I would like my MultiNet nameserver to query the
corporate nameservers if it gets a query for any node in 'ab.xyz'
which isn't in MultiNet's own zone file.
Can this be done?
Thanks,
Jeremy Begg