dyndns

Check-in [7e03c409e1]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix up the markdown
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | master | trunk
Files: files | file ages | folders
SHA3-256:7e03c409e1f2469887d2db26a83fffa6c282b746e1896539842e9d239c993ec3
User & Date: ajv-899-334-8894@vsta.org 2017-06-15 04:56:59
Context
2017-06-15
04:57
Argh, more fixups check-in: bddab1c531 user: ajv-899-334-8894@vsta.org tags: master, trunk
04:56
Fix up the markdown check-in: 7e03c409e1 user: ajv-899-334-8894@vsta.org tags: master, trunk
04:52
Merge branch 'master' of https://github.com/vandys/dyndns check-in: bdad547ae1 user: ajv-899-334-8894@vsta.org tags: master, trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to README.md.

16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
..
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

The other server port is a simple DNS server.  It is intended to be used
as a sub-zone of your main domain, and answers A requests with the
current IP address of any registered host.  In your main zone you want
to define both this server (it requires its own IP address; NS
records do not specify a port, alas) and its domain.

$ORIGIN example.com.
(...)
dyn	IN	NS	ns1.dyn.example.com.
ns1.dyn	IN	A	a.b.c.d

(By convention, our dynamic DNS server is "ns1" under its own
dynamic part of the domain.)

Now this server at a.b.c.d receives DNS questions about hosts under
dyn.example.com ("joe.dyn.example.com", "home.dyn.example.com", etc.).

................................................................................
Hosts are managed by a simple file mapping host name to pre-shared key.
Nonces are used, but are not saved on disk; the security here is intended
to be enough to deflect casual vandalism, not to hold off a nation-state.
Similarly, host state is not saved to disk; if the host is not sending an
update, presumably it's offline, so why bother giving its old IP address?

The hosts supported are tabulated in etc/hosts, with a format:
<host> <pass>

Continuing example.com above, the line:
joe xyz

would let the client update joe.dyn.example.com if it knows the
pre-shared key "xyz".








|
|
|
|







 







|


|




16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
..
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

The other server port is a simple DNS server.  It is intended to be used
as a sub-zone of your main domain, and answers A requests with the
current IP address of any registered host.  In your main zone you want
to define both this server (it requires its own IP address; NS
records do not specify a port, alas) and its domain.

    $ORIGIN example.com.
    (...)
    dyn	IN	NS	ns1.dyn.example.com.
    ns1.dyn	IN	A	a.b.c.d

(By convention, our dynamic DNS server is "ns1" under its own
dynamic part of the domain.)

Now this server at a.b.c.d receives DNS questions about hosts under
dyn.example.com ("joe.dyn.example.com", "home.dyn.example.com", etc.).

................................................................................
Hosts are managed by a simple file mapping host name to pre-shared key.
Nonces are used, but are not saved on disk; the security here is intended
to be enough to deflect casual vandalism, not to hold off a nation-state.
Similarly, host state is not saved to disk; if the host is not sending an
update, presumably it's offline, so why bother giving its old IP address?

The hosts supported are tabulated in etc/hosts, with a format:
    <host> <pass>

Continuing example.com above, the line:
    joe xyz

would let the client update joe.dyn.example.com if it knows the
pre-shared key "xyz".