We've had exactly the same here that led to Golog being implemented.
Golog is just a two line patch to bind to redirect 'NXDOMAIN' :<br>
<br>
;; QUESTION SECTION:<br>
;ww.gooooooooregergerger.com. IN A<br>
<br>
;; ANSWER SECTION:<br>
<a href="http://ww.gooooooooregergerger.com">ww.gooooooooregergerger.com</a>. 10000 IN A XX.XX.XX.XX<br>
<a href="http://ww.gooooooooregergerger.com">ww.gooooooooregergerger.com</a>. 10000 IN TXT "NXDOMAIN"<br>
<br>
While we had the same concerns the implementation led to no problems
except for a brief round of complaints from users. We did however only
issue it to our users and do not preform any lookups from our server
base to it. While it's something I personally don't like the cut
throat DSL market does make it necessary for us to create revenue where
ever possible without a major effect on customers and to be honest
Golog is one of the lesser evil services of this type I have come
across.<br>
<br>
regards<br>
<br>
Rod<br>
<br>
Luke Besson wrote:
<blockquote cite="mid33f728c0610190550x28178a80r5036d5ebf545d096@mail.gmail.com" type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=ISO-8859-1">
I work for a big French ISP and I manage the DNS architecture (based on
Linux+Bind); Golog proposed to our society the DNS redirect service
(redirect all the not existant domains according to marketing criteria).<br>
Even if our marketing team would like to join this solution, our
technical team opposes hardly to such a not-standard implementation of
the DNS.
<br>
Can you suggest me any objective reason in order to invalidate this proposal?<br>
<br>
Regards<br>
<br>
Luke<br>
<br>
</blockquote>