DNS (Domain & Workgroup)

[Miguel Angel Miranda]

Hi!
Actually I've a domain called CCSC and it works fine, but recently,
we add a new unit to the organization, a general Warehouse, and for
organization questions, we require that stay separate of our domain.
Therefore, we made a called workgroup " warehouse", but the
problem it is that I can't make that these PC's registers in our internal
DNS.
The IP for the DNS is 127.0.0.1 (eg) and all (11) PC's points to this IP
as Primary DNS.
How I can to make so that they register in my DNS and therefore in
does the one Active Directory??

I hope you can help me.

Thank you!!

 

[Ace Fekay [MVP]]

Sounds like a couple things going on here. First, it appears you have a
single label DNS domain name. An example of a single label DNS domain name
is CCSC. PRoper name would be ccsc.com or ccsc.miguel, etc. This is not
recommended with AD. If it is single label name, and you have SP4 installed,
then I would follow this article to force registration:
http://support.microsoft.com/?id=300684

As for the DNS address, 127.0.0.1, that is the local loopback and not a
valid IP. DCPROMO probably put that in there for you, because you can't do
it thru the GUI. I would change it to the actual IP address of the server
itself.

Here's the SIMPLE rules for Dynamic Updates (assuming either an AD
environment or not):

1. Primary DNS Suffix of the machine MUST be the zone name of AD or the
zone name you want to update to.
2. Point ONLY to the DNS server hosting this zone (no other servers
whatsover unless they host a copy of this zone also for fault
tolerance). If you use your ISP's in your properties, it probably will
not work and it may try to update to their servers and you'll get
errors stating so.
3. Enable Updates on the zone (set it to at least YES).
4. If AD, make sure the Primary DNS Suffix and the zone name in DNS are
spelled EXACTLY the same.
5. If not AD, make sure the Primary DNS Suffix is spelled EXACTLY as the
zone name in DNS.
6. If a reverse zone, make sure the reverse zone is created EXACTLY to
reflect the actual subnet your machine is on.
7. If using DHCP, specify Option 006 to be ONLY the internal DNS servers
that host a copy of this zone.
8. If using DHCP, specify option 015 the Primary DNS Suffix.
9. If using DHCP and you have legacy clients, specify Option 081 to
force registration for clients that cannot (that's in DHCP properties,
DNS tab, check off the box).

Netlogon uses the Primary DNS Suffix to register that same name zone
into DNS. If in a workgroup, the DNS Suffix has to be manually set to the
zone name in DNS that you want it to register into or you can use Option 015
in DHCP to force it (as outlined above).

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[vinnie]

if you i.p is class C such as 192.168.1.xxx
you can not set 127.0.0.1, you can only set 127.0.0.1
is on Windows 2003 server.