Ok, I'll bite...
Michael Sokolov wrote:
3: Reverse DNS for 208.221.139.1 - Failed!
That's the piece of **** known as BIND. I can't wait to replace it with
MSDNS (Michael Sokolov's Domain Name Server), my own DNS server
implementation written 100% by me 100% from scratch, running under
4.3BSD-Quasijarus and strictly implementing the letter of RFC 1035.
In my opinion, RFCs are strong suggestions and intended for best
practice (e.g. I do not follow all of them with MTAs I manage,
particularly Exchange servers and MX backups). What compelling reason
do you have for implementing this particular RFC? Why RFC 1035 over,
say, this one?
http://tools.ietf.org/html/rfc527
Add that task to the TBD consultant's TODO list.
Nope. Finishing MSDNS is one of those gazillion tasks that must be done
by me and may not be outsourced. Besides, being part of the core
infrastructure it runs on our 4.3BSD-Quasijarus VAXen, not on pee sea
hardware, and I would never let anyone else near those even if someone
does claim to be old enough to know this stuff.
Ok, I must have missed something. You're missing a PTR record (I'm
guessing) on your MTA, and the remote MTA doesn't like it (with good
reason). And we're now we're talking about VAX, rewriting a new flavor
of DNS, and non "pee sea hardware"?
Please help us understand here.
