Host name common practice

[Gregory Hicks]

Greetings:

As much as we would like to help, the problem seems to be with MS  AD
and MS DNS.  The comp-protocols-bind group is for BIND ("Berkeley
Internet Name Daemon") only and while some of the users MAY have AD
experience, you'll probably be better served asking on a Microsoft
newsgroup...

Regards,
Gregory Hicks

> To: comp-protocols-dns-bind at isc.org
> From: "mmccaws2" <mmccaws at comcast.net>
> Subject: Host name common practice
> Date: 12 Jul 2005 11:02:05 -0700
> 
> We have multiple AD forests host name problems.  Each forest has it's
> independantly created DNS.  So NS1.AD1.here is SOA for AD1.here and
> NS2.AD2.here is SOA for AD2.here.  AD1.here one-way trust AD2.here.
> Administrator in AD2.here would like to rename server
> hostname1.AD2.here but if hostname1.AD1.here is present the OS prevents
> this.  The gotcha on this is if hostname1 is a unix box in AD1.here
> then it is allowed.
> 
> Why is this happening if domains name servers are independant?
> 
> If duplicant host names are required on the two domains, what option
> needs to be set in MS DNS.
> 
> Or is this even a DNS problem but only the symptoms appear as a DNS
> problem?
> 
> Thanks for looking at it.
> 
> Mike
> 
> 

-------------------------------------------------------------------
Gregory Hicks                        | Principal Systems Engineer
Cadence Design Systems               | Direct:   408.576.3609
555 River Oaks Pkwy M/S 6B1          | Fax:      408.894.3400
San Jose, CA 95134                   | Internet: ghicks at cadence.com

I am perfectly capable of learning from my mistakes.  I will surely
learn a great deal today.

"A democracy is a sheep and two wolves deciding on what to have for
lunch.  Freedom is a well armed sheep contesting the results of the
decision." - Benjamin Franklin

"The best we can hope for concerning the people at large is that they
be properly armed." --Alexander Hamilton