Active Directory network topology DNS problem

Home Forums Server Operating Systems Windows Server 2000 / 2003 / 2003 R2 Active Directory network topology DNS problem

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    lacko
    Member
    #153912

    I have a four Domain Controlers divided in 3 sites (same domain lacko.me).

    Site A (subnet 192.168.0.0/24) 2 DCs (IP 192.168.0.100 and IP 192.168.0.200)
    Site B (subnet 10.16.0.0/24) 1 DC (IP 10.16.0.100)
    Site C (subnet 10.24.0.0/24) 1 DC (IP 10.24.0.100)

    When client from site A (IP address 192.168.0.55/24, primary DNS 192.168.0.100, secondary DNS 192.168.0.200) try to resolve lacko.me sometimes gets address from site B (IP 10.16.0.100) and site C (IP 10.24.0.100) for domain lacko.me.

    Due to network connectivity client from the site A can reach only DCs on a site A.

    How can I fix DNS to sends responses to clients depending on the network topology.

    The goal is that customers who belong to the A site always gets DCs IP addresses from site A when resolving lacko.me.

    Whan i try nslookup lacko.me from client (192.168.0.55/24) periodically I get 10.16.0.100, 10.24.0.100 addresses and because of that client may not downloading GPOs.

    I try ipconfig / flushdns but it solves the problem temporarily.

    I try from client PC \lacko.mesysvol properties DFS (distribution file system) and check Yes for DC from site A but this solves the problem temporarily.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.