Alpine Linux - User contributions [en]

TinyDNS Format

2012-07-10T18:42:56Z

Wmjohnso: Added AAAA Records

= TinyDNS data file =

The offical data format for tinydns data is documented in http://cr.yp.to/djbdns/tinydns-data.html See notes at bottom for more information on certain fields.

== SOA Record ==

`Zfqdn:nameserver:contactinfo:serial:retry:expire:min:ttl:timestamp:lo`

'''Zmy.example.net:208.210.221.65:abuse.example.net'''
Question: Zmy.example.net.
my.example.net. +2560 soa 208.210.221.65. abuse@example.net. 1206390017 16384 2048 1048576 2560

'''Zmy.example.net:208.210.221.65:abuse.example.net:2008032201:1000:2000:3000:4000'''
my.example.net. +2560 soa 208.210.221.65. abuse@example.net. 2008032201 1000 2000 3000 4000

== A, NS record combined ==

`&fqdn:ip:x:ttl:timestamp:lo`

Creates an ''A'' and ''NS'' record. Typically used to delegate a subdomain; can be used in combination with '''Z''' to accomplish the same thing as the combo above, but with a different email address.

'''&my.example.net:208.210.221.65:something:'''
# Question: Zmy.example.net.
# NS replies:
my.example.net. +259200 ns something.ns.my.example.net.
# AR replies:
#something.ns.my.example.net. +259200 a 208.210.221.65

'''&my.example.net:208.210.221.65:ns1.somewhere.com:3600'''
# Question: Zmy.example.net.
# NS replies:
my.example.net. +3600 ns ns1.somewhere.com.
# AR replies:
#ns1.somewhere.com. +3600 a 208.210.221.65

== A and PTR record ==

`=fqdn:ip:ttl:timestamp:lo`

'''=alpha.my.example.net:192.168.1.1'''
Question: Zalpha.my.example.net.
alpha.my.example.net. +86400 a 192.168.1.1

# Question: Z1.1.168.192.in-addr.arpa.
1.1.168.192.in-addr.arpa. +86400 ptr alpha.my.example.net

For the PTR record to be returned, you must have the corresponding SOA record defined:
Zmy.example.net:ns1.my.example.net:abuse.example.net
&my.example.net:208.210.221.65:ns1.my.example.net

Z168.192.in-addr.arpa:ns1.my.example.net:abuse.example.net
&168.192.in-addr.arpa:208.210.221.65:ns1.my.example.net

== A record ==

`+fqdn:ip:ttl:timestamp:lo`

'''+alpha.my.example.net:192.168.1.1'''
Question: Zalpha.my.example.net.
alpha.my.example.net. +86400 a 192.168.1.1

== MX Record ==

`@fqdn:ip:x:dist:ttl:timestamp:lo`

'''@my.example.net:208.210.221.77:something'''
Question: @my.example.net.
my.example.net. +86400 mx 0 something.mx.my.example.net.

'''@my.example.net:208.210.221.77:mx1.my.example.net:10'''<br>
'''@my.example.net:208.210.221.78:mx2.my.example.net:20'''
Question: @my.example.net.
my.example.net. +86400 mx 10 mx1.my.example.net.
my.example.net. +86400 mx 20 mx2.my.example.net.
# AR replies:
#mx1.my.example.net. +86400 a 208.210.221.77
#mx2.my.example.net. +86400 a 208.210.221.78

== CNAME ==

`Cfqdn:x:ttl:timestamp:lo`

'''Cmailserver.my.example.net:yourmailserver.somewhere.com'''
Question: Zmailserver.my.example.net.
mailserver.my.example.net. +86400 cname yourmailserver.somewhere.com.

== TXT ==
`'fqdn:s:ttl:timestamp:lo`

''''my.example.net:Please do not bug us we know our DNS is broken'''
Question: Tmy.example.net
my.example.net. +86400 txt 'Please do not bug us we know our DNS is broken'

== SRV ==
<code>Sfqdn:ip:x:port:priority:weight:ttl:timestamp</code>

Standard rules for ip, x, ttl, and timestamp apply. Port, priority, and weight
all range from 0-65535. Priority and weight are optional; they default to zero
if not provided.

'''Sconsole.zoinks.example.com:1.2.3.4:rack102-con1:2001:7:69:300:'''
query: 33 console.zoinks.example.com
answer: console.zoinks.example.com 300 SRV 7 69 2001 rack102-con1.example.com

== NAPTR ==
`Nfqdn:order:pref:flags:service:regexp:replacement:ttl:timestamp`

The same standard rules for ttl and timestamp apply. Order and preference
(optional) range from 0-65535, and they default to zero if not provided. Flags,
service and replacement are character-strings. The replacement is a fqdn that
defaults to '.' if not provided.

