Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Recently I used a server to run some of my websites, but the computer name was something gibirish (like W8-SmgN138-B blah blah).

I didn't like this name, however, I didn't change it till recently I just felt really annoyed with it (For connecting to database server, web server, etc.)

So, I changed it to something new, say "MyServer".

After restarting Windows, I saw that in IIS, the server name is changed automatically. However, in DNS records, the old name still appears. In other words a records like:

Name Server: W8-SmgN138-B.

hasn't been changed to become:

Name Server: MyServer.

What should I do? Should I manually change all of these names? Why they don't pull the computer name from a centralized place?

My server is not joined to a domain, and is in fact the only member of the default WORKGROUP. DNS server is also installed on the same physical machine, just like web server (IIS), mail server, etc. This is a personal server, and doesn't have high load, thus everything including database server (MS SQL Server) is installed on it.

share|improve this question
    
Saeed, for info, questions relating to home/personal server issues are not within the scope for this site. The FAQ details this. I've voted to migrate your question to the sister site, SuperUser, which is a better fit for this question. p.s. I've updated my answer below. –  Bryan Mar 11 '12 at 14:16

1 Answer 1

Your question is somewhat lacking in detail, so I'm going to have to make the following assumptions.

  • You are using Active Directory, and the server is a member of the domain.
  • DNS is running on your domain controllers, and accepts dynamic updates.

If these assumptions are incorrect, please edit your question and add the correct details so a better answer can be provided.

When you rename a computer that is a member of an Active Directory domain, the computer will attempt to re-register itself in DNS, and remove the old DNS entry.

You don't specify how you are querying DNS? Are you using nslookup or similar, if so, you might be seeing cached results.

Does nslookup MyServer actually resolve? If so, you might find that ipconfig /flushdns (or a little patience) is all that you need to clear the old name from your DNS queries.

If you aren't a member of an AD domain, or you aren't using dynamic DNS, then the chances are that you will need to manually update your DNS records, or switch configure your DNS server to accept dynamic updates. A little more info in your question will help you get a better answer if this is the case.


Edited answer for updated question:

You have two options, either enabling dynamic updates on your DNS server, or probably easier in your configuration, just update the DNS records manually.

To configure dynamic updates in the DNS server.

1. Configure your server

On your server, open the DNS administrative tool and expand the tree to show your server, and expand Forward Lookup Zones. Right click the relevant forward lookup zone and click properties, on the general tab, you will find the Allow dynamic updates dropdown box, you need to select the option that allows 'non secure updates' for your configuration. Click OK to close all dialog boxes.

2. Configure your clients

On each workstation, open the properties for the network interface, and drill down into the TCP/IP properties. You will find a DNS tab, which contains two checkboxes at the bottom for 'Register this connection's address in DNS' and 'Use this connections DNS suffix in DNS registration'. Ensure both of these checkboxes are ticked.

Update the DNS records manually.

In the DNS management tool, locate the out of date DNS A Record for your server, right click on it and select 'Delete'. Now right click on a blank part of the screen (or right click on the forward lookup zone) and select the option to add a new A record. Give the A record the new hostname and the IP address of your server.

Moving forwards.

If you're planning to add more computers to the network in the future, you might want to consider adding active directory to your network, as it makes configuration of systems so much easier. Be warned though, you really should have a minimum of two domain controllers, and don't make a server into a domain controller if it is exposed to the internet (e.g. runs a public IIS or mail server).

share|improve this answer
    
Hi @Bryan, thanks for responding. I updated the question. I'm not joined to a domain and the DNS server is installed on the same physical machine. I use DNS MMC to manage DNS records, and as I can clearly see there, some records are not updated automatically. Also, I don't know how to config my DNS to accept dynamic updates. –  Saeed Neamati Mar 11 '12 at 6:43

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.