From 62b880018cea02a258c8af0e8f5977db095e5aff Mon Sep 17 00:00:00 2001 From: Ubuntu Date: Wed, 11 Apr 2018 15:36:12 +0000 Subject: [PATCH] fix up markdown --- tdns/README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/tdns/README.md b/tdns/README.md index 36a47db..0ec6fb5 100644 --- a/tdns/README.md +++ b/tdns/README.md @@ -67,7 +67,7 @@ When storing data for the org zone, it may look like this: ************************************************************************************************* * * * .---. * -* 1 +---------+ . +--------+ * +* 1 +---------+ +--------+ * * / '-+-' \ * * / | \ * * .-+-. .-+-. .-+-. * @@ -107,11 +107,10 @@ downward again, starting at the apex with `ns1.ord.ietf` and going to the `ietf`, `ord` and finally `ns1` labels. There we find attached the IP(v6) addresses. - +TBC.. - This -is implemented in `dns-storage.cc` and `dns-storage.hh`. + This is implemented in `dns-storage.cc` and `dns-storage.hh`. This lookup mechanism will tell you if a name is fully present in a zone, or if it was matched by an NS record. It will also perform wildcard matching, @@ -121,3 +120,5 @@ but not CNAME chasing. The code does not do any form of DNS escaping. Instead, DNS names are stored and manipulated as a sequence of DNS labels. So instead of messing with "www.powerdns.org", we use {"www", "powerdns", "org"}. + + \ No newline at end of file