DelphinusDNS Blog

(the latest about delphinusdnsd)

Previous Page

Development is stalled probably until mid-March

February 13th, 2022

For those that expect to see major code additions I have to disappoint you. Development is stalled on a project for my dad, which i hope to have done by mid-March. I also had to shuffle a lot of computers around at home in order to make electricity savings. That shuffle is pretty much done. I'm craving for doing additions to delphinusdnsd though and this spring when it commences will be great. A damper to that will be a new job but I haven't been accepted to any outstanding resumes, so my hopes aren't very high on that.


Politics: EU wants to abuse the DNS

January 20th, 2022

According to this article which has deeper hyperlinks linking to here, the EU is planning on providing DNS infrastructure for everyone. This is similar to efforts of government taking back the Internet from corporations. As you may recall telephone access fees became a lot more affordable when corporations built the Internet which surpassed the POTS (plain old telephone network). It was a fight between ITU and corporations that united in a great big network, the Internet. The corporations won, but government wants it back because they realised that communications is control over citizens. What they plan on doing is also building an extensive filtering system into their DNS system. This provides opportunity to be abused by government for censorship, for corruption. Delphinusdnsd isn't related to this project and I'm glad I don't have to lift a finger to help the government see this through. It's just disgusting though, and I wanted to make DNS enthusiasts aware of this. Yes it is political.


Logging has changed over the years, an explanation

January 1st, 2022

In 2019:

In 2022:

The sum is important to cross-reference CACHEHITS which is a small cache in Delphinusdnsd 1.6.0 to speed up answers.


Happy New Year 2022

January 1st, 2022

As I sit here in my parents living room, and drinking coffee, I wish you a: Happy New Year 2022. May you have a great year ahead of you!


Delphinusdnsd-1.6.0 released

December 20th, 2021

I have tagged the tree to 1.6.0. It was the first time doing it with git I think and it was uneventful and just worked. Please consult the CHANGES file to see what changed. It makes no sense to run anything below 1.6.0 unless you have custom hacks that need to be ported first. Enjoy and have a happy solstice, christmas and new year!

0 comments is back on my servers

November 28th, 2021

I have put back on my servers since Ricardo's server was down for a full week. I have still left him as a mirror site from this blog. I hope he's not too sad, I'm very happy he helped me out, but I guess the downed server was a message that I'd have to take my baby back.


The current APEX of

November 23rd, 2021

