authentication changing domain names?

[g]

Hello,

I have an application server called intranet.site1.mydomain.local in a nt
domain called site1.
I have 8 other sites 2-9 each with their own nt domain site(2-9) I have a
two way trust from site1 to each other site. Users log in with site()\user
to the intranet server.
I want to collapse this multi-master setup and use my site1 domain name
with a new dns structure mydomain.com.

So what I was going to do was upgrade site1 to active directory and keep
the trusts to site2-9 until i could go out and change servers/users
into site1/mydomain.com. The problem is, my developer guys put all the
"links" to intranet.site.mydomain.local and hard coded them to that fqdn
so the client side of the apps need intranet.site1.mydomain.local.

I was wondering if anyone had any experience with this? I was going to
keep both zones site1.mydomain.local and mydomain.com but i was wondering
if this would do anything weird when i changed the dns suffix to my app
and f&p servers, clients, etc from site1-9.mydomain.local to mydomain.com.

Far as i can tell it should make no difference, it is just a dns name
resolving intranet.site1.mydomain.local to the same address as
intranet.mydomain.com but with microsofts "integration" with dns I am not
to sure.
If someone could help me out or give me a few pointers that would be very
nice.

Thanks

 

[Jeremy]

Time for a code change, .local is not an RFC supported namespace.
..local came from an FYI that went to Draft and was never accepted, it
expired sometime around June of 2000 I beleive.
It was heavily referenced but since then had caused numerous issues in AD
deployments and use of Exchange, Webservices, PKI, Mobility support, etc.
You should go to a registered namespace in AD.
Only the following namespaces are supported as internal namespaces.



Excerpt From RFC 2606
ftp://ftp.rfc-editor.org/in-notes/rfc2606.txt

" .test
.example
.invalid
.localhost

".test" is recommended for use in testing of current or new DNS
related code.

".example" is recommended for use in documentation or as examples.

".invalid" is intended for use in online construction of domain
names that are sure to be invalid and which it is obvious at a
glance are invalid.

The ".localhost" TLD has traditionally been statically defined in
host DNS implementations as having an A record pointing to the
loop back IP address and is reserved for such use. Any other use
would conflict with widely deployed code which assumes this use."


Also for informational purposes read the following RFC:
ftp://ftp.rfc-editor.org/in-notes/rfc2826.txt

You stand to have issues, done incorrectly and eployed on that premise you
will pay a price when you least need the hassle.


Jeremy

 

[g]

You stand to have issues, done incorrectly and eployed on that premise you
will pay a price when you least need the hassle.


Jeremy

Thanks for the reply jeremy, is the problem I will be having with the
..local or with the setup? I am not using nor will i use .local, i just
needed an example instead of my real domain names.

Thanks