How not to set up your DNS (part 13)

December 7, 2006

In the traditional illustrated format:

; sdig ns aescorts.net.
ns1.bnmq.com.
ns2.bnmq.com.
; dig mx aescorts.net. @ns1.bnmq.com.

[...]
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
[...]
;; AUTHORITY SECTION:
. 1 IN SOA . abuse.opticaljungle.com. ...

That's an interestingly grandiose claim of authority bnmq.com is making there. (And also an interesting primary nameserver they claim the DNS root has.)

For bonus points, they actually return an A record for aescorts.net, although without the usual authority records that you'd expect. It's just queries for other records that they fail. I'm left wondering if the bnmq.com nameservers are actually some species of caching nameservers, and bits have fallen out of their caches and haven't been refreshed.

(Given everything else, we probably didn't want to get email from a domain called 'aescorts.net' anyways.)

Written on 07 December 2006.
« Setting up switches to avoid unwanted VLAN leakage
Another obnoxious discovery about Ubuntu's /var/run stuff »

Page tools: View Source, Add Comment.
Search:
Login: Password:
Atom Syndication: Recent Comments.

Last modified: Thu Dec 7 10:49:19 2006
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.