Title: Reverse address
Post by: Rob Lensen on November 09, 2004, 05:21:21 AM
Post by: Rob Lensen on November 09, 2004, 05:21:21 AM
What is the proposed way of adding reverse zone records to Nictool?
Title: Re: Reverse address
Post by: matt on November 11, 2004, 12:18:14 AM
Post by: matt on November 11, 2004, 12:18:14 AM
| Rob Lensen |
What is the proposed way of adding reverse zone records to Nictool? |
Just add them like any other zone. For the IP space 192.168.0, you'd create a zone named: 0.168.192.in-addr.arpa. and then start filling it with PTR records.
Matt
Title: Re: Reverse address
Post by: LogicX on December 09, 2004, 12:20:33 PM
Post by: LogicX on December 09, 2004, 12:20:33 PM
How about classless?
on http://cr.yp.to/djbdns/dot-arpa.html
it states:
I have the following setup:
zone: 192-30.179.9.69.in-addr.arpa
194 PTR mail2.imcc.ca.
root:sector|2:16:31pm|: grep 194 data
+mail2.imcc.ca:69.9.179.194:3600::
^194.192-30.179.9.69.in-addr.arpa:mail2.imcc.ca.:3600::
So it can do forwards but seemingly not reverse accurately?
on http://cr.yp.to/djbdns/dot-arpa.html
it states:
In this case your data file should contain lines such as .144-145.3.2.1.in-addr.arpa:1.8.7.200:a .144-145.3.2.1.in-addr.arpa:1.8.7.201:b =phoenix.elysium.heaven.af.mil:1.2.3.144 ^144.144-145.3.2.1.in-addr.arpa:phoenix.elysium.heaven.af.mil =bogey.elysium.heaven.af.mil:1.2.3.145 ^145.144-145.3.2.1.in-addr.arpa:bogey.elysium.heaven.af.milusing the same name 144-145.3.2.1.in-addr.arpa selected by the parent administrator. Normally ^ lines are unnecessary, because they are automatically generated by = lines, but classless reverse delegation breaks this feature.
I have the following setup:
zone: 192-30.179.9.69.in-addr.arpa
194 PTR mail2.imcc.ca.
root:sector|2:16:31pm|: grep 194 data
+mail2.imcc.ca:69.9.179.194:3600::
^194.192-30.179.9.69.in-addr.arpa:mail2.imcc.ca.:3600::
root:sector|2:17:13pm|: dig 69.9.179.194 @ns2.imcc.ca; <<>> DiG 9.3.0 <<>> 69.9.179.194 @ns2.imcc.ca;; global options: printcmd;; connection timed out; no servers could be reachedroot:sector|2:20:15pm|: dig mail2.imcc.ca @ns2.imcc.ca; <<>> DiG 9.3.0 <<>> mail2.imcc.ca @ns2.imcc.ca;; global options: printcmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28745;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2;; QUESTION SECTION:;mail2.imcc.ca. IN A;; ANSWER SECTION:mail2.imcc.ca. 3600 IN A 69.9.179.194;; AUTHORITY SECTION:imcc.ca. 3600 IN NS ns1.imcc.ca.imcc.ca. 3600 IN NS ns2.imcc.ca.;; ADDITIONAL SECTION:ns1.imcc.ca. 3600 IN A 69.9.174.146ns2.imcc.ca. 3600 IN A 69.9.179.176;; Query time: 0 msec;; SERVER: 69.9.179.176#53(ns2.imcc.ca);; WHEN: Thu Dec 9 14:20:26 2004;; MSG SIZE rcvd: 115
So it can do forwards but seemingly not reverse accurately?
Title: Re: Reverse address
Post by: LogicX on December 10, 2004, 01:45:53 AM
Post by: LogicX on December 10, 2004, 01:45:53 AM
Note to self:
if you're having trouble troubleshooting a djbdns, tinydns reverse delegation of classless subnets then you may want to look into the fact that BIND has to call the FILENAME of the zones something like:
192-30.179.9.69.in-addr.arpa
however, the real zone that you've been delegated is:
192/30.179.9.69.in-addr.arpa
Even though Oddly, tinydns seemed to not like the 192-30 style, and would simply return the name again without an answer when I'd query it.
tinydns clearly handles reverse records without problem, as now that I've resolved my issue -- I love it
if you're having trouble troubleshooting a djbdns, tinydns reverse delegation of classless subnets then you may want to look into the fact that BIND has to call the FILENAME of the zones something like:
192-30.179.9.69.in-addr.arpa
however, the real zone that you've been delegated is:
192/30.179.9.69.in-addr.arpa
Even though Oddly, tinydns seemed to not like the 192-30 style, and would simply return the name again without an answer when I'd query it.
tinydns clearly handles reverse records without problem, as now that I've resolved my issue -- I love it