N
norma
I work at a university where our campus has a UNIX server
that supports DNS on the network using static records.
We have our own subdomain and had a NT PDC which we just
upgraded to 2000 Domain Controller. When prompted for our
domain name in the installation I input subdomain.domain
without adding the .ca on the end. We are using the UNIX
DNS server to resolve names and DNS is not set up in
Active Directory. The IT department asked me to forward a
copy of the netlogon.dns file to them so they can add
entries into their UNIX DNS records for our subdomain.
They are saying that I should have added the .ca at the
end and that it will cause problems. I don't believe that
is true if I am not using AD integrated DNS. All of our
2000 servers including the DC point to the UNIX DNS
server. Our workstations are functioning correctly and
there seems to be no connectivity issues.
If I listen to them, I have to re-install my DC and that
would mean losing my user accounts and starting fresh
again which I don't want to do. Can anyone point me to
documentation or proof that I can give our IT department
that will ease their concerns. We also were seen on the
network as subdomain.domain before the upgrade and are
still seen the same way. I can't see what the issue is.
Thanks. If you could email me directly that would be
greatly appreciated.
that supports DNS on the network using static records.
We have our own subdomain and had a NT PDC which we just
upgraded to 2000 Domain Controller. When prompted for our
domain name in the installation I input subdomain.domain
without adding the .ca on the end. We are using the UNIX
DNS server to resolve names and DNS is not set up in
Active Directory. The IT department asked me to forward a
copy of the netlogon.dns file to them so they can add
entries into their UNIX DNS records for our subdomain.
They are saying that I should have added the .ca at the
end and that it will cause problems. I don't believe that
is true if I am not using AD integrated DNS. All of our
2000 servers including the DC point to the UNIX DNS
server. Our workstations are functioning correctly and
there seems to be no connectivity issues.
If I listen to them, I have to re-install my DC and that
would mean losing my user accounts and starting fresh
again which I don't want to do. Can anyone point me to
documentation or proof that I can give our IT department
that will ease their concerns. We also were seen on the
network as subdomain.domain before the upgrade and are
still seen the same way. I can't see what the issue is.
Thanks. If you could email me directly that would be
greatly appreciated.