Differences
This shows you the differences between two versions of the page.
|
dnsresolver [2006/06/14 06:23] stockholm created |
dnsresolver [2006/06/14 06:23] (current) stockholm created |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== DNS resolver ====== | ||
| + | The DNS resolver code (optionally to be compiled into Etherboot) allows for filenames to contain hostnames. Thus, | ||
| + | |||
| + | <file> | ||
| + | http://www.memtest86.com/memtest.nbi | ||
| + | </file> | ||
| + | |||
| + | might in theory be a valid file to be downloaded (you will have to compile-in HTTP support as well). | ||
| + | |||
| + | DNS resolver code will only work if a nameserver has been configured inside your DHCP config. Most regular hostnames are expected to work: A (adress) and CNAME (alias) records are allowed for a certain depth. There is no support for IPv6 hostname resolution yet, but that will not do any harm as Etherboot does not yet support IPv6 anyway. | ||
| + | |||
| + | Hostnames may only be used in fully specified URIs of the form | ||
| + | <file> | ||
| + | protocol://hostname:port/path/filename | ||
| + | </file> | ||
| + | |||
| + | The '':port'' part may be omitted. | ||
| + | |||
| + | Currently allowed ''protocols'' include "http", "tftp", "nfs", and "[[multicast#Using atftpd|x-tftp]]". | ||
| + | |||
| + | [[multicast#Using mini-slamd|SLAM]] might or might not work with DNS... FIXME. | ||
