DNS Gurus - please advise
We are in process of transferring a customers domain name away from our servers to the servers of a large ISP. We'll use custdomain.com ourdns.com and largeisp.com for this example to protect the innocent.
Custdomain.com is currently listed in network solutions with name servers ourdns1.com and ourdns2.com. We use an alabanza cp therefore we do not access the SOA records ourselves.
We intend to update the network solutions database with the DNS records of dnslargeisp1.com dnslargeisp2.com and dnslargeisp3.com so their technical geeks can control the entire web hosting solution.
Our concern is for extended customer downtime.
We made the following recommendation to the largeisp.com technical team, HOWEVER the state our recommendation is impossible to accomplish without us first transferring the custdomain.com name in the ns database.
We requested they modify the SOA records on their DNS server to reflect the transfer of domain, and once completed we will initiate the transfer with network solutions. Our thought is that the old DNS information will still resolve until it times out (48-72 hours, then the new authoritative name servers dnslargeisp.com
will be queried and resolve the custdomain.com URL properly.
Have we mad an incorrect assertion that largeisp.com can change their public name servers SOA records prior to the network solutions isp update? Our thought is the only issue is lame delegation which will not impact the custdomain.com URL since dnslargeisp.com will not be queried until the network solutions database is updated. In other words do their name servers have to pull the information from network solutions? Or is network solutions only role to point to dnslargeisp.com for information?
Please help out here, as the technical intricacies are left to others in my organization, and the largeisp.com's technical team has me second guessing our "quasi-technical" resource.
