web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Changing AOS cluster name and IP address

(0) ShareShare
ReportReport
Posted on by

Hey There,

In my company we have built a new live Environment with Multiple AOS's and Load Balancer.

My question is when going live the it Department Suggested once the change is going they will change the server name with new ip in the DNS, they showed me demo and it's working, but i feel there is something not working fine, so what the impact if 600 users worked that way ?? 

*This post is locked for comments

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    304,508 Super User 2026 Season 1 on at

    Hi Mohammed,

    Please elaborate. Which IP addresses from which server(s) will be changed? The old or the new ones?

  • Community Member Profile Picture
    on at

    Old Aos name is : AOSSERVER with ip : ***.**.*.142

    New Aos Name(AXLB) name is : AXLB with ip : ***.**.*.243

    Clients Configuration used to look at the old server (AOSSERVER), so they changed in DNS the Ip of AOSSERVER to 243 , so now if we ping AOSSERVER it replies with ip 243, and so clients are now connected to the new aos.

    But i feel that this solution is not right, so am i overreacting or what ?

  • André Arnaud de Calavon Profile Picture
    304,508 Super User 2026 Season 1 on at

    Hi Mohammed,

    I don't follow how it has been done exactly. To prevent any DNS issues (e.g. DNS server not available), I always recommend to setup IP addresses on the client configurations anyway.

  • BorisD Profile Picture
    2,826 Moderator on at

    Hello Mohammed,

    I would not recommend the suggestion from the your IT Department to change the A record in DNS to look like it is a server that it isn't.

    This would be a troubleshooting nightmare for anyone in the future. If someone down the line decides to do some Active Directory cleanup and forgets about this entry, then removes the DNS record because they think that server no longer exists. All your client will have problems connecting.

    This is just a really bad idea. Take the time and do it right now, because once you are live it will be a lot harder to fix this.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 39

#2
Michel ROY Profile Picture

Michel ROY 14

#3
imran ul haq Profile Picture

imran ul haq 8

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans