On Apr 14, 2017, at 2:40 PM, McDonald, Daniel (Dan) <dan.mcdon...@austinenergy.com> wrote: > > Setting up global server load balancing seems easy enough – just add ns > records pointing at the load balancer and away you go: > > example.com. 38400 IN SOA ns20.example.net. > dan\.mcdonald.example.com. 2017011107 10800 3600 604800 3600 > example.com. 38400 IN NS ns1.example.com. > example.com. 38400 IN NS ns2.example.com. > test.example.com. 900 IN NS > gslb1.example.com. > test.example.com. 900 IN NS > gslb2.example.com. > > That works fine for test.example.com. But when I go to production, I need to > do it for example.com and www.example.com. How do I delegate just the A > record and not the SOA, TXT, MX, SPF, and NS records, nor any of the other > entries in the zone. As I recall, I can’t just delegate , as an example, > www.example.com, then use a CNAME for example.com.
You can't do this for example.com. Obviously, www.example.com is not a problem. Your GSLB device should have a work-around for the zone apex (example.com itself), such as a simple webserver (right on each GSLB, perhaps) that takes those web requests and redirects them to www.example.com. Then in your main zone (not on the GSLB), you would have a record set pointing that zone apex to each of those web servers. Regards, Chris Buxton _______________________________________________ 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
