having my master nameserver resolve another zone...
Mark_Andrews at isc.org
Mark_Andrews at isc.org
Fri Jan 31 00:06:01 UTC 2003
Or use a DNAME, but take care as the is a bug in all version of bind 9
upto and including 9.2.2rc1 which breaks the resolution of DNAMES.
Mark
>
> Create aliases (CNAME records).
>
>
> -
> Kevin
>
> "Christopher L. Barnard" wrote:
>
> > What I'm trying to accomplish is to have cbott.com appear as a subzone
> > of cbot.com. I want "foo.cbott.com" to be resolved by our internal
> > DNS as "foo.corp.cbot.com".
> >
> > Or, if that is not possible, have "machine.zone.cbott.com" be resolved
> > by our internal DNS as "machine.zone.cbot.com".
> >
> > Christopher
> >
> > > "Christopher L. Barnard" wrote:
> > >
> > > > Sorry. The master forward dns table of the cbot.com zone.
> > > >
> > > > The cbott.com zone and the cbot.com zone both work just fine, all
> > > > entries are defined, etc. What I am trying to do is to get the cbot.co
> m
> > > > zone to recognize the cbott.com zone as a subzone of cbot.com.
> > >
> > > Well, only subdomains can be subzones. cbott.com is not a subdomain of cb
> ot.com,
> > > so how can it be a subzone?
> > >
> > > Perhaps you should clarify what you're trying to accomplish.
> > >
> > >
> > > - Kevin
> > >
> > > > > It's not clear to me what you mean by "master forward dns table". You
> > > > > should be putting these records in the cbott.com zone. Unless you int
> end
> > > > > to define a cbott.com zone explicitly on *all* relevant nameservers,
> you
> > > > > should also be adding these same records as glue to the parent zone
> > > > > ("com" or root).
> > > > >
> > > > >
> > > > > - Kevin
> > > > >
> > > > >
> > > > > Christopher L. Barnard wrote:
> > > > >
> > > > > >I must be missing something here, but I do not see what.
> > > > > >
> > > > > >I am trying to add the new zone "corp.cbot.com" under the existing c
> bot.com.
> > > > > >Because of some other requirements, this server is actually "cbott.c
> om"
> > > > > >(note the extra t). cbott.com has been registered with Internic, so
> that
> > > > > >should not be an issue. I suppose it does not matter actually, sinc
> e it
> > > > > >is internal-only...
> > > > > >
> > > > > >What I am trying to do is have a machine "foobar.cbott.com" resolve
> as
> > > > > >"foobar.corp.cbot.com", thus masking the fact that it is really in t
> he
> > > > > >cbott.com zone. I am trying to fight one forest fire at a time, so
> I
> > > > > >want to resolve just "foobar.cbott.com" first. Then I'll tackle hav
> ing it
> > > > > >resolve as foobar.corp.cbot.com. I have put in the master forward d
> ns
> > > > > >table the glue records
> > > > > >
> > > > > >cbott.com. IN NS cbottad1.cbott.com.
> > > > > >cbott.com. IN NS cbottad2.cbott.com.
> > > > > >
> > > > > >and the corresponding A records for their IP.
> > > > > >
> > > > > >cbottad1.cbott.com. IN A 164.74.77.101
> > > > > >cbottad2.cbott.com. IN A 164.74.77.102
> > > > > >
> > >
>
>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
More information about the bind-users
mailing list