[dns-operations] Worst current practice example

[Lutz Donnerhacke]

I recently came across of an glue only domain, ...

Resolving aplex.com.tw/IN/MX works the first time and then fails for long
period. "dig +trace" fails immediatly due to missing glue handling.

************************************************************************

;; QUESTION SECTION:
;aplex.com.tw.                  IN      MX

;; AUTHORITY SECTION:
aplex.com.tw.           86400   IN      NS      dns2.aplex.com.tw.
aplex.com.tw.           86400   IN      NS      dns1.aplex.com.tw.

;; ADDITIONAL SECTION:
dns1.aplex.com.tw.      86400   IN      A       220.130.128.200
dns2.aplex.com.tw.      86400   IN      A       220.130.128.200

;; Query time: 357 msec
;; SERVER: 211.79.207.25#53(e.twnic.net.tw.)

************************************************************************

;; QUESTION SECTION:
;aplex.com.tw.                  IN      MX

;; ANSWER SECTION:
aplex.com.tw.           60      IN      MX      10 spam.aplex.com.tw.

;; ADDITIONAL SECTION:
spam.aplex.com.tw.      60      IN      A       220.130.128.201

;; Query time: 323 msec
;; SERVER: 220.130.128.200#53(220.130.128.200)

************************************************************************

;; QUESTION SECTION:
;dns1.aplex.com.tw.             IN      A

;; AUTHORITY SECTION:
aplex.com.tw.           60      IN      SOA     nas.aplex.com.tw.
hostmaster.aplex.com.tw. 31 900 600 3600 60

;; Query time: 338 msec
;; SERVER: 220.130.128.200#53(220.130.128.200)

************************************************************************

;; QUESTION SECTION:
;dns2.aplex.com.tw.             IN      A

;; AUTHORITY SECTION:
aplex.com.tw.           60      IN      SOA     nas.aplex.com.tw.
hostmaster.aplex.com.tw. 31 900 600 3600 60

;; Query time: 322 msec
;; SERVER: 220.130.128.200#53(220.130.128.200)

************************************************************************