How not to configure your DNS

david% dig -x 190.208.19.230

; <<>> DiG 9.4.2-P2 <<>> -x 190.208.19.230
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35398
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;230.19.208.190.in-addr.arpa.   IN      PTR

;; ANSWER SECTION:
230.19.208.190.in-addr.arpa. 3600 IN    PTR     190.208.19.230.

;; Query time: 253 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Apr 10 10:00:21 2009
;; MSG SIZE  rcvd: 73

Whoops

One thought on “How not to configure your DNS”

Tricky
on April 10, 2009 at 1:46 pm said:

Lol. I’ve seen that happen a few times.

Oddly, a plain dig returns the corresponding forward record:

[ brendan@watricky : 14:44:17 : ~ ]
🙂 dig 190.208.19.230

; <<>> DiG 9.6.0-P1 <<>> 190.208.19.230
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54312
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;190.208.19.230. IN A

;; ANSWER SECTION:
190.208.19.230. 0 IN A 190.208.19.230

;; Query time: 1 msec
;; SERVER: 10.5.1.254#53(10.5.1.254)
;; WHEN: Fri Apr 10 14:44:22 2009
;; MSG SIZE rcvd: 48

One thought on “How not to configure your DNS”

Leave a Reply Cancel reply