Easier LsAgent migrations with Smart DNS Records.

[#1]

Moving Lansweeper installations to new servers can be tricky. Every LsAgent deployed across your network needs to know where the server is. If you move the Lansweeper Server from svr01.example.com to svr02.example.com, you normally need to update the LsAgent settings on each device. This can take hours, especially in large environments.

What is going on
LsAgent uses a fixed endpoint to send data back to the Lansweeper Server. If the server address changes, and you’ve hardcoded the old address into your LsAgent deployment, those agents can’t reach the new server. Updating those endpoints means pushing new configs or redeploying agents—a time-consuming task.

How can I fix this
There’s a simpler, smoother way: use a friendly DNS alias.

• Create a DNS CNAME Record
  Set up a DNS entry like lansweeperlsagent.example.com. Point it to your current server, for example, svr01.example.com.

• Configure LsAgent to Use the Alias
  When installing LsAgent or updating its settings, use lansweeperlsagent.example.com as the server address. This becomes the stable point of contact.

• Migrate with Confidence
  When it’s time to move Lansweeper from svr01 to svr02, all you do is update the DNS entry. Point lansweeperlsagent.example.com to svr02.example.com. The LsAgents will automatically reroute to the new server without needing reconfiguration.

• Verify Resolution
  Once the DNS change is made, ensure clients resolve lansweeperlsagent.example.com to the new server. Use DNS tools like nslookup or dig to confirm resolution.

• Keep It Going
  This method also helps for future changes or failovers. Your agents will always follow the DNS pointer, so they stay connected, even as your backend evolves.

Why this works
DNS aliases provide a fixed name that always points to the right place. It decouples the server name from the endpoint configuration. That way, the LsAgent only needs to remember one name, even if the server behind it changes.

Final Tip
Apply short TTL (Time To Live) on this DNS alias during migrations. This forces clients to check DNS more often, picking up changes faster.

With this smart DNS setup, shifting Lansweeper Servers becomes easier, faster, and less risky. You stay in control, and your network stays connected.