You will have all sorts of problems if you try to host public and private
DNS zones on the same DNS server. Your AD integrated zone should be your
local LAN and its name should be the same as the name of your Active
Directory domain. This can be the same as your registered domain name or it
can be different. All LAN clients should use this DNS server, because many
AD services are accessed through DNS.
Have a look at recent postings in windows.server.dns on the best way to
handle hosting private and public DNS servers and the use of split horizon
(also sometimes called split brain) DNS services.
"Sharad" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> OK, then my problem seems to be something different.
>
> In the DNS, forward lookup zone (AD integrated),
> the SOA and Names Server show different domain (which
> is our registered domain for mail server.)
> (where as zone name is correct, - the Domain Controller)
> I tried to change these manually to the Domain Controller
> but upon refresh it goes back to the other one.
> Therefore where as my Names Server should have been
> servername.mydomain , it is servername.mailserverdomain
> I tried removing all the zones, and adding them again, didn't work, and
> un-installed DNS, removed cache back up etc. and re-installed, and
> again the same problem.
>
> In fact I have a separate primary forward lookup zone, for the registered
> domain for mail server (it's not AD integrated.) When DNS re-installed,
> even before adding this forward lookup zone, I faced the same problem.
>
> I found that the AD, though shows connected to mydomain.com, it shows
> Default-First-Site as servername.user.mailserverdomain (instead of
> serverame.user.mydomain) So I thought the Default-First-Site was
> the problem.
>
> I even un-installed DC and AD, re-installed, and again found the same
> problem.
> Everything works fine as such except the names server to be used. I did
not
> even notice that there is such problem, until, I wanted to make the DNS
> public
> for resolution of our own mail server and also certain other links.
>
> Any idea how to solve this issue?
>
> Sharad
>
> "Bill Grant" <bill_grant at bigpond dot com> wrote in message
> news:(E-Mail Removed)...
> > I am not sure I understand what you want to do. If you don't specify a
> > name it is called DefaultFirstSite. It is just a name. It does not have
> to
> > be a domain name. If you have sites in two diffferent cities you can
call
> > them Sydney and Melbourne. If you have sites at two different locations
> you
> > can call them PittSt and MartinPlace.
> >
> > Sites are used to define the physical layout of your network. They
are
> > not used to define the domain structure. You can have multiple domains
> > within a site, or a domain spread across several sites.
> >
> > "Sharad" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > I have setup Win 2003 standard server as Domain Controller.
> > > The AD shows default first site name, to different domain name (
> > > actually it is another registered domain name, to be used for mail
> > > server.) It seems while configuring, by mistake I put that domain
> > > name in the default site. I want to change it now back to the
> > > Domain Controller domain name.
> > > Can anyone help how to do this.
> > >
> > > Otherwise I am planning to remove and re-install the Domain Controller
> > (AD)
> > > role,
> > > if I do so, will it wipe out all user profiles? Is there any way to
> backup
> > > them first
> > > and backup all clients usernames and settings?
> > > Am not much worried about backing up the clients username and groups
> > because
> > > there are not more than 20, but the on the server machine want to
> retain
> > > the administrator
> > > profile.
> > >
> > > Sharad
> > >
> > >
> >
> >
>
>
|
Similar Threads
Linear Mode
