This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 26%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
Getting the below warning in AAM. We have two web front end servers.
websp2 is not configured currently. Can we have custom zone for websp1 and websp2.
If the machine names are "<blank>webspN", then this is why the rule is calling out the AAM. You need to not use the machine name as an AAM. Since you have two servers, you should be using a load balancer in front of the two FEs, map a DNS A record to virtual IP address on the load balancer, and that virtual IP address forwards to your SharePoint servers. Your SharePoint servers should have an AAM mapping the FQDN to your Web Application.
The client does not have load balancer configured for the SharePoint Farm. The client uses http://intranet to access the web front server websp1 and websp2. However websp2 is not configured in AAM.
Without a load balancer, how are you going to route traffic to >1 server? You don't want to use DNS round robin as that won't be able to detect a downed server.
Your client needs a load balancer. There are plenty of free options such as HAProxy.
Hi @Sajith Gopalakrishnan Hema , do you have any progress on this thread? Please feel free to let us know if you need further assistance.