bsd.m3th.org
Yet another *nix admin blog

The local press tried to be hilarious? See the story by The Star.

I made a request to TM for reverse dns delegation on static IP address ranges that were assigned to office SDSL accounts. 2 thumbs up for their prompt response and action on my query. Now my name servers are managing the pointers for the IP address ranges. I’m a user of DJB’s tinydns. Below are tinydns data entries. The IP addresses value and domain are masked.

=router.mydomain.com:124.99.199.41
=firewall.mydomain.com:124.99.199.42
=ns3.mydomain.com:124.99.199.43
.41.199.99.124.in-addr.arpa::ns1.mydomain.com:3600
.41.199.99.124.in-addr.arpa::ns2.mydomain.com:3600
.41.199.99.124.in-addr.arpa::ns3.mydomain.com:3600
.41.199.99.124.in-addr.arpa::ns4.mydomain.com:3600
.42.199.99.124.in-addr.arpa::ns1.mydomain.com:3600
.42.199.99.124.in-addr.arpa::ns2.mydomain.com:3600
.42.199.99.124.in-addr.arpa::ns3.mydomain.com:3600
.42.199.99.124.in-addr.arpa::ns4.mydomain.com:3600
.43.199.99.124.in-addr.arpa::ns1.mydomain.com:3600
.43.199.99.124.in-addr.arpa::ns2.mydomain.com:3600
.43.199.99.124.in-addr.arpa::ns3.mydomain.com:3600
.43.199.99.124.in-addr.arpa::ns4.mydomain.com:3600
.44.199.99.124.in-addr.arpa::ns1.mydomain.com:3600
.44.199.99.124.in-addr.arpa::ns2.mydomain.com:3600
.44.199.99.124.in-addr.arpa::ns3.mydomain.com:3600
.44.199.99.124.in-addr.arpa::ns4.mydomain.com:3600
.45.199.99.124.in-addr.arpa::ns1.mydomain.com:3600
.45.199.99.124.in-addr.arpa::ns2.mydomain.com:3600
.45.199.99.124.in-addr.arpa::ns3.mydomain.com:3600
.45.199.99.124.in-addr.arpa::ns4.mydomain.com:3600
.46.199.99.124.in-addr.arpa::ns1.mydomain.com:3600
.46.199.99.124.in-addr.arpa::ns2.mydomain.com:3600
.46.199.99.124.in-addr.arpa::ns3.mydomain.com:3600
.46.199.99.124.in-addr.arpa::ns4.mydomain.com:3600


The Lookup

%dig 42.199.99.124.in-addr.arpa NS

; <<>> DiG 9.3.4 <<>> 42.199.99.124.in-addr.arpa NS
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1968
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 4

;; QUESTION SECTION:
;42.199.99.124.in-addr.arpa. IN NS

;; ANSWER SECTION:
42.199.99.124.in-addr.arpa. 3600 IN NS ns1.mydomain.com.
42.199.99.124.in-addr.arpa. 3600 IN NS ns2.mydomain.com.
42.199.99.124.in-addr.arpa. 3600 IN NS ns3.mydomain.com.
42.199.99.124.in-addr.arpa. 3600 IN NS ns4.mydomain.com.

;; ADDITIONAL SECTION:
ns1.mydomain.com. 22258 IN A 202.191.74.118
ns2.mydomain.com. 22260 IN A 203.175.167.108
ns3.mydomain.com. 22260 IN A 124.99.199.43
ns4.mydomain.com. 22260 IN A 212.214.138.2

;; Query time: 44 msec
;; SERVER: 161.142.2.17#53(161.142.2.17)
;; WHEN: Wed Oct 15 12:21:10 2008
;; MSG SIZE rcvd: 195


%nslookup 124.99.199.42
Server: 161.142.2.17
Address: 161.142.2.17#53

Non-authoritative answer:
42.199.99.124.in-addr.arpa name = firewall.mydomain.com.

Authoritative answers can be found from:
42.199.99.124.in-addr.arpa nameserver = ns4.mydomain.com.
42.199.99.124.in-addr.arpa nameserver = ns1.mydomain.com.
42.199.99.124.in-addr.arpa nameserver = ns2.mydomain.com.
42.199.99.124.in-addr.arpa nameserver = ns3.mydomain.com.
ns1.mydomain.com internet address = 202.191.74.118
ns2.mydomain.com internet address = 203.175.167.108
ns3.mydomain.com internet address = 124.99.199.43
ns4.mydomain.com internet address = 212.214.138.2