<p>I'm hearing more and more about domain specific languages being thrown about and how they change the way you treat business logic, and I've seen <a href="http://ayende.com/blog/tags/domain-specific-languages" rel="noreferrer">Ayende's blog posts</a> and things, but I've never really gotten exactly why I would take my business logic away from the methods and situations I'm using in my provider.</p>

<p>If you've got some background using these things, any chance you could put it in real laymans terms:</p>

<ul>
<li>What exactly building DSLs means?</li>
<li>What languages are you using?</li>
<li>Where using a DSL makes sense?</li>
<li>What is the benefit of using DSLs?</li>
</ul>

DSL
stands for
Domain Specific Language
i.e. language designed specifically for solving problems in given area.
For example, Markdown (markup language used to edit posts on SO) can be considered as a DSL.
Personally I find a place for DSL almost in every large project I'm working on. Most often I need some kind of SQL-like query language. Another common usage is rule-based systems, you need some kind of language to specify rules\conditions.
DSL makes sense in context where it's difficult to describe\solve problem by traditional means.