Hosting Your Own DNS
Mac OS X Servers also do not like their names to change. So much so that there is a hostname configuration wizard (described further in Chapter 2). DNS can be a holistic topic. This is because there are two views, arguably the public and private view. These are known as BIND views and each hostname can have different IP addresses associated to it based on which subnet that a request is made from.
In this section, we are only going to look at DNS on a local network, assuming that public-facing DNS is hosted on a public DNS server, such as those made readily available from Network Solutions and ZoneEdit. Because we are constraining our view of DNS (no pun intended) to the local network, it is worth starting off with the domain name you will be using. In this example, we will be using krypted.com. However, we could just as easily be using krypted.lan or krypted.home. In those cases, there would be no DNS available when you are outside the local network, unless using DNS over a VPN connection.
Because we are using krypted.com, we should also create records for any public services that are offered, mimicking the settings from the host for them (unless they are also hosted internally). For example, www.krypted.com is not located inside the network. Therefore, if we are using krypted.com, then we will need to define a www record externally in order to resolve that name internally (resolution is the response for a DNS record from the authoritative source). The server ...