An important problem solved with IPv6 is the enormous amount of new IP numbers that can be given out. To this extent, even the smallest node on the internet (a cable modem/dialup) gets a staggering amount of IPs. Normally, somewhere in the range of 2^64 to 2^80 addresses.
With this new address space, people are more easily delegated address space resolving via a reversed DNS zone. The main problem we face is that inexperience and ignorance leads people to pollute their DNS zones.
A hostname on the internet is of the form hostname.domain.tld. Perhaps, if you are a delegation within the 'domain.tld' domain, you will receive a subdomain, which makes your hostname hostname.subdomain.domain.tld. This addressing scheme, which is documented in RFC1178, was devised to organize DNS as a logical hierarchy.
Having hostnames like 'I.am.the.king.of.the.internet.domain.tld' or any other form of sentence / phrase are without any doubt in disagreement with the hierarchical definition of the global naming system (DNS).
One of the biggest problems with this DNS pollution in general is the fact that the IP's for these 'vhosts' could have been used for a company providing dialup services, SSL webservers and other useful reasons instead of a 'nice vhost on irc'.
As a general rule of thumb; a hostname belongs to an interface on a machine. This interface should get a hierarchical name, named after the machine or a name describing the interface. Eg. 'raven.example.org': This box is called raven and is in the example.org domain. 'raven-adsl.example.org' which is raven's ADSL interface. 'crow.wlan.example.net' could then for instance be a laptop using the wireless LAN network of example.net.
Hostnames that consist of phrases, bogus domains, bad language or in other forms undesirable textual data, are considered to be DNS pollution and this form of behaviour will be acted upon on several IRC channels. Also IRCNet itself has a nice policy.
Joost 'Garion' Vunderink created a spam calculation script which can be found at http://spamcalc.net/, this allows semi-automatic checks for dnsspam. This script is also available through the following form: