Bind 9 ext and int zone

[aklist_bind at enigmedia.com]

> As you have pointed out, using testhis.com for your dev servers, will
> require an internal DNS server to resolve local addresses, and possibly
> additional records (eg, www) that point to external addresses. If you
> *have* to use testthis.com, you probably don't have much choice here.
> There shouldn't be a lot in the way of management though. Probably,
> you'd just add a few records, and be done with it.
> Nothing says you have to use that domain though. How about putting them
> in the testthat.com domain and just adding records for the dev servers?
> Of course you have to create that domain, and add records there too...

Am I missing something obvious, or wouldn't it be appropriate to use views 
in this case?

--Andrew

>
> On Wed, 2006-03-08 at 09:26, Nick Allum wrote:
>> Would anyone have any suggestions as to what options I might handle the
>> following situation.
>> We have a zone testthis.com which is and external zone on some external
>> NS servers. However they are also requesting that we host this zone
>> internally on our internal NS server to point to some development
>> servers with internal addressing.
>>
>> I do not want to have to maintain any changes interally that are made
>> externally, so I am looking for an alternate solution.
>>
>> Any suggestions would be much appreciated.
>>
>> Nick
>>
>>
>
>