␡
- Dynamic DNS
- Of Masters and Slaves
- Accepting and Doing Updates
- TSIG
- The Dynamic Zone
- The Client
- Update Prerequisites
- Update Actions
- Using nsupdate
- Slave Server Issues
- Reverse Zones
- A One Host Zone
- DHCP
- Mixing DNS and DHCP Implementations
- DHCP and Static DNS Entries
- DHCP and Dynamic DNS Entries
- Dynamic Updates by the Client
Reverse Zones
I have not mentioned reverse zones at all thus far into the chapter. Of course you will need reverse zones as well as forward zones, and they are maintained exactly the same way. In the case of classlessly delegated reverse zones, you should send update requests for the real record name, not the correct name. In the case of the classless emperor.penguin.bv network in Chapter 2, the update request would be for names such as 129.128-255.56.168.192.in-addr.arpa, not 129.56.168.192.in-addr.arpa.