Host name common practice
mmccaws2
mmccaws at comcast.net
Sat Jul 16 21:58:12 UTC 2005
let's try this again.
I have hostname1.AD1.here in the AD1.here ad forest. On the same
common network behind the firewall we have somename.AD2.here server
that we are renaming to hostname1.AD2.here. The name change is being
done by someone having administrator priveledges in AD2.here. There is
no previous registered name in AD2.here as hostname1. AD2.here forest
doesn't allow that name, hostname1, it reports it as in use. So
AD2.here seems to be saying that hostname1 is in use for AD2.here but
it hasn't been assigned by anyone.
Mike
Barry Finkel wrote:
> mmccaws2" <mmccaws at comcast.net> wrote:
>
> >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.
>
> I am trying to understand what is happening.
>
> How is Administrator in AD2.here attempting to rename server
> hostname1.AD2.here? Is this a DNS record deletion/addition?
> Or is the Administrator actually changing the hostname on the
> hostname1.AD2.here computer?
> ----------------------------------------------------------------------
> Barry S. Finkel
> Computing and Information Systems Division
> Argonne National Laboratory Phone: +1 (630) 252-7277
> 9700 South Cass Avenue Facsimile:+1 (630) 252-4601
> Building 222, Room D209 Internet: BSFinkel at anl.gov
> Argonne, IL 60439-4828 IBMMAIL: I1004994
More information about the bind-users
mailing list