Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
zeroconf_design [2009/02/25 13:33] crackerjackmack |
zeroconf_design [2009/11/12 15:18] (current) crackerjackmack |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| ===== Link Local Addressing ===== | ===== Link Local Addressing ===== | ||
| + | Maybe a good failsafe behavior? IPv6 based booting will be based on this as well. This would just the IPv4 equivalent. | ||
| ===== Multicast DNS ===== | ===== Multicast DNS ===== | ||
| + | Proposed PXE definition | ||
| + | |||
| + | pxe PXE Configuration | ||
| + | Kevin Landreth <crackerjackmack at gmail.com> | ||
| + | Protocol description: None | ||
| + | Primary Transport Protocol: None | ||
| + | Defined TXT keys: Mixed | ||
| + | |||
| + | |||
| + | Still need to work out keys. Basic premise is to store DHCP PXE client options in DNS | ||
| ===== DNS service discovery ===== | ===== DNS service discovery ===== | ||
| Line 15: | Line 26: | ||
| ====== Use cases ====== | ====== Use cases ====== | ||
| Put any use cases here | Put any use cases here | ||
| + | |||
| + | ===== Extending DNS support ===== | ||
| + | In general, it might be handy to utilize mDNS in a few cases. In some environments, DNS servers either aren't available or unnecessary. If it is an isolated network, then DNS servers aren't always reachable or don't have resource records for the boot servers (which could vary per location). On local, test, development, or lab environments it isn't always ideal or worth the trouble to setup a DNS server and/or integrate it with DHCP. Honestly, what is the need for a registered domain for an 8 node lab? | ||
| + | |||
| + | Utilizing multicast DNS should be a compile time option for **.local** suffixed requests. The default behavior can be debated later =) | ||
| ===== Ad hoc deployment network ===== | ===== Ad hoc deployment network ===== | ||
