If you are authoritative for a cname that points to an A elsewhere, your server will resolve the cname and leave it to the client dns server to go get the A from the server that hosts it. On Mar 16, 2012 10:14 AM, "Samantha Steers" <sam.fait...@gmail.com> wrote:
> Hi, > > I am getting prepped to migrate dns from one service to in-house servers. > While going through the zone file to ensure I got everything, I found that > we have CNAME in our domain pointing to a CNAME in another domain that is > pointing to the A record in the other domain: > > host record.ourdomain.com > record.ourdomain.com is an alias for record.client.otherdomain.com. > record.client.otherdomain.com is an alias for otherhost.otherdomain.com. > otherhost.otherdomain.com has address x.x.x.x > > To duplicate this exactly on our servers, it appears that I have to enable > recursion but the provider said that they are not doing that. I get the > feeling that I am not going to get the information from them on how they > are accomplishing this without recursion. > > Right now I have replaced the CNAME with an A record pointing to the IP > directly and am getting the proper results, but feel that this leaves me > having to watch for changes that the otherdomain.com administrator might > make. > > Am I missing something else that I can do to replicate? A separate > external view? > > Thanks. > > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users >
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
