[cisco-voip] OT: DNS for data centers
Lelio Fulgenzi
lelio at uoguelph.ca
Fri Nov 8 16:21:45 EST 2019
Here a question for those with DNS experience....
We have a requirement for our DC hosts to access some services/hosts using different IP addresses as the rest of campus. Sounds familiar right? We're investigating the best way to do this.
Are we looking at enabling split view DNS on our campus DNS servers? Or introducing a new set of data center DNS servers?
Here's the catch.... The DC servers need to access all the rest of the hosts at the same address of the rest of campus.
What we don't want to do is replicate our DNS zones in their entirety and then have to update each of them with each new DNS record request that comes in.
The question a few of us had is this.
Can a DNS server which is authoritative for a zone forward requests for that zone if they don't resolve internally?
The picture would be this.
Our campus DNS servers would remain. Two new DC DNS servers would be created with a handful (ok, more than a handful) of entries. The servers in the DC would point to the DC DNS server to get their information and the DC DNS server would forward the rest that it can not resolve to our campus DNS servers.
The campus DNS servers would _never_ refer requests to the DC servers.
Thoughts? (about this request)
---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook
[University of Guelph Cornerstone with Improve Life tagline]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 16795 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191108/a357d533/attachment.bin>
More information about the cisco-voip
mailing list