BIND2CSV2(1) MaraDNS reference BIND2CSV2(1)NAME
bind2csv2 - convert zone files from BIND to MaraDNS compatible format
DESCRPTION
MaraDNS 1.3 has BIND zone file support. This means it is possible to use BIND zone files in MaraDNS. This makes it easier for people to use
MaraDNS in mixed DNS server environments.
Instead of having direct BIND zone file support, MaraDNS has a script, called bind2csv2, that converts BIND zone files in to the "csv2"
zone file format that MaraDNS 1.2 and 1.3 use. The zone files generated by bind2csv2 are not MaraDNS 1.2 compatible; MaraDNS 1.3 is needed
to read zone files generated by bind2csv2.
bind2csv2 is a Python script, written in version 2.2.3 of the Python interpreter. The script should be compatible with more recent versions
of Python. The script assumes Python is the file /usr/bin/python on your system; if Python is located elsewhere on your system, please
change the first line of bind2csv2. Naturally, you will need the Python interpreter installed on your system to use bind2csv2. This is a
well-known open source language supported by most modern Linux and BSD distributions.
USAGE
To use the script, enter a directory containing BIND zone files, and invoke the script thusly:
bind2csv2 -c zone1 zone2 zone3
Substitute "zone1", "zone2", and "zone3" with a list of one or more BIND zone files you wish be converted in to MaraDNS 1.3 csv2 zone
files.
Once the script is run, you should have files with names like "zone1.csv2", "zone2.csv2", and "zone3.csv2". These files are csv2 zone files
that MaraDNS will be able to parse. Copy these csv2 zone files to a place where MaraDNS can find the zone files.
Should there already be a "zone1.csv2" file when bind2csv2 is run, the "zone1.csv2" file will be replaced.
OPTIONS
None. Bind2csv2 can only be used as above.
BUGS
bind2csv2 is not a perfect zone file converter. In particular, bind2csv2 does not act like BIND when NS records have different TTLs. Please
make sure all NS records in your BIND zone files have the same TTL.
In addition, bind2csv2 also does not support all resource record types that BIND supports. Only the following RRs are supported by
bind2csv2: A AAAA AFSDB CNAME GPOS HINFO ISDN LOC MB MD MF MG MINFO MR MX NS NSAP PTR PX RP RT SOA SPF SRV TXT WKS X25
MARADNS September 2007 BIND2CSV2(1)
Check Out this Related Man Page
ASKMARA-TCP(1) askmara-tcp ASKMARA-TCP(1)NAME
askmara-tcp - do simple dns queries over TCP
DESCRIPTION
askmara-tcp queries the user-specified dns server for records, and outputs the reply in a csv2-compatible format (csv2 is the format of
zone files that maradns uses). However unlike askmara it uses TCP rather than UDP.
USAGE
askmara-tcp [-n] [-v|-t timeout] query [server]
OPTIONS -t If this is present, the following argument is the askmara-tcp timeout, in seconds. Note that askmara-tcp can not both have a user-
defined timeout and verbose output.
-v If this is set, askmara-tcp will verbosely output the complete reply that the server sent. Note that this verbose output is not
csv2-compatible.
-n If this is set, askmara-tcp, when sending out a query, will not request DNS recursion; in other words, askmara-tcp will request that
the remote DNS server not contact other DNS servers to answer the query in question.
query
dns record to be queried. The query has two sections: The type of record we desire, and the hostname we want this record for.
The type of query can have two forms: A one-letter mnemonic, or a numeric rtype followed by a colon. This is immediately concatenated by
the full name of the host name we wish to look up.
For example, to ask for the IP of 'example.com.', we can use the one-letter mnemonic, in the form 'Aexample.com.', or we can use the
numeric RR followed by a colon, giving the query '1:example.com.' (since A has the record type of one). Note that the query name needs the
trailing dot at the end.
Askmara supports a handful one-letter mnemonics, as follows:
A signifies a request for an A (ipv4 address) RR
N signifies a NS RR
C signifies that we are asking for a CNAME RR
S signifies that we want a SOA RR
P signifies that we want a PTR RR
@ signifies that we mant a MX RR
T signifies that we want a TXT RR
Z signifies that we want to ask for all RRs.
server
IP address of the dns server to be queried. If no server is given, askmara-tcp will query 127.0.0.1.
EXAMPLES
Asking the server with the ip 127.0.0.1 for the IP address of example.com:
askmara-tcp Aexample.com.
Asking the server with the ip 198.41.0.4 for the IP address of example.com:
askmara-tcp Aexample.com. 198.41.0.4
Asking the server with the ip address 127.0.0.1 for the IP address of example.com, using the rr_number:query format:
askmara-tcp 1:example.com.
Asking the server with the ip address 127.0.0.1 for a SRV record. In particular, we ask for the "http over tcp" service for example.net.
Since askmara-tcp doesn't have a mnemonic for SRV record types, we use the numeric code (33 for SRV):
askmara-tcp 33:_http._tcp.example.net.
Asking the server with the ip address 127.0.0.1 for the AAAA (ipv6 ip) record for example.net:
askmara-tcp 28:example.net.
Note that the output will be a raw DNS packet in both the SRV and AAAA examples.
BUGS
When askmara-tcp is asked for an SOA record, the output of askmara-tcp closely resembles the format of a csv2 file, but can not be parsed
as a csv2 file without modification.
askmara-tcp outputs multi-chunk ("character-string") TXT records incorrectly (it only outputs the first chunk).
SEE ALSO maradns(8), askmara(1)
http://www.maradns.org
LEGAL DISCLAIMER
THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
AUTHOR
MaraDNS is written by Sam Trenholme. Jaakko Niemi used 5 minutes to roll this manpage together, which Sam has subsequently revised.
January 2002 askmara-tcp ASKMARA-TCP(1)