VHost

A 'vHost' (virtual host) allows users to hide their hostmask (i.e., Rizon-BA37C5B3.rogers.com) with something creative (i.e., i.am.awesome). The nickname must be registered in order to request a vHost.

Rules

All vHosts

1. must contain a dot (aka . ) and can only contain alphanumeric characters, dots ( . ) and dashes ( - );
   • Valid: some.vhost
   • Invalid: somevhost
2. must not contain a @
   • Invalid: blah@my.new.host
3. must not be an IP or IP look-a-like;
   • Invalid: 127.0.0.1 or 127.o.o.1
4. must not resolve (basically, the vHost can't point to an actual site);
   • Valid: not.a.real.website
   • Invalid: google.com or xertion.org
   • Exception to this rule is if you own the domain. Please join #help and speak with an operator;
5. must not mimic government organizations such as FBI, CIA, ATF, Interpol, etc. This also refers to MPAA or RIAA;
6. must not contain the words 'ircop', 'admin', 'network', 'xertion', or any IRC Operator's nick;
7. must not contain racist words (what is considered racist/derogatory by operator discretion);
8. must not refer to other networks/spamming;
   • Invalid: join.my.channel or come.to.irc.blahblahblah.net
9. must not refer to "kiddy"-like activity. (dosing, rooting, "carding," etc.)

Understanding vHosts

1. vHosts are first filtered by a bot, which validates the vHosts against the rules. If your vHost keeps getting rejected and you think it is a mistake, /join #help for further assistance.
2. vHosts must then be manually approved.
3. Ban evasion using vHosts will cause you to get: your vHost removed, network banned from Xertion for a set period of time, and vHost banned for an extended period.

Requesting a vHost

You must have a registered nickname in order to request a vHost. In order to register your nickname, please visit Register your nickname

To request a vHost, use the command

/msg HostServ REQUEST vhost.goes.here

Once your vHost is approved, it can be turned on with

/msg HostServ ON

Understanding of the vHost system

When you request a vHost, yes, a bot first checks it. But that request is also sent to the vHost team.

• So if you keep on pounding the system without correcting your error, we see it. Over and over.

Once your request is vHost bot approved, it is presented to the vHost team with a simple approve or reject choice.

And then finally, some human on the vHost team will accept or reject the request.

• This can take anywhere from 6 seconds, and a few hours.
  • Not everyone on the vHost team lives in your timezone.
  • Sometimes a vHost team member may defer (put off) an answer pending consultation with other team members.
• Reminding staff to approve your vHost is nothing but frustrating. The vHost team did see your request in every condition where you got a valid response from the vHost request system. Please wait patiently.

Please do not experiment with different vHost requests, or put in a default example and expect to change it a few minutes later.