Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Windows Server 2019, Third Edition

You're reading from   Mastering Windows Server 2019, Third Edition The complete guide for system administrators to install, manage, and deploy new capabilities with Windows Server 2019

Arrow left icon
Product type Paperback
Published in Jul 2021
Publisher Packt
ISBN-13 9781801078313
Length 690 pages
Edition 3rd Edition
Languages
Concepts
Arrow right icon
Author (1):
Arrow left icon
Jordan Krause Jordan Krause
Author Profile Icon Jordan Krause
Jordan Krause
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Getting Started with Windows Server 2019 2. Installing and Managing Windows Server 2019 FREE CHAPTER 3. Active Directory 4. DNS and DHCP 5. Group Policy 6. Certificates in Windows Server 2019 7. Networking with Windows Server 2019 8. Remote Access 9. Hardening and Security 10. Server Core 11. PowerShell 12. Redundancy in Windows Server 2019 13. Containers and Nano Server 14. Hyper-V 15. Troubleshooting Windows Server 2019 16. Other Books You May Enjoy
17. Index
Appendix: Answers to the end-of-chapter Questions

Split-brain DNS

In all of our lab configurations, screenshots, and examples you will notice that domains we create on the internal network always end with .local. This is purposeful and is best practice. Public DNS zones, as you well know, can end in a myriad of ways. Websites or services that live on the internet may end with .com, .org, .edu, .biz, .info, .tech, .construction—the list goes on and on. These are known as top-level domains, and the creative use of such DNS suffixes should remain on the internet and away from our internal DNS zones.

Now, many of you may already work in corporate environments where your internal DNS is configured as something other than a .local, and so you already realize that internal domains can certainly be configured as one of these other suffixes. For example, Microsoft.com is obviously one of the public domains that Microsoft owns, and they could very well also have used Microsoft.com as an internal DNS zone too. In fact, it could even...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime