Basically when you try to browse a website like www.google.com the DNS entries tell the computer trying to access that website, what IP address to go to to bring the website up. Every website domain in existence has a IP address masked behind the domain and the IP address is actually what the browser is pulling information from.

Nameservers are effectively a control system for dns records, so if a customer points their DNS nameservers to our company, we can manage their DNS for them to make sure everything runs well.

Well this particular customer decided they wanted to manage their own dns entries, so they pulled the nameservers away from us and are now pissed at us because they have no idea what they just did and it broke the website.

They still want to control their own dns records, but they want us to guide them through the process and basically educate them on how to do what they are trying to do.

I'm not doing it, give back control of your DNS to us and let us fix it, or take the information I gave you and figure it out.

---
RIP: Canuklehead, Karma: 1369 // RIP: Gen_Lee_Enfield, Karma: 1731 //
RIP: Orlando of the Axe, Karma: 1642 // RIP nayr626 Karma: 4395 --They delivered!

So my company controls the DNS entries of hundreds of websites and the customer.

[none]

[none]

---