From the course: Learning Windows Admin Center

DNS editing in Active Directory - Windows Admin Center Tutorial

From the course: Learning Windows Admin Center

Start my 1-month free trial

DNS editing in Active Directory

“

- I'm logged into the windows domain controller, and from here I'm going to open up tools from our server manager, and go to DNS for the domain name services manager. Now I'm going to do, is I'm going to create an A record just as I did in the previous video on the public DNS. I'm going to do this also on the internal DNS, so that way we can use the same name internally as well as externally to get to the windows admin center gateway. I'll go to the forward lookup zones, and I already have a zone for TechPub.us, if you don't, you can create a new zone by right clicking on the name of the server, and click on 'New Zone' and go through the wizard to create that zone. So it has to point to the domain name itself, which in our case is TechPub.us. All you need to do now is create a new A record, which is a pointer from the name to the IP address. So I'll right click anywhere on the right hand side and click on new host, also known as an A record, and type in the name Gateway. So we see its going to point to gateway.TechPub.us, capital letters do not matter in this particular case so it could be all caps or any kind of mixture. There's the internal IP address, we don't need a pointer record because its not going to be an active directory type of name, this is just going to be a simple A record name. And I clicked 'Add host', click okay, and now done. Now if I open up a command prompt, you can do this through power shell as well, I should be able to type in 'ping gateway.techpub.us'. And there it is, so now its pointing to the internal name. I'm now in a windows 10 client, and I'm going to open up using the new name gateway, open up the supported google chrome, and prompted for the username and password, and we see that we are logging in and our certificate is trusted. Now one of the bugs about this is that it doesn't work the same way on the server in which you installed the admin center gateway, lets take a look. If I put in gateway.techpub.us into fileserver1, in which the admin center is installed, you see it says the page isn't working. However, I can still put in the fileserver1 name and I will get prompted to login, however, it will say the certificate is no longer trusted. And this is a bug that hopefully will be cleared up by the time you watch this video, but it still may not be so just be prepared for that. The admin center is now accessible by name, both internally and externally. It will also not cause any browser certificate warnings since the names in DNS match the certificate name. Of course this works on all different servers and work stations, except the computer in which its installed.

Contents