hi, i've tried searching for answers, but most stuff returned is about redirecting/cnaming the root A record, which is not what i'm trying to do. basically, i'm trying to migrate all dns to new servers, with new hostnames. i've already copied over all the zone files. i have 2 old dns servers dns1.domain.com and dns2.domain.com, and 2 new dns servers ns1.domain.com and ns2.domain.com put simply, i have no problem changing all the nameservers for domains registered through us, but we also do dns for a lot of third party domains, and it's a nightmare getting them all to make changes. so rather than ask them all to change the dnsservers from dns1 and dns2 to ns1 and ns2, can we just change the A records for dns1 and dns2 to match the ip's of ns1 and ns2, (or change dns1/dns2domain.com to cname to ns1/ns2.domain.com)? i've done some testing and as far as i can tell, it would all work. but i want to make sure this is really all ok and there's nothing i'm overlooking. this is a live system with a lot of domains, so i can't afford to miss something. *note, just to be completely clear, this is not about changing the records in every zonefile, that's already done on the new servers. it's purely changing the A record target of dns1/2 in domain.com's zone to match the ip of ns1/2 (or cnaming dns1/2 to ns1/2) and leaving the dns servers configured with the registrars (nominet/opensrs etc) as dns1/dns2.domain.com just not sure if dns queries to dns1.domain.com actually going to ns1.domain.com will cause any unexpected issues, i don't think it will, but as i said, i can't risk being wrong. i know i'd have to get them to change it at the registrar eventually, but this would relieve the hassle and time constraints of trying to get everyone to change things at the same time or to continue maintaining two sets of nameservers because some bugger won't make the change.