Here is the current APEX of the zone as queried with dig any (pod is one of the nameservers of I also ran this through a grep -v RRSIG since those are machine like signatures that serve no real human purpose.

;; Truncated, retrying in TCP mode.

; <<>> dig 9.10.8-P1 <<>> any
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48222
;; flags: qr aa rd; QUERY: 1, ANSWER: 26, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

; EDNS: version: 0, flags:; udp: 4096

;; ANSWER SECTION:	86400	IN	SOA \ 2021112101 3600 1200 1209600 86400	3600	IN	DNSKEY	256 3 13 \
QJRb5mSQZxmSd1N1QvAboRUh8vk4J1H25SKvtYlun8msxs/l9LXb9I97 QKZZ9oBWVfCiWKB6FCQqfFM45UjSEQ==	3600	IN	DNSKEY	257 3 13 \
Jr2jhZF/5IWshQKN+pINgjN4nHumie/TR+w7W3pvZRzUMgSBi8mc9K/1 GMl9l01r2vggrzYqaV0TVY680GXSDg==	86400	IN	LOC	50 4 3.600 N 10 15 4.600 E 350.00m 1m 0.00m 0.00m	86400	IN	RP	0	IN	NSEC3PARAM 1 0 10 -	86400	IN	NS	86400	IN	NS	86400	IN	MX	5	86400	IN	MX	10	86400	IN	MX	20	86400	IN	TXT	"v=spf1 ip4: ip4: \
ip6:2a01:4f8:c010:71dd::1 ip6:2a03:6000:6f68:631::170 ip6:2003:a:60f:ce01::108 ~all"	86400	IN	TXT	"the latest dns server is available at, \ is the softwares maintainer site hosted by Ricardo Santos"	86400	IN	A	86400	IN	AAAA	2a03:6000:6f68:631::170

;; Query time: 30 msec
;; SERVER: 2a01:4f8:c010:71dd::1#53(2a01:4f8:c010:71dd::1)
;; WHEN: Tue Nov 23 02:27:00 CET 2021
;; MSG SIZE  rcvd: 2028
I'm especially proud of the LOC addition just a few weeks ago. update: I line wrapped the output a little...


I'm reinstating this blog temporarily

November 21st, 2021

Pirata is away and the website isn't working so I feel that I should take control again and give people something to let you know that we're not gone. Sorry for disappearing a while ago. The official website is still on pirata's site which leads you to the GITHUB. There you can download and clone delphinusdnsd.

We're still on track for a delphinusdnsd 1.6.0 release in mid December 2021.

Your friendly DNS programmer, Peter.


My rough notes on the LOC RR

March 3rd, 2021

Before I start programming on another thing, I'd like to understand what I'm doing. So it happens to be that I've been studying RFC 1876. With a possibly slight learning disability this was hard to decipher, but I've finished with some notes. Here they are

       MSB                                           LSB
      0|        VERSION        |         SIZE          |
      2|       HORIZ PRE       |       VERT PRE        |
      4|                   LATITUDE                    |
      6|                   LATITUDE                    |
      8|                   LONGITUDE                   |
     10|                   LONGITUDE                   |
     12|                   ALTITUDE                    |
     14|                   ALTITUDE                    |

The LOC record has a VERSION which is always 0, a SIZE which is the size of
the location (described as entity in the RFC) as a sphere.  Here if you want
to indicate a place you can give it 0x12 (1e2 cm or 1 meter).  There is a
Vertical and Horizontal precision of data which is a circle of error instead
of a positive/negative value.  Here you can say 0x16 for horizontal and 
0x13 (1e3) for vertical precision.  0x16 would be 10km and 0x13 would be 10 

Then comes latitude and longitude expressed as a 32 bit integers.
Altitude is interesting.  As you stand on the oblate spheroid of earth your
altiude is 100,000 meters if you were standing on the water (sea level).  If 
you were below sea leavel say -2.30 meters you would be at an altitude of 
9,999,770 cm or 99,997.70 meters.  It is a value in centimeters represented in
the packet.

An example LOC RR reply:

09:40:28.182941 > [udp sum ok] 8633 1/0/1 LOC(83) (ttl 255, id 17634, len 111)                
  0000: 4500 006f 44e2 0000 ff11 933f c0a8 b102  E..oD......?....               
  0010: c0a8 b108 0035 4c7f 005b 7278 21b9 8180  .....5L..[rx!...               
  0020: 0001 0001 0000 0001 0b6e 6c6e 6574 6c61  .........nlnetla               
  0030: 6273 3031 0472 696e 6705 6e6c 6e6f 6703  bs01.ring.nlnog.               
  0040: 6e65 7400 001d 0001 c00c 001d 0001 0000  net.............               
  0050: 012f 0010 0012 1613 8b3c 05b1 8110 3903  ./.......<....9.               
  0060: 0098 959a 0000 2910 0000 0000 0000 00    ......)........

This is what it looks like in dig:

;    IN      LOC

;; ANSWER SECTION: 600 IN      LOC     52 21 22.993 N 4 57 20.387 E \
	-2.30m 1m 10000m 10m

The output here gives:

latitude, longitude, -2.30meter below sealevel (giving 98959A == 9999770 cm),
1 meter (1e2 = 0x12) entity, 10km (1e6 = 0x16) horizontal precision, and
10 meters (1e3 = 0x13) vertial precision.

So it may very well be that I'll start writing LOC support into delphinusdnsd in the future.


Delphinusdnsd 1.5.2 released

February 25th, 2021

This fixes the compiling on OpenBSD-current (which had enabled -fno-common by default in it compiler going forward). There is no other fix since the botched and little tested 1.5.1 release. OS's this was tested on were: OpenBSD-6.9-beta/arm64, OpenBSD-6.8/amd64, FreeBSD/amd64, NetBSD/amd64 and Linux on amd64. Enjoy!


Next Page


RSS Feed

Click here for RSS

On this day in

Other links

Have feedback?

By clicking on the header of an article you will be served a cookie. If you do not agree to this do not click on the header. Thanks!

Using a text-based webbrowser?

... such as lynx? Welcome back it's working again for the time being.

Older Blog Entries

Powered by BCHS