ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Resolved (Pertino client bug): DNS Records Not Updating Automatically

    Scheduled Pinned Locked Moved IT Discussion
    5 Posts 3 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • wrx7mW
      wrx7m
      last edited by wrx7m

      I noticed today that when I was trying to connect to a windows 7 client with a UNC, it wasn't giving me the correct system. I started investigating and found several computers that had DHCP addresses that were different than what my DNS servers where showing.

      I found that my DNS servers had scavenging set for 3 days and my dhcp scope was set to 1 day leases. I changed the scavenging and then made sure that I selected to scavenge for stale resource records. This did not seem to have any effect on the records.

      I then started testing using a test system. I got an IP address for the DHCP server and saw the hostname. I checked DNS and it was correct. Next I changed the IP address from DHCP to a static one and specified the proper DNS servers. It has been about 45 minutes and DNS still shows the old ip address in the forward lookup zone.

      So it looks like it will add new records but not update existing ones.

      I started wondering if this had something to do with installing the Pertino client on my DCs last Friday but am not sure. To be safe, I have uninstalled it from all 3 DCs. I am still facing this issue.

      Server 2008 R2 and Server 2012 R2 DCs running DNS and Server 2012 R2 DHCP server

      1 Reply Last reply Reply Quote 0
      • nadnerBN
        nadnerB
        last edited by

        Just checking, have you enabled dynamic updating of A and PTR records in DHCP?

        DHCP --> Server --> scope (Right Click) --> Properties --> DNS

        • Check the box for Enable DNS dynamic Updates ...
          Select: Always dynamically update...
        • Check the box for Discard A and PTR records...
        • Check the box for Dynamically update DNS A and PTR ...
        wrx7mW 1 Reply Last reply Reply Quote 1
        • wrx7mW
          wrx7m @nadnerB
          last edited by wrx7m

          @nadnerB Yes thanks. I think I have traced it to the Pertino client being installed on the DCs. I am waiting to hear back from them but basically every time I uninstall the client from my DCs, client systems that do not have anything to do with Pertino start working again. Once I install it again, the records stop updating dynamically when the IP address changes. I tried it about 4 or 5 times can reproduce the results every time.

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @wrx7m
            last edited by

            @wrx7m said:

            @nadnerB Yes thanks. I think I have traced it to the Pertino client being installed on the DCs. I am waiting to hear back from them but basically every time I uninstall the client from my DCs, client systems that do not have anything to do with Pertino start working again. Once I install it again, the records stop updating dynamically when the IP address changes. I tried it about 4 or 5 times can reproduce the results every time.

            Do you have the DCs assigned as DCs in Pertino?

            wrx7mW 1 Reply Last reply Reply Quote 1
            • wrx7mW
              wrx7m @scottalanmiller
              last edited by wrx7m

              @scottalanmiller Thanks, I did have them assigned as dedicated resources/DCs.

              It was definitely a bug in the Pertino client (build 520):
              So after dealing with Pertino support, they recommended I try the previous build (510) and that seems to have corrected the issue. They mentioned there were some other problems that led them to pull down the 520 build from the site and replace it with the 510. Support said that a new build (526) should be released soon.

              1 Reply Last reply Reply Quote 3
              • 1 / 1
              • First post
                Last post