Server 2016 r2 dns not updating
This is a good step to perform early as when dealing with public DNS servers it can take several hours for these requests to be created and propagate throughout the Internet.
As shown in the diagram each Edge server is assigned 4 unique IP addresses, three on the external network and one on the internal network.
A functional Front End server deployment is required before one or more Edge servers can be deployed into the environment.
This means successfully completing the configuration detailed in at least these three articles: Part 1, Part 2, and Part 3.
But for this article a different, much more verbose approach has been taken.Also the details covered here in the preparation stage are reviewing an already staged environment, the actual Windows Server deployment and configuration steps will not be covered in detail here.The various items required for the actual Edge Server role deployment are identified and outlined but basic Windows Server administration knowledge is assumed.The Server deployment article linked above only covers the unique, individual steps to quickly deploy an Edge Server in a lab with private certificates.This article covers in-depth best practices and explanations of each step along the way to deploying a pair of servers in an Edge Pool leveraging a more realistic scenario using public IP addresses and third-party certificates.