Re: duplication when setup.... ie: acme.acme.com

From: randy (randy_at_discussions.microsoft.com)
Date: 07/29/04 

Date: Wed, 28 Jul 2004 20:55:05 -0700

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> In news:7036BA45-5685-41E0-BAE4-F1D9E95D8750@microsoft.com,
> Randy <Randy@discussions.microsoft.com> posted a question
> Then Kevin replied below:
> > "Kevin D. Goodknecht Sr. [MVP]" wrote:
> >
> >> In
> >> news:47EF15EF-C50A-4180-BBD1-73C8157841E9@microsoft.com,
> >> Randy <Randy@discussions.microsoft.com> posted a question
> >> Then Kevin replied below:
> >>> I have been asked to help an organization fix a problem
> >>> with their server; they had a crash and now their backup
> >>> DNS is also not working correctly. I say this cause I
> >>> do not know anything about how the original config
> >>> procedures.
> >>>
> >>> I've tried everything I can think of, even a second
> >>> server they have set up. The problem is basically when
> >>> I install the DNS or have the AD wizard install the DNS,
> >>> the server always thinks its DNS entry is
> >>> "acme.acme.com". (This information is found by doing
> >>> 'config /all' from the DOS prompt.) YET, when you go
> >>> into the DNS manager, it shows as "acme.com". The
> >>> problem is verified, since when pinging my server
> >>> (acme.com) if fails, but I can ping 'acme.acme.com'.
> >>>
> >>> My domain is a private domain (not registered), and I've
> >>> tried setting it up with an Internet connection and
> >>> without. I've tried with the wizard and without -
> >>> separate from active directory and with, I've tried
> >>> changing the netbios name (which creates the 'windows
> >>> domain name'), and no success. Everything I try comes
> >>> up the same.
> >>>
> >>> Is this information in some configuration file or in the
> >>> registry some place? Does anyone have any idea what's
> >>> wrong with the environment? I'm at a loss. Thanks for
> >>> your assistance.
> >>
> >> You can't change the domain name, but three things
> >> _must_ match exactly. The Primary DNS suffix
> >> The Active Directory Domain name in AD User & Computers
> >> The forward lookup zone in DNS.
> >>
> >> Maybe your domain name is acme.acme.com, it could be
> >> worse, it could be acme.com or just acme. If you ask why
> >> acme.com is worse that acme.acme.com it is because all
> >> your domain members must use the internal DNS server
> >> only, and that DNS server must have a zone for the AD
> >> domain name. If your domain name is acme.com then you
> >> would not be able to resolve any name in the acme.com
> >> domain on the internet, because DNS will not forward for
> >> domain names it is authoritative for.
> >>
> >> That being said can you post the three items I mentioned
> >> above?
> >>
> >> --
> >> Best regards,
> >> Kevin D4 Dad Goodknecht Sr. [MVP]
> >> Hope This Helps
> >> ============================
> >> --
> >>
> >
> > Then Kevin replied below:
> >> I have been asked to help an organization fix a problem
> >> with their server; they had a crash and now their backup
> >> DNS is also not working correctly. I say this cause I do
> >> not know anything about how the original config
> >> procedures.
> >>
> >> I've tried everything I can think of, even a second
> >> server they have set up. The problem is basically when I
> >> install the DNS or have the AD wizard install the DNS,
> >> the server always thinks its DNS entry is
> >> "acme.acme.com". (This information is found by doing
> >> 'config /all' from the DOS prompt.) YET, when you go
> >> into the DNS manager, it shows as "acme.com". The
> >> problem is verified, since when pinging my server
> >> (acme.com) if fails, but I can ping 'acme.acme.com'.
> >>
> >> My domain is a private domain (not registered), and I've
> >> tried setting it up with an Internet connection and
> >> without. I've tried with the wizard and without -
> >> separate from active directory and with, I've tried
> >> changing the netbios name (which creates the 'windows
> >> domain name'), and no success. Everything I try comes up
> >> the same.
> >>
> >> Is this information in some configuration file or in the
> >> registry some place? Does anyone have any idea what's
> >> wrong with the environment? I'm at a loss. Thanks for
> >> your assistance.
> >
> > You can't change the domain name, but three things _must_
> > match exactly.
> > The Primary DNS suffix
> > The Active Directory Domain name in AD User & Computers
> > The forward lookup zone in DNS.
> >
> > Maybe your domain name is acme.acme.com, it could be
> > worse, it could be
> > acme.com or just acme. If you ask why acme.com is worse
> > that acme.acme.com
> > it is because all your domain members must use the
> > internal DNS server only,
> > and that DNS server must have a zone for the AD domain
> > name. If your domain
> > name is acme.com then you would not be able to resolve
> > any name in the
> > acme.com domain on the internet, because DNS will not
> > forward for domain
> > names it is authoritative for.
> >
> > That being said can you post the three items I mentioned
> > above?
> Let me give a little more background...
> We have 2 servers, a PDC and a BDC (or server 1 & 2 if you prefer.) The PDC
> server crashed a while back and since it's taken them a while to make it
> work, their BDC has seized the A/D roles and is functioning as a single
> server domain. The BDC is also functioning as DNS, DHCP, etc.
>
>
>
> Let me start by saying this, in Win2k there is no such thing as a BDC, there
> is only DCs and the PDC emulator is only one of the five FSMO roles.
>
> If you are trying to create a new domain, it is going to have to be a
> different NetBIOS and DNS name. If they have a DC already in acme.com with
> users and computer accounts, all you need to do is promote the new DC as a
> replica of the existing DC.
>
> So as of right now I don't know what you are asking, so I need to see the
> three items I asked for and a clear explantion of the task you are trying to
> do.
>
> When you say you removed all services, what exactly does that mean?
>
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
> ============================
> --
> When responding to posts, please "Reply to Group" via your
> newsreader so that others may learn and benefit from your
> issue. To respond directly to me remove the nospam. from my
> email. ==========================================
> http://www.lonestaramerica.com/
> ==========================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ==========================================
> Keep a back up of your OE settings and folders with
> OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ==========================================
>
>
>

First, I do understand AD, Right there is no PDC or BDC, the client actually named them that which I woudl hoping you would catch by my comment or call them server 1 or server 2 if you like and commented about siezing the global catalog.

Since PDC is less letters (typing) than 'server 1', I'm going to continue to call it PDC. I hope that you can work with that. If not, let me know and I'll come up with another short acronym to save typing.

I cannot explain it any better than I just did. I realize it's confusing, so lets start over. lets also kee it simple.

I have a new server, PDC. It is the only server on my test network and I have 1 workstation. There is a gateway to the internet (A seperate device). There are no other computers, and no other domains in this test network. Every time I use the AD wizard my 'nslookup' says the domain is 'acme.acme.com' yet when installing A/D I never typed anything but acme.com. why does nslookup point to my server do a lookup and tell me it's doing a DNS lookup from acme.acme.com?

The names under the network tab of the "my computer" properties have the computer names as PDC, and the netbios name as acme (I've also tried 'test' and other options for the netbios name).

If I open the DNS manager tool from the 'administrator tools menu' it tells me my heirarchy is in the format of 'root/servername/forwardlookup/zone', DNS/PDC/ForwardLookupZones/acme.org.

I hope that was straight-forward enough. I believe my problem is visible at this point. That problem being WHY does nslookup say my DNS server name is 'acme.acme.com' when my DNS manger forward lookup zone says it's 'acme.com'?

:Randy

Relevant Pages

  • Re: DNS Forward lookup problem - now having problems with a period (.)
    ... we have had sporadic problems on our network. ... Chances are you have some that are still pointing at the lost DNS ... If you have more than one Domain, every DNS server must ... > recreate the forward lookup zone on our AD-integrated DNS Server (which ...
    (microsoft.public.windows.server.dns)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... AD-Integrated DNS does not do zone transfers between the ... your DNS server will bypass ...
    (microsoft.public.windows.server.active_directory)
  • Re: Servers hang on boot
    ... The last DC at that site (not a DNS server). ... EventID: 0x00000457 ... (Event String could not be retrieved) ...
    (microsoft.public.windows.server.networking)
  • Re: DNS Redesign Issue
    ... set the new child domain DNS server as primary for the domain controllers? ... -If you are going to create a new AD Integrated Zone in each child domain, ...
    (microsoft.public.windows.server.dns)
  • Re: Reverse Lookup Zone record problem
    ... I've tried torun aging and scavenge on DNS server, ... I've also set up DHCP to dynamic update DNS A and PTR records. ... In the Forward Lookup Zone: ...
    (microsoft.public.windows.server.sbs)