Sometimes, SMB, for example, doesn't play well with CNAME or additional A records. Firstly, though it may not be the simplest solution, it does ensure that as much as possible will continue to work with the new name. "netdom computername (current FQDN of system) /makeprimary (alternate FQDN)"įrom there, you will need to restart the server for the name change to take effect and for the server to register its changes with DNS. ![]() In that case, you can perform this command immediately after you perform the previous one: Note that the above command also works if you are changing the name of the system. "netdom computername (current FQDN of system) /add (alternate FQDN)" After that installation, you can use the following command inside a regular cmd prompt (no need for PowerShell) to not change, but rather add a computer name to the system. However, you can install the Remote Server Administration Tools for AD and this command should be included with the installation. As it's not a domain controller, it will not have this command by default as it is include with the AD DS role. Instead of just creating a DNS record, there is another way. In my experience, however, I suggest doing something slightly different. I see all of the other answers here suggest that you add a A record or a CNAME record to the DNS zone database. Add a new A record to the zone and leave the name field blank, and specify the static IP of the TFS server.Add a new active directory integrated / primary zone.This method is useful for an “internal use only” site and eliminates the risk identified in the previous suggestion. This method is necessary if you intend to have TFS accessible externally.Īlternatively, you can add the zone to your AD DNS server. There is a very small risk of exposing your internal network IP scheme to an attacker, but the information is virtually useless without other attack vectors being exploited. ![]() It is OK to use a private IP address for that A record if TFS is only accessible internally. The simplest thing to do is to add an A record for with the DNS server that is hosting your domain, which is probably a 3rd party. ![]() Because your internal AD domain is and the domain name you want to use is you will not be able to create a CNAME record in your AD dns server as suggested in previous answers.
0 Comments
Leave a Reply. |