[SOLVED] Is it safe to have Internal DNS Master have NS records point to DMZ Server?
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: RHEL 5.9 Server and Workstation, RHEL 6.4,Server and Workstation, OracleVM, HP/UX, Solaris
Posts: 9
Rep:
Is it safe to have Internal DNS Master have NS records point to DMZ Server?
I have three internal DNS servers, 1 master and 2 slaves, and three DMZ servers, 2 masters and 1 slave. The internal master currently has two NS records pointing to the 2 DMZ Masters. Is this a safe practice? Should I change them to point to the 2 internal slave servers? Is there a limit to the number of NS records?
Thank you for any feed back.
The DMZ server should really only host Internet facing zones - e.g. mycompany.com. The internal name servers should be authoritative for internal domains (e.g. mycompany.local) and possibly operate as caching servers for external lookups. However this is not the only way to architect things, bind supports 'views' which allow you to provide access to different information based on where the client request is coming from.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.