-2

I have a server hosted by linode. I just finished a job for a customer and want to move his site to his server.

The current DNS records are pointing to my Linode server, but his site is now hosted elsewhere.

If instead of him changing his DNS entries and setting up his own domain, if I forward the site from my Linode server to his IP, will this be using my bandwidth (or other) resources?

Is this recommendable or is it better that he actually changes the DNS records to his new server?

Mark Henderson
  • 68,823
  • 31
  • 180
  • 259
Mauro Morales
  • 121
  • 3
  • Why do you not want to forward the DNS entries? – Ben Lessani Sep 30 '12 at 18:12
  • The customer thinks is too complicated to be done by them and they don't want to give me access to the domain at godaddy ... plus they know this can be done but I don't want to say yes if it is going to use any of my resources or if it's something stupid to do :P – Mauro Morales Sep 30 '12 at 18:14
  • Well, if they're happy to pay for your bandwidth and have a slower, more unreliable site - then keep at it. – Ben Lessani Sep 30 '12 at 19:07
  • so it does take some of my bandwidth? (sorry I have really no idea how this works) – Mauro Morales Sep 30 '12 at 19:44
  • This is not DNS forwarding, but something else; what it is exactly depends on how you do it. DNS forwarding is when one resolver forwards a DNS query to another resolver instead of recursively finding the answer itself. – Falcon Momot Oct 07 '12 at 22:42

2 Answers2

4

Yes, it will require network bandwidth and CPU time on your server for it to receive and forward the DNS queries. Very likely it will be a modest amount, but it will require some.

I would be more concerned that you will also become an additional point of failure in the design -- if your forwarders stop working, the client's DNS stops working. Why would you want that additional responsibility? (And why would they want that, too?)

Michael McNally
  • 1,500
  • 9
  • 14
2

Unless you have a good reason for needlessly forwarding traffic - you'll just be adding a bottleneck.

Point the DNS to where the site is supposed to be.

Ben Lessani
  • 5,244
  • 17
  • 37
  • Got it, thanks for the quick answer ... yes I also didn't think it was the best of the ideas but I want to have a good reason to tell them to just change their domain servers – Mauro Morales Sep 30 '12 at 18:15