Re: WINDOWS RAPLICATION ISSUE



Hello mastermind,

hI

i am facing following issue.My domain toplogy is as follow.

I am having single forest with Multiple domain in my each geogaphical
location.

mY Head office in DUBAI. hAVING ROOT FOREST DOMAIN
mY BRANCH OFFICE singapore ,kuwait, doha having domain controller with
in
same forest.
I am haiving single GC located at dubai .
All location singapore ,kuwait ,doha having Local DNS SERVER with AD
integrated.
Same way My head office also hev local DNS server.

YOu havent given details of the multiple domains. I assume each country (singapore, kuwait) is its own domain. I also assume each country has at least one DC for their own domain that also runs DNS.

What you havent done is provide details of the DNS Setup. Do you have one zone per AD domain or do you have one single zone to support all of this.

My issue is
1) I am unable to resolve kuwait ,doha & singapore domain by nslookup
but I
am able to do dns look up from kuwait ,doha & singapore branch to my
head
office domain .

First things first. You need to solve the DNS issues. This is critical for AD. If it makes things simple, I recommend configuring all domain controllers globally to use one DNS server initially. That means let the DNS run on all domain controllers as is. But configure each domain controllers, DNS section in TCP/IP settings to point to one DNS. I recommend configuring this all to point to the root domain for now. I.e. Dubai

You also fail to mention when doing your nslookup queries where you are doing this from. You also fail to say which DNS servers you are querying. Therefore to make things simple I suggest configuring your nslookup session to use the DNS server of the root domain (Dubai).

Once all domain controllers have been configured to point to Dubai DC for DNS, ensure dynamic updates are enabled on the DNS zone at Dubai. Next restart the netlogon service (one at a time) on each DC of all other countries. This will ensure each DC attempts to register its records in DNS again. Once this complete, you can ensure the correct records are available by runnning the following command on each DC. dcdiag /test:Dns

If you run dcdiag /test:dns /fix it will attempt to register records that are missing. My experience with this has been OK. Albeit it doesnt always seem to work.

Dnslint from http://support.microsoft.com/kb/321045 is a great way to ensure your DNS is healthy. Extract the files to anywhere. Doesnt have to be a DC; a PC will also do. Then run the following

dnslint /ad domain_controller_IP_Address /s Root_Domain_DNS_DC

This will make an HTML file with results. Subsititute Root_Domain_DNS_DC for the IP address of the DUbai DC which is now running DNS with all records.

2) I am not able to do raplication automatically as well as mannually.

Once you get DNS working, replication should also start to work.

Please post updates.

HTH

M@


.



Relevant Pages

  • Re: WINDOWS RAPLICATION ISSUE
    ... I am running nslookup & DNS QUERY from my dubai server. ... All location have OWN dc as well as local DNS SERVER. ... Alias and glue records for forest GUIDs from server: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Directory Services Not Starting on DC
    ... The primary DNS server for each site ... The secondary DNS server in the head office ... I would then like to rebuild DC1 and have it take over the ...
    (microsoft.public.windows.server.active_directory)
  • 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)