IP synthesizer: Make "internal" the TLD being used
DNS-to-IP script: Allow TLD to be changed.
coLunacyDNS: Clarify string/numeric for all processQuery() return values
coLunacyDNS: Another doc update
README.md: Remove redundant coDNS.log() from example
README.md: Minor grammar fix
coLunacyDNS: Update README.md
* coLunacyDNS is now version 1.0.010
* Clarify that example configs are public domain
* Add script to convert something like 10.1.2.3.ip4.invalid in to the
corresponding IP (10.1.2.3 in this case)
MARARC.parser: Remove obsolete note from 2007
Deadwood has had real dictionary variables since around early 2008.
coLunacyDNS: Update source code to 1.0.010 release
Next: Update the win32 binary
coLunacyDNS: Fix bug where we improperly use FD_ISSET w.r.t. select()
If you use FD_ISSET on a connection never set with FD_SET, this triggers
a buffer overflow in Ubuntu’s 20.04 glibc. Fixed.
Found when updating tests for https://github.com/samboy/MaraDNS/issues/91
This *also* means we will need to make a coLunacyDNS 1.0.010
coLunacyDNS: Remove Ubuntu 20.04 compile time warning
Deadwood SQA: Disable sqa_tcp_buffering
I am rather concerned that these tests, which work like a charm
in CentOS 8 + Podman, are failing in Ubuntu 20.04 + Docker. It
*probably* indicates a bug with the Linux kernel or the libc TCP
libraries, since these tests have been running just fine for over
I do not have the resources right now to deal with this bug.
DNS-over-TCP in Deadwood is only there for strict RFC compliance,
and I should probably disable DNS-over-TCP in Deadwood until
when and if I have time to deal with these corner case bugs.
Deadwood testing: Update two more tests for Ubuntu 20.04 LTS
Update another test to use only nobody user (Ubuntu 20.04 work)
update cache file test to run in Ubuntu 20.04
sqa_tcp_buffering_2 fails in ARM64 and/or Ubuntu 20.04
I will not bother investigating this. dns-over-tcp is deprecated.
lunacy: Remove compile-time warning; correct os_time comment
lunacy: Update manual for 2020-12-06 (limited os.time() restored)
Lunacy: Update for 2020-12-06
This does not affect coLunacyDNS, since the only change for 2020-12-06
is to add a limited version of os.time() (no arguments allowed; this
function simply returns the system time as a UNIX compatible timestamp
w/o Y2038 issues)
* Non-issue in UNIX and clones with 64-bit time_t (Lunacy uses 64-bit
floats for all numbers)
* Non-issue in 32-bit Windows build (we convert the 64-bit Windows
“FileTime” timestamps in to Lua’s 64-bit float format)
* Minimal issue in UNIX and clones with 32-bit time_t (negative times
are assumed to be between 2038 and 2106); even here, Lunacy will use
a 64-bit float.
coLunacyDNS: Update version number in README
README.md for coLunacyDNS: Add co1AA/co1RA/co1TTL example