Announcement

Collapse
No announcement yet.

Domain Controller Resolving is to Wrong IP

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Domain Controller Resolving is to Wrong IP

    Hi,

    I m facing strange problem.My Domain Controller Resolving is to Wrong IP Address of other DC's in my domain.Whenever pinging hostname on my domain everytime it provides me other Dc's IP.


    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\admin>ping xyz.net
    Pinging xyz.net [192.168.34.4] with 32 bytes of data:
    Reply from 192.168.34.4: bytes=32 time=43ms TTL=115
    Reply from 192.168.34.4: bytes=32 time=49ms TTL=115
    Reply from 192.168.34.4: bytes=32 time=37ms TTL=115
    Reply from 192.168.34.4: bytes=32 time=43ms TTL=115
    Ping statistics for 192.168.34.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 49ms, Average = 43ms
    C:\admin>ipconfig /flushdns
    Windows IP Configuration
    Successfully flushed the DNS Resolver Cache.

    C:\admin>ping xyz.net
    Pinging xyz.net [192.168.37.4] with 32 bytes of data:
    Reply from 192.168.37.4: bytes=32 time=87ms TTL=115
    Reply from 192.168.37.4: bytes=32 time=73ms TTL=115
    Reply from 192.168.37.4: bytes=32 time=101ms TTL=115
    Reply from 192.168.37.4: bytes=32 time=72ms TTL=115
    Ping statistics for 192.168.37.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 72ms, Maximum = 101ms, Average = 83ms
    ipconfig /flushdns
    Windows IP Configuration
    Successfully flushed the DNS Resolver Cache.
    ping xyz.net
    Pinging xyz.net [192.168.33.4] with 32 bytes of data:
    Reply from 192.168.33.4: bytes=32 time=123ms TTL=124
    Reply from 192.168.33.4: bytes=32 time=128ms TTL=124
    Reply from 192.168.33.4: bytes=32 time=119ms TTL=124
    Reply from 192.168.33.4: bytes=32 time=139ms TTL=124
    Ping statistics for 192.168.33.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 119ms, Maximum = 139ms, Average = 127ms
    C:\Documents and Settings\bkpcitrixadmin>


    C:\admin>nslookup

    Default Server: abc.xyz.net
    Address: 192.168.1.103
    > xyz.net
    Server: abc.xyz.net
    Address: 192.168.1.103
    Name: xyz.net
    Addresses:
    192.168.40.80,
    192.168.168.100,
    192.168.51.100,
    192.168.33.4
    192.168.17.17,
    192.168.49.4,
    192.168.35.4,
    192.168.91.39,
    192.168.52.2
    192.168.91.89,
    192.168.39.4,
    192.168.68.11,
    192.168.95.4,
    192.168.30.2
    192.168.49.131,
    192.168.49.228,
    192.168.16.27,
    192.168.34.4,
    192.168.37.4
    192.168.49.0
    > 192.168.1.103
    Server: abc.xyz.net
    Address: 192.168.1.103
    Name: abc.xyz.net
    Address: 192.168.1.103



    HELP......


    Regards


  • #2
    Re: Domain Controller Resolving is to Wrong IP

    Hi, based on the output you have pasted, it seems everything is correct in your domain.
    Try to ping with the FQDN of DC you want to ping, it will give you the correct IP.

    Since you are pinging with the domain name it will give you one of the IP address from all the SRV record registered in your DNS.

    Comment


    • #3
      Re: Domain Controller Resolving is to Wrong IP

      u right.. If I ping thru FQDN it resolves IP Properly.....But y not otherway.


      Some thing is wrong...!!!

      Comment


      • #4
        Re: Domain Controller Resolving is to Wrong IP

        When you say the otherway, I take it you mean IP to name? Is your DC the ABC? You need to check your reverse lookup zone and delete and update the PTR records as appropriate.

        Comment


        • #5
          Re: Domain Controller Resolving is to Wrong IP

          My Domain is xyz.net and its hostname is abc.xyz.net and IP for the same is 192.168.1.103.

          If I go for nslook up u will find below result which seems to be right.
          C:\admin>nslookup
          Default Server: abc.xyz.net
          Address: 192.168.1.103
          > xyz.net
          Server: abc.xyz.net
          Address: 192.168.1.103
          Name: xyz.net
          Addresses:
          192.168.40.80,
          192.168.168.100,
          192.168.51.100,
          192.168.33.4
          192.168.17.17,
          192.168.49.4,
          192.168.35.4,
          192.168.91.39,
          192.168.52.2
          192.168.91.89,
          192.168.39.4,
          192.168.68.11,
          192.168.95.4,
          192.168.30.2
          192.168.49.131,
          192.168.49.228,
          192.168.16.27,
          192.168.34.4,
          192.168.37.4
          192.168.49.0

          Apparently whenever I ping with hostname of Domain i.e xyz.net it resolves from any of other DC's available.If I m looking to DNS Server setting everything seems ok.All other DC's details are added in Name server setting. in forward and reverse lookup setting.I can't make much change in DNS untill not sure of root cause in live scenario. .


          A

          Comment


          • #6
            Re: Domain Controller Resolving is to Wrong IP

            Lets get some things clear first, XYZ.net is your Domain. ABC.XYZ.net is the FQDN of a Node (Workstation/Server) on your Domain XYZ.net.

            Second, when you have multiple Domain controllers you're going to usually ping the domain controller you've authenticated to if you ping XYZ.net. You may get one server or another. Usually a DC in the same site as you, if there are multiple DC's then usually one you've authenticated to.

            Do this for me, nslookup all your hostnames (forward) and then by ip's (reverse) and make sure they match. From what you've stated in the first post the host is a DNS/Domain controller. You must add this DC to the Name servers of the zone you're using to get forward addresses from, zone XYZ.net AD integrated Primary (usually replicating Domain wide).

            Now you may have some lingering records in your DNS for old servers. In your XYZ.net zone make sure there aren't any A records (same as parent folder) that aren't DC's.

            If there are not errors, is it just being anal?
            Last edited by stamandster; 27th May 2009, 15:10.
            GoogleFu is strong with this one ^

            Comment


            • #7
              Re: Domain Controller Resolving is to Wrong IP

              It is very simple..
              Since you are pinging with the domain name it will give you one of the IP address from all the SRV record registered in your DNS.
              and as stamandster said
              "when you have multiple Domain controllers you're going to usually ping the domain controller you've authenticated to if you ping XYZ.net. You may get one server or another. Usually a DC in the same site as you, if there are multiple DC's then usually one you've authenticated to."

              Comment


              • #8
                Re: Domain Controller Resolving is to Wrong IP

                Looking at your original mentioned issue, you state that

                I m facing strange problem.My Domain Controller Resolving is to Wrong IP Address of other DC's in my domain.Whenever pinging hostname on my domain everytime it provides me other Dc's IP.

                However, you are pinging the 'domain name' during the tests and not the hostname as you mention.

                If you are not experiencing any problems with the domain, I would say that you have nothing to worry about. It is normal behaviour.

                Comment


                • #9
                  Re: Domain Controller Resolving is to Wrong IP

                  Agreed that due to multiple Domain Controllers SRV Record registered in my DNS m getting IP addresses of different DC's.
                  Is there any way to put priority or setting on server end so that If I ping my domain name xyz.net it resolves only IP of my Domain hostname abc.xyz.net i.e 192.168.1.103 from different subnets of my whole network.

                  Comment


                  • #10
                    Re: Domain Controller Resolving is to Wrong IP

                    Not that I'm aware of. You can check in AD Sites ad Services at the DC node properties in there to see if there is a option. You can look at the SRV record properties.

                    Also, if you have a DC at each site, clients will first go to that DC.

                    Comment


                    • #11
                      Re: Domain Controller Resolving is to Wrong IP

                      Maybe you could fill us in on the real issue here. Surely pinging the domain FQDN and getting a response from the same DC is not what you're really trying to solve. How is this a problem for you? What are you trying to fix? Do you have multiple sites and are trying to figure out why clients authenticate to the wrong DC?

                      Comment

                      Working...
                      X