'''Nsomedomain.org:100:90:s:SIP+D2U::_sip._udp.somedomain.org'''
query: 35 somedomain.org
answer: somedomain.org 78320 NAPTR 100 90 "s" "SIP+D2U" "" _sip._tcp.somedomain.org

'''Ncid.urn.arpa:100:10:::!^urn\058cid\058.+@([^\.]+\.)(.*)$!\2!i:'''

== AAAA ==
`:fqdn:28:location:ttl`

These records are used to resolve IPv6 addresses.

''':alpha.my.example.net:28:\050\001\103\000\302\072\000\077\105\052\064\355\256\064\063\124:86400'''
query: alpha.my.example.net IN ANY
answer: alpha.my.example.net. 86400 IN AAAA 2801:4300:c23a:3f:452a:34ed:ae34:3354

== Notes ==

Each line starts with a character, and continues with colon separated fields. Spaces and tabs at the end of a line are ignored. Blank lines are also ignored.

'''timestamp''' is an optional TAI64 (hex format) timestamp. If the timestamp is given the ttl has special meaning:
* If ttl is nonzero or omitted, then the timestamp is when this record goes "live"
* if ttl is zero, then the timestamp is the "time to die", when the record is no longer to be served. Tinydns will dynamically adjust the ttl so that the DNS records are not cached beyond the "time to die"

'''lo''' is an optional location field. The record is ignored if the client is outside that location. lo can be one or two characters. For example,

%in:192.168
%ex
+www.mydomain.com:192.168.1.1:::in
+www.mydomain.com:200.20.32.1:::ex
specifies www.mydomain.com has address 192.168.1.1 for clients in the 192.168.0.0/16 address range, and 200.20.32.1 for all other clients.

In lines with "x", if "x" contains a dot, then "x" is used as the server name rather than "x".[something].fqdn You should omit ip if x has IP addresses assigned elsewhere in the data file.

'''Wildcards''' in the form of *.fqdn are allowed, and will resolve any address EXCEPT those that have their own records, or more specific wildcards.

+www.mydomain.com:200.3.1.1
+*.mydomain.com:127.0.0.1

Will send the user to his local machine for foo.mydomain.com, mx.mydomain.com, in fact ANYTHING .mydomain.com, except www.mydomain.com

[[Category:Networking]]

User:Wmjohnso

2012-04-20T15:36:43Z

Wmjohnso: Created page with "== Made you look. :) =="

== Made you look. :) ==

Sircbot

2012-04-20T15:31:32Z

Wmjohnso: fixed the numbered list in the Troubleshooting Section

Sircbot is a simple irc bot based in lua script.

== Install sircbot ==

{{Cmd|apk add sircbot lua-sircbot}}

== Configue sircbot ==

{{Cmd| vi /etc/conf.d/sircbot}}

Change name, server and channel

sircbot_opts="-n name -s server"
sircbot_channels="#channel"

== Create sircbot scripts folders and files ==

Sircbot will use an folder for the channel where is logged in. Lets say we will use it at the "test" channel.
The folder path is: /etc/sircbot.d/#channel

== Example ==

Lets see an example:

Our bot will be named kumquat and we will join at the #test channel in the irc.ddd.ddd server.

{{Cmd| vi /etc/conf.d/sircbot}}

Change name, server and channel

sircbot_opts="-n kumquat -s irc.ddd.ddd"
sircbot_channels="#test"

Create folder bot.

