As mentioned in the title I have instructed my client to update their DNS A records to point to my new server IP 3 days ago. The domain registrar is Heart Internet and the client has provided me with an actual screenshot of the page showing that the (*, @, www) A records have indeed been pointed to my new server but I am seeing no change in any DNS records using various tools such as whatsmydns.
The old and new servers are both running Ubuntu 12. The old server is running using Nginx while the new one is running using Apache2.
I am clueless as to why this is happening because using another registrar I have successfully updated DNS records for other clients which all point to the new server correctly.
If I am not able to solve the problem using advice I will provide the IP/domain name here.
Best Answer
It's not uncommon for the name servers to exist somewhere other than the Registrar. Many web hosting companies tell customers to move their name servers to the web hosting company (some may even require it although there's no technical requirement for a web host to also host the DNS). Many "individual" web hosters also tell their customers to move their name servers (foolishly, because web hosters aren't typically good at hosting DNS and probably shouldn't do so).
The key is to update the A record at the DNS host that is authoritative for the domain. Right now, that appears to be
ns59.1and1.co.ukandns60.1and1.co.uk. So your client should have a login for 1and1 so that they can edit the A record there. If they don't then they'll need to contact 1and1 to get a login. I'm assuming that 1and1 hosted their web site at one point. Your client could also move their name servers back to the Registrar. They'll need a login at the Registrar to do that.EDIT
This is a topic that I find confuses a lot of people so I'd like to clarify a few things:
When a domain name is registered there are typically four major components/entities involved:
1. The Registrar - This is where the domain is registered. The Registrar has ultimate authority of the domain name (registration, renewal, suspension).
2. DNS Host - This is where the name servers and DNS zone and records exist. What name servers are authoritative for the domain name?
3. Web Site - Where does the web site exist?
4. Email - Where does email for the domain go?
In today's market where providers want to "be all things to all people" it's not uncommon to have a single entity handle all four of these components, but there's no technical requirement to do so.
For example: I have several domain names registered via Network Solutions. Network solutions is the registrar and if I so choose they can also host my DNS namespace (the DNS zone for my domain name - this is where the authoritative name servers are), they could also host my web site and my email if I so choose. But that's not a requirement. I happen to have my DNS zone (again, the authoritative name servers) hosted at DynDNS. I host my web sites and my email myself. So you see that in my case there are three different entities involved:
1.Network Solutions, who is the Registrar.2.DynDNS, who hosts the DNS zone for my domain.3.Me, who hosts my web sites and my email.The point of all of this being: the name servers can be hosted by anyone who provides that service. It does not have to be the Registrar. It can be, and often is, the entity that hosts the web site. In your case it looks like 1and1 hosted the web site at some point and probably had the customer move their name servers to 1and1.