Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I used to have a network setup as follows: -> Server 1 (XXX.XXX.XXX.1) -> Server 2 (XXX.XXX.XXX.2)

Server 1 simply redirected all port 80 traffic to Server 2. It was also being used to store files and run a couple other services.

Recently, I upgraded Server 2, and eliminated Server 1. Everything now looks like: -> ??? -> Server 2 (XXX.XXX.XXX.2)

I asked my hosting provider if they could update their DNS cluster to point to the same IP address as the second domain, but they require an additional fee to do so.

I'm very new to this, but I think my goal is to set up a custom nameserver on Server2, and update to point to the nameserver running on Server2. Can someone maybe point me towards a good tutorial/explanatory guide showing how to accomplish this? I've Google'd a bit, but I got a bit lost. I have a good amount of Unix knowledge/experience, but very limited networking knowledge.

share|improve this question
up vote 2 down vote accepted

Here is a very quick-and-dirty description of how DNS system works, and here is a bit longer explanation. Before you start tinkering with DNS try to grasp how the system works.

Depending on how your systems are set up you could just add Server 1's IP address (possibly as an alias) to Server 2's network card and be done. If it won't work for whatever reason (e.g. routing), you have at least 3 possible roads:

  1. Pay the fee and have the DNS records updated.
  2. Change the provider to one who doesn't charge you for such minor service.
  3. Set up your own DNS servers.

If you decide to go via route 3, you again have several options :). Just note, that DNS servers are a crucial piece of infrastructure -- if they fail then people will be unable to reach anything within your domain. Also note, that to have your own DNS server, you have to own a domain. This means, that if you want to have a server in you have to own the whole domain. If your host is, but someone else owns, then you have to have the same server.

There are several ways to get your DNS servers point where you need:

  1. Find some reliable company providing DNS services. They should have at least 2 DNS servers in 2 different networks (so that failure of a single router won't cut the world off from your DNS servers).
  2. Set up your own servers. If your servers fail, or there won't be usable route to them, then people wont be able to resolve names to addresses, but then the hosts with these addresses won't be accessible either. This affects everything from shell accounts to web pages to mail.
  3. Find another person in similar situation, set up your master DNS server on your host and have him host your secondary DNS server. Repay by hosting his secondary DNS server. This increases availability of your DNS service.
share|improve this answer

Nameservers are set within the network adapter itself. 2 computers on the network can have 2 different name servers. One could even use the other as a name server. To point a domain to an IP, you need to A) have bought a domain name and be able to set name servers within, if you are hosting the server on the domain name its pointing to; or B) use a custom DNS service like "" and set up A-records to point the domain to an IP. Email me "Support/@/" for free DNS service. I run a few DNS servers.

share|improve this answer
Nameservers are not set within network adapters. – Paweł Brodacki Aug 16 '11 at 6:49
If this is too late, sorry. But yes, in windows, the DNS service can be changed. Usually it defaults to the router company's servers. Read on the "Google DNS: and" Stuff. I can provide that service. – U4iK_HaZe Aug 25 '11 at 10:42

Your Answer


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.