In
Tomboy said:
Hi
I have an W2K03 AD with 2 DC's I have built a 3rd server from scratch,
joined to domain, installed dns and then run dcpromo. The server
added ok no errors, however after 24 hours the DNS domain had fialed
to replicate, and the server was not sharing the sysvol folder and
thus was not operating as a dc. I rebuilt the server and exactly the
same. I then rebuilt a 3rd time before joing to domina i ran ipconfig
/registerdns and got the following error:
Registration of DNS records failed: The RPC server is unavailable.
Has anyone seen this and is this causing the DNS repl to fail and
stopping the server from being a DC properly?
The server is brand new and had a fresh install of W2K03
Things to keep in mind to insure AD functionality (including replication,
RPC communication, authentication, etc etc etc), and just to note, by
default, registration just works as long as:
1. The Primary DNS Suffix matches the zone name that is allowing updates.
Otherwise the client doesn't know what zone name to register in. You can
also have a different Conneciton Specific Suffix in addition to the Primary
DNS Suffix to register into that zone as well.
2. The DNS addresses configured in the client's IP properties must ONLY
reference the DNS server(s) hosting the AD zone you want to update in. You
cannot use an external DNS in any machine's IP property in an AD
environment. You can't mix them either. That's because of the way the DNS
Client side resolver service works. Even if you mix up internal DNS and
ISP's DNS addresses, the resolver algorithm can still have trouble asking
the correct DNS server. It will ask the first one first. If it doesn't get a
response, it removes the first one from the eligible resolvers list and goes
to the next in the list. It will not go back to the first one unless you
restart the machine, restart the DNS Client service, or set a registry entry
to cut the query TTL to 0. The rule is to ONLY use your internal DNS
server(s) and configure a forwarder to your ISP's DNS for efficient Internet
resolution.
3. DHCP Option 006 for the clients are set to the same DNS server.
4. If using DHCP, DHCP server must only be referencing the same exact DNS
server(s) in it's own IP properties in order for it to 'force' (if you set
that setting) registration into DNS. Otherwise, how would it know which DNS
to send the reg data to?
5. If the AD DNS Domain name is a single label name, such as "EXAMPLE", and
not the proper format of "example.com" and/or any child of that format, such
as "child1.example.com", then we have a real big problem. DNS will not allow
registration into a single label domain name.
This is for rwo reasons:
1. It's not the proper hierachal format. DNS is
hierarchal, but a single label name has no hierarchy.
It's just a single name.
2. Registration attempts causes major Internet queries
to the Root servers. Why? Because it thinks the
single label name, such as "EXAMPLE", is a TLD
(Top LEvel Domain), such as "com", "net", etc. It
will now try to find what Root name server out there
handles that TLD. In the end it comes back to itself
and then attempts to register.
Due to this excessive Root query traffic, which ISC found from a study that
found Microsoft DNS server causing excessive traffic because of single label
names, stopped the ability to register into DNS with Windows 2000 SP4, XP
SP1, (especially XP,which cause lookup problems too), and Windows 2003.
6. AD/DNS zone is not configured to allow dynamic updates, whether Secure or
Secure and Non-Secure. If a client is not joined to the domain, and the zone
is set to Secure, it will not register either.
7. 'Register this connection's address" on the client is not enabled under
the NIC's IP properties, DNS tab.
8. Maybe there's a GPO set to force Secure updates and the machine isn't a
joined member of the domain.
9. DHCP client service not running. This is a requirement for DNS
registration and DNS resolution even if the client is not actually using
DHCP.
So in essence, as long as you do not reference any DNS servers that do not
host the AD zone, (no ISP's DNS servers can be in any machine's IP
properties),
and you leave everything else default, this just works. No registry
modifications
are required.
If you feel this wasn't helpful, I think it's time to ask for more specific
configuration information to better assist, such as:
1. ipconfig /all from a client and from your DC(s)
2. The DNS domain name of AD (found in ADUC)
3. The zonename in your Forward Lookup Zones in DNS
4. If updates are set to allow under zone properties
5. If this machine has more than one NIC
6. Do you have a firewall separating the DCs? If so, what brand?
7. Is/are forwarder(s) configured?
8. Do the SRV records exist under your zone name?
9. Event ID errors?
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