{{Cmd| mkdir /etc/sircbot.d/#test -p}}

Create the lua scrip file for our bot.

{{Cmd| vi /etc/sircbot.d/#test/commands}}

#!/usr/bin/lua

-- Scripts for kumquat in Lua

args={...}

sender=args[1] -- is the nickname of running the command on IRC
message=args[2] -- is the message or command typed
channel=args[3] -- is the channel name

os.execute("sleep " .. tonumber(1))

-- This command will show: What can i do for you "nickname"?
local kumquatresult = string.find(message, "kumquat")
if kumquatresult ~= nil then
command="echo 'What can i do for you '"..sender.."'?' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show: Hello there, amigo "nickname"
local kumquatresult = string.find(message, "hi")
if kumquatresult ~= nil then
command="echo 'Hello there, amigo '"..sender.."'' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show the current UTC date and time
local kumquatresult = string.find(message, "date")
if kumquatresult ~= nil then
command="date -u | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a search for a alpine linux package
local kumquatresult = string.find(message, "apk search:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 12))
command="apk search"..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will resolve a host name and ip
local kumquatresult = string.find(message, "host:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="host "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a 3 times ping to a server or ip address
local kumquatresult = string.find(message, "ping:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="ping -c 3 "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

Make the script to be executable

{{Cmd| chmod +x /etc/sircbot.d/#test/commands}}

== Giving life to the bot ==

Starting bot service and adding to boot.

{{Cmd|/etc/init.d/sircbot start && rc-update add sircbot default}}

== Troubleshooting ==

If your bot is not responding as expected, an easy way to troubleshoot is to manually execute the script in /etc/sircbot.d/<#channelname>/<scriptname> with the three agruments.

{{Cmd|/etc/sircbot.d/<#channelname>/<scriptname> username hi '<#channelname>'}}

If your bot responds as expected, then you know that your script works. The problem is that sircbot is not executing the script. Here are two likely causes:

# Sircbot is case-sensetive when looking for the channel directory for a script to execute. For example, if you have a channel named "#Alpine", sircbot will look for /etc/sircbot.d/#Alpine/*. If that pathway isn't exactly right, then sircbot will skip that folder. In our example, if you have /etc/sircbot.d/#alpine/script, sircbot will not execute anything in that folder. To fix, simply rename the folder to /etc/sircbot.d/#Alpine/
# Sircbot doesn't execute scripts that have a '.' in the name. For example a script named 'listen.lua' will not be executed. Simply rename the script to 'listen'.

Sircbot

2012-04-20T11:06:56Z

Wmjohnso: Added the Troubleshooting section. - wmjohnso

Sircbot is a simple irc bot based in lua script.

== Install sircbot ==

{{Cmd|apk add sircbot lua-sircbot}}

== Configue sircbot ==

{{Cmd| vi /etc/conf.d/sircbot}}

Change name, server and channel

sircbot_opts="-n name -s server"
sircbot_channels="#channel"

== Create sircbot scripts folders and files ==

Sircbot will use an folder for the channel where is logged in. Lets say we will use it at the "test" channel.
The folder path is: /etc/sircbot.d/#channel

== Example ==

Lets see an example:

Our bot will be named kumquat and we will join at the #test channel in the irc.ddd.ddd server.

{{Cmd| vi /etc/conf.d/sircbot}}

Change name, server and channel

sircbot_opts="-n kumquat -s irc.ddd.ddd"
sircbot_channels="#test"

Create folder bot.

{{Cmd| mkdir /etc/sircbot.d/#test -p}}

Create the lua scrip file for our bot.

{{Cmd| vi /etc/sircbot.d/#test/commands}}

#!/usr/bin/lua

-- Scripts for kumquat in Lua

args={...}

sender=args[1] -- is the nickname of running the command on IRC
message=args[2] -- is the message or command typed
channel=args[3] -- is the channel name

os.execute("sleep " .. tonumber(1))

-- This command will show: What can i do for you "nickname"?
local kumquatresult = string.find(message, "kumquat")
if kumquatresult ~= nil then
command="echo 'What can i do for you '"..sender.."'?' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show: Hello there, amigo "nickname"
local kumquatresult = string.find(message, "hi")
if kumquatresult ~= nil then
command="echo 'Hello there, amigo '"..sender.."'' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show the current UTC date and time
local kumquatresult = string.find(message, "date")
if kumquatresult ~= nil then
command="date -u | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a search for a alpine linux package
local kumquatresult = string.find(message, "apk search:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 12))
command="apk search"..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will resolve a host name and ip
local kumquatresult = string.find(message, "host:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="host "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a 3 times ping to a server or ip address
local kumquatresult = string.find(message, "ping:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="ping -c 3 "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

Make the script to be executable

{{Cmd| chmod +x /etc/sircbot.d/#test/commands}}

== Giving life to the bot ==

Starting bot service and adding to boot.

{{Cmd|/etc/init.d/sircbot start && rc-update add sircbot default}}

== Troubleshooting ==

If your bot is not responding as expected, an easy way to troubleshoot is to manually execute the script in /etc/sircbot.d/<#channelname>/<scriptname> with the three agruments.

{{Cmd|/etc/sircbot.d/<#channelname>/<scriptname> username hi '<#channelname>'}}

If your bot responds as expected, then you know that your script works. The problem is that sircbot is not executing the script. Here are two likely causes:

# Sircbot is case-sensetive when looking for the channel directory for a script to execute. For example, if you have a channel named "#Alpine", sircbot will look for /etc/sircbot.d/#Alpine/*. If that pathway isn't exactly right, then sircbot will skip that folder. In our example, if you have /etc/sircbot.d/#alpine/script, sircbot will not execute anything in that folder. To fix, simply rename the folder to /etc/sircbot.d/#Alpine/

## Sircbot doesn't execute scripts that have a '.' in the name. For example a script named 'listen.lua' will not be executed. Simply rename the script to 'listen'.