Announcement

Collapse
No announcement yet.

dns issue

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

  • dns issue

    We had an older server name xxxx01 running 2k3 with ip address 1.2.3.4, I built a new never name xxxx04, shutdown xxxx01 and assign ip 1.2.3.4 the xxxx04.
    My problem now is that i'm able to ping xxxx01 which resolve to 1.2.3.4 but for some xxxx01 still reply to it's old ip of 1.2.3.4. I've checked dns for any old entries and also manually scavange for stale or old records. Any help will be great.


    Mark

  • #2
    Re: dns issue

    run ipconfig /flushdns on the client - there is a client side cache and it takes it a while till it's flushed/refreshed.
    "ipconfig /displaydns" will show you the cached data on the client
    Guy Teverovsky
    "Smith & Wesson - the original point and click interface"

    Comment


    • #3
      Re: dns issue

      this migration was done last night. I've done the ipconfig /flushdns and registerdns.

      mp

      Comment


      • #4
        Re: dns issue

        Do you have WINS servers hanging around ?
        Guy Teverovsky
        "Smith & Wesson - the original point and click interface"

        Comment


        • #5
          Re: dns issue

          Yes my first AD server has wins installed.

          Comment


          • #6
            Re: dns issue

            I've uninstall wins on all servers.

            Mark

            Comment


            • #7
              Re: dns issue

              I did a scan of my registry for all instance of the old server. After deleting and rebooting the keys, i'm no longer able to ping the old AD server.
              Thanks for your help.

              Comment

              Working...
              X