I'm trying to help someone solve their dns issues and I'm wondering what effect this might have on things. The user already had glue records like dns1.domain.com = 192.168.0.10 dns2.domain.com = 192.168.0.11 They wanted to start to transition their services to a nother backbone provider so they also made glue records of dns3.domain.com = 10.0.0.30 dns4.domain.com = 10.0.0.31 They copied their domain.com zone file over to the new server and the relevant portions of it had things like domain.com. NS dns1.domain.com. domain.com. NS dns2.domain.com. dns1 A 10.0.0.30 dns2 A 10.0.0.31 dns3 A 10.0.0.32 dns4 A 10.0.0.33 Then they changed the nameservers at the registrar from dns1 & dns2.domain.com to dns3 & dns4.domain.com They waited for changes to propagate but kept having issue. i was digging around at various places and it looks like some servers are still going to 220.127.116.11 and .11 to resolve the domain instead of going to the new servers, some are going to the new servers of 10.0.0.30 and 31 to resolve names like they wanted. Its been like a week and a half so all changes should be propagated by now. Clearly it needs a major cleaning up. I'd like to understand more of why this seems to break things. To my understanding what they put in as an A record for the dns servers really is irrelevant since those are entered on the higher level servers as glue records and should be answered there first. So what actually is happening and what "needs" to match versus what should match to be RFChappy? Do the NS records of the domain have to match the name servers given to the registrar? Do the A records of the dns servers given to the registrar to be used as glue have to match the locally created A records for those servers?