This page has not been updated in many many years. The information is valid to
a degree but don't count on it.
Newcomers guide to DALnet
Welcome to the "Newcomers guide to DALnet".
The purpose of this page is to give you an introduction to DALnet, the IRC network.
I will try to explain what DALnet is, what advantages it has compared to other existing
IRC networks and teach you what you need to know to get started on DALnet.
DALnet was founded in early 1995 by Sven Nielsen (Dalvenjah
FoxFire), together with MirclMax,
Morpher and Lefler when
they got tired of the havoc on EFnet. The Services were created a short while afterwards,
and got added to DALnet. Services allows persons to register their nickname(s) and
channel(s), and thus prevent other people from taking them from you.
DALnet has several advantages compared to most other IRC networks, you can find
a list of some of them below.
Does this sound nice? Are you willing to give it a try? Then continue reading, and I
will explain to you how you connect to DALnet, and how to get started with things
when you are connected.
- 30 character nicknames.
- Did you always want to use your Ohsoverylongnickname, but never
been able to due to the 9 character limit most other IRC networks
has? Look no further, DALnet is the network for you. On DALnet
you can use up to 30 characters in your nickname.
- DALnet provide you with an outstanding service which allows you to
register your nickname(s) and channel(s) so that noone can steal
them from you while you are offline. No more need for bots
holding the channel for you until you return, no more takeovers
and no more fights about someone using your nickname. DALnets
Services does all this for you, and much more.
- DALnet is called "The friendly network",
and we are proud of it. If you are in need of assistance, there will most
likely be someone available to help you, and try to solve the problem(s)
together with you.
Connecting to DALnet
There are two ways of connecting to DALnet.
The best way to do it is by using one of the available IRC clients,
and use it to connect to one of our servers. If you don't have one
installed already, I suggest you download one and installs it before
you read any further. There are several clients available for you:
mIRC and PIRCH for Windows, Ircle and
Homer for Macintosh, AmIRC for Amiga and ircII
for Unix. All of these can be downloaded from ftp.dal.net /pub/dalnet/clients/.
If you can't download and install, or aren't allowed to compile a
a client of your own, you can still use DALnet through the telnet-gateway
we provide you with. All you need when using this gateway is your
favourite telnet client. Point it to telnet.dal.net
, and log on with the userid dalnet
Example of a telnet session:
Connected to telnet.dal.net.
Escape character is '^]'.
Red Hat Linux release 4.0 (Colgate)
Kernel 2.0.20 on an i586
Password: [Press RETURN]
Last login: Tue Jan 21 11:50:00 from Husky1.StMarys.C
found 24 users
Welcome to DALnet!
You are telnet client user number 24 of 35.
Please see http://www.dal.net for info on DALnet.
Don't forget to register your channels and nick!
/msg chanserv help
/msg nickserv help
Please do NOT not use the name rh129-22.reshall.ucsd.edu when telnetting to
this client. Use telnet.dal.net !!!!!!!
Maelcum, Eagle, JoelKatz, and EasyRider for their help in making this
telnet client possible!
What would you like your nickname on DALnet to be?
If you are using telnet to access DALnet, you will automatically be
connected to mindijari.ca.us.dal.net
after entering what Nickname to use. If you are using the other method
of connecting to DALnet, with a client of your own you need to find
out how to specify what server and port to connect to. Then point it
to irc.dal.net port 7000, which will put
you on a random DALnet server. For more information on what servers
are available to you, please visit http://www.dal.net/servers/ and
try to find someone as geographically close to you as possible, to
avoid getting long responsetimes between the server and yourself.
When you connect to one of the DALnet servers the first thing you will see is something similar to the following
*** If you are having problems connecting due to ping timeouts, please type /raw pong 369D6D56 or
/quote pong 369D6D56 now.
This feature is here to prevent people from faking the address they are connecting from (Called spoofing),
unfortunatelly some strange clients will not work with this. This should not be a problem if you are using one
of the clients I have recommended you to get above, but if your client should freeze after those lines, do what
it says. And type /raw pong thelistednumber or
/raw pong thelistednumber to get the server to accept your client.
*** If you still have trouble connecting, please email email@example.com with the name and version of the c
lient you are using, and the server you tried to connect to: (name.of.server.on.dal.net)
Sometimes you may also get this message:
*** You are not welcome on this server: Reason for the serverban. Email
firstname.lastname@example.org for more information. (from name.of.server.on.dal.net)
This means you are banned (K-lined) from that specific server. Before you send a mail to email@example.com
to ask why you are banned, you should try to connect to another server instead. If that works, you should
contact the administration for the server you were banned on, asking them why the ban is there. The kline team
has enough work as it is already, without having to deal with single K-lines too. To get the administrative
information about a specific server when you have connected to another server, type
/admin name.of.server.on.dal.net, and you will be given a few lines of information on who to
contact for information on that server.
If you are very unlucky you might get this message:
*** You are not welcome on this network. Email firstname.lastname@example.org for more information.
When you get the above message, that tells you that you are banned from the entire network you need to write
a mail to email@example.com and ask what is wrong, and what can be done about it. When you send the mail to
firstname.lastname@example.org, include what the message looks like that the server sends you, when you tried to connect
(what time, and what timezone you are in) together with information on what client you are using, and from
what adress you tried to establish the connection.
When you finished connecting you might also get a notice from ChanServ, looking something like this:
-NickServ- This nick is owned by someone else. Please choose another.
This means that you are using a nickname that is registered to someone else on DALnet, or to yourself from
another user@host address than the one you are currently using. If it is your nickname, and you know the
password for it, type:
-NickServ- If this is your nick, type: /msg NickServ IDENTIFY
-NickServ- You have 60 seconds to comply before I send a nick collide.
/msg NickServ identify putyourpasswordhere and if it is entered
correctly you will see something like:
-NickServ- password accepted for yournick
After all this, you are ready to start using DALnet. In the next few sections I will explain how
to get started with the various Services, and how to use the basic commands they offer.
NickServ - "Protector of names"
NickServ is the first thing I recommend you to get in touch with when you are a newcomer to
DALnet. NickServ is the part of Services that takes care of your nickname, and all settings
associated with it. To assure that noone else will be able to take your nickname away from
you, without a possibility for you to recover it again. When you register your nickname it
will be added to a huge database, for later association with channels, memos and all
other things Services allows you to do.
The first thing you need to do when you are to figure out a nice nickname, that suits you,
and that you like. Is to figure out if someone else owns it already or not. NickServ makes
you aware of this rather quickly in most cases, if it tells you that you are using someone
elses nickname, and requires you to change, do this by issuing the command:
/nick AnotherNickname (Exchange AnotherNickname for
whatever nickname you want to try).
If NickServ doesn't tell you anything the nick is hopefully free for you to use. But to
be really sure, you should doublecheck. To get information on if a nickname is registered
or not you need to send a command to NickServ, and request that it provides you with the
necessary information on it. To do this, type: /msg NickServ
info NicknameToCheck (and exchange NicknameToCheck, with the nickname you
want information on. *smiles*). If you check the information for the nick "Ahnberg" you
will probably get information that looks something like this:
-NickServ- *** Ahnberg is MillaNs Vampire Lord
And if it's not, you will just be told that "Nick Ahnberg is not registered".
If the nickname should happen to be registered you need to find a new one. Then repeat the
same procedure for that one too. When you find one that isn't registered already, you need
to tell NickServ that you want to register it to yourself. This is done with the following
command: /msg NickServ register passwordyouwanttouse,
and when it succeeds, NickServ will send you a few lines in reply.
-NickServ- Last seen address:
-NickServ- Last seen time:
Mon 12/02/96 11:46:36 CST
-NickServ- Time registered:
Tue 09/24/96 14:50:03 CDT
-NickServ- Time now:
Mon 12/02/96 11:52:38 CST
-NickServ- This user has enabled nick kill enforce.
-NickServ- *** End of Info ***
-NickServ- "nickname" is now registered under your account: email@example.com
When you have registered your nickname there is really nothing more you have to do to
be able to chat. Some hints I can give you though is to change one of the settings associated
to the nickname, namely the "nick kill enforce" option, which denies other persons to
use your nickname when you are not online yourself, or when you are using another nickname.
When you have nick kill enforce activated, anyone that tries to use your nickname will
be given 60 seconds to change. If they fail to change nickname within 60 seconds they will be
killed by Services. And an enforcer will be online in it's place for a little while
to stop the user from reconnecting, stealing the nickname again, and again, and again. To add
this option to your nickname you type: /msg NickServ set kill on
-NickServ- Your password is passwordyouwanttouse - please write it down
for later use.
-NickServ- For more information on NickServ type: /msg NickServ help
-NickServ- Change will become permanent at next database sync in 8 minute(s)
If you don't want to add the nick kill enforce option to your nickname, people will be
able to use it when you are offline. To get it back when you get online, and finds out that
someone else is using it, you need to tell Services to recover it for you. Send:
/msg NickServ recover nickname password to NickServ.
When it's done, Services will collide the user of your nickname and place an enforcer
to hold it, just to stop the user from reconnecting to get it again (as mentioned above, when
I talked about the nick enforce kill option). NickServ will then tell you:
-NickServ- User claiming your nick has been killed
If you want to use the nickname yourself at once after recovering it, you need to ask NickServ
to release it from the enforcing. Do this by typing: /msg NickServ
release nickname, and when NickServ tells you it is done with your request, you can
change your nickname and use your own.
-NickServ- Type /msg NickServ release nickname to get it back
There are some important things you should keep in mind considering your nickname, and the
password you have chosen for it. When you are choosing a password for your nickname, be sure
to be as careful as when you are dealing with the password for your own account. If it's
lost it can take a while before someone can help you get it for you, but you should know that
there are possibilities of recovering it if you happen to loose, or forget it. When
this happens to you, join #dragonrealm and tell us that you have lost your password,
and that you would like a CSop to help you recover it for you. Have patience, CSops have
ALOT to do, and you might have to wait for a while. You should also keep in mind that passwords
are cAsE sEnSiTIvE, so you should always be careful and write it EXACTLY as it looked when
you registered the nickname with it. When you are about to identify with NickServ you should
ALWAYS check to see if it is the real NickServ that is online, and noone claming
to be (if you should happen to end up on another network). There are alot of people without
lives that tries to steal peoples passwords, and mess up their nicknames for their own wicked
pleasure. To prevent this from happen, always make sure you are sending the password to the
one, and only, DALnet NickServ. And to NOONE else. If someone asks you about your password,
NEVER give it out. Even though the person might claim to be god himself you should not
give it out. NOONE have the right to your password, except yourself. You should never EVER
use a script, or automated functions, that automatically identifies with NickServ for you
whenever you log onto IRC. This is the most common reason that people loose their nicknames,
and have to go through a great deal of problems to get it back. Finally, when you have made
sure that NickServ really is NickServ, and nothing else. You identify by typing:
/msg NickServ identify password, to verify yourself as the owner of the
For more information on NickServ and it's other functions, please visit the NickServ part
of the official DALnet homepage. It can be found at
http://www.dal.net/services/, or you can get online help by typing:
/msg NickServ help.
If you for some reason should decide that you no longer want to be listed as owner of your
nickname, you can just drop it. You do this by identifying with NickServ as I just told you.
After that send: /msg NickServ drop nickname to
NickServ, and it will tell you that the nickname is removed from it's databases.
ChanServ - "Guardian of channels"
When you have walked around on the available channels on DALnet, and learned a little
about how things work, and what you can do. You might want to get a place of your own
where you can take your friends for a chat, or simply a channel where you hang out,
test things, etc. This is when ChanServ comes into the picture.
ChanServ is the part of DALnet Services that takes care of the channels, their options,
and everything else that needs to be dealt with concerning channels.
When you're going to register a channel, you need to go through almost the same procedure
as when choosing nickname. ChanServ also contains that info command, that gives information
on registered channels. Decide on a channelname, and then type:
/msg ChanServ info #channel to see some information about it.
-ChanServ- *** Info on #dragonrealm
If ChanServ says the channel isn't registered, you are free to do it yourself. To do this
you need to tell ChanServ about it, just as you did with your nick. Join the channel you
want to register (you need to have ops in there to be able to register it), and type:
/msg ChanServ register #channel passwordyouwanttouse Description
of the channel goes here.
-ChanServ- Founder :
-ChanServ- Mode Lock :
-ChanServ- Last Topic :
Welcome to DALnets IRCop/admin Channel.
DALnet Operator Channel
-ChanServ- URL :
-ChanServ- Options :
SecuredOps, "Sticky" Topics
-ChanServ- Registered :
Mon Jan 23 13:33:46 1995
-ChanServ- Last opping:
Tue Jan 21 21:26:26 1997
And then the channel is registered to you, and you will always be opped by ChanServ upon
arrival to the channel. And you are now ready to change some basic settings.
I recommend you to use a command that locks certain modes on the
channel, the ones most channels have nowadays are +nt. This means that
people can't send messages to the channel without actually beeing on
it themselves (+n), and that only channeloperators can change the
topic on the channel (+t). You might also want to add -k so that
people can't add strange keys to it if they happen to gain ops in the
channel when Services is absent, or during a netsplit. If this
happens, it is still pretty easy to get the channel back, but I will
talk about that further down on this page. Anyways, to add that
modelock I was telling you about you need to type: /msg ChanServ set #channel mlock
+nt-k. When the modelocks are added, they will be
automatically added by ChanServ when someone enters the channel. You
can also add options so that merely persons included in your AOP/SOP
list(s) are opped by ChanServ upon entering, or that the topic can't
be changed by someone else than the Founder himself, or the
SOP(s). You can also add the URL to a webpage to the channel, and
several other things. But I will not teach you how to do that in this
little guide *smiles*.
In the above load of text I mentioned something called AOP and SOP. AOPs
means AutoOPs, and are people that will be opped by ChanServ upon
entering the channel. People that are frequent visitors on a channel, and
gets to know the people in there, often gets AOP after a while so they
can help take care of the channel. The other thing, SOP, means SuperOP.
SuperOPs have some more "power" on the channel. They can for example add
new AOPs and add AKICKs (AutoKICKs, i.e. people that will be kicked automatically
upon entering the channel). The Founder is the only one that can add new SOPs,
and the Founder and SOPs can add new AOPs... this is the hirearchy of DALnet
To add SOP to your channel, you should first be identified with ChanServ as
the founder of the channel (explained later on), and then just type:
/msg ChanServ SOP #channel add nickname
You can also add user@host patterns to the SOP/AOP list(s), but since
I think that is merely a cause of problems, I will not teach you how to do it.
Instead I think you should ask all persons you plan on having as AOP/SOP on the
channel to register their nickname with NickServ, and then add them with that one.
Then it doesn't really matter what adress they are connected from, as long as
they have successfully identified with NickServ as the owner of the nickname.
To add a new AOP, you do exactly the same way as you did with SOPs, but exchange
the word SOP with AOP ofcourse: /msg ChanServ AOP
#channel add nickname.
To remove an AOP/SOP you just exchange
ADD with DEL, and the process will be reversed. And the nick will no longer
be opped by ChanServ upon entering the channel.
What if someone enters your channel while you are offline, gains op on it and bans you
from the channel? That is a good question, and I will answer it as efficiently
as possible. Everything can, ofcourse, be done through ChanServ. As long as the person
in the channel haven't found out your password and changed it to something else,
then your only way out of the mess is to come to #dragonrealm and ask a CSop to assist
you in the recovery of your password.
If you are banned from your own channel (or any channel that you are AOP, SOP or Founder
on), you can just type: /msg ChanServ unban #channel me
and ChanServ will clear all bans matching your address on the specified channel. After
that you should be able to enter without problem, gain ops and kick the person from the
channel. But if the person is faster than you are, and kicks you out again before you
manage to kick him out, there is another command you can give to ChanServ, called MKICK.
This command is invoked by typing: /msg ChanServ mkick #channel
and everyone in the channel will be kicked.
And if the person that tried to take your channel added some modes to deny you access to
the channel, for example added a +l 2 (max limit of 2 persons on the channel), you have
to use the MLOCK command again, to remove that flag too.
/msg ChanServ mlock #channel -l does this for you.
These guidlines should atleast give you some chance, and knowledge of recovering your
channel if someone got it from you.
The security issue with the channel is at least as important as when dealing with your
nickname. Someone managing to get the password to your channel can cause alot of damage,
change your settings, remove your AOP/SOP's and add new of his choice instead. Or merely
lock it from you, so that you can't even enter it. So before identifying with ChanServ
to gain founder access to your channel, make sure it's the real ChanServ, and not
a faked on, merely there to steal your password.
For more help on ChanServ and it's various functions, please visit
http://www.dal.net/services/ or type:
/msg ChanServ help while you are online.
MemoServ - "The messenger"
The third service included in Services is MemoServ, which allows you to send small
notes to registered nickname(s). If they are online or not doesn't really matter,
but the main thought behind it is to leave small notes to people that you need
to talk to about something, or merely give some information on something.
There are basically three things you can do with MemoServ. Send, Read and
Delete memos. To send a memo to a registered nickname you type:
/msg MemoServ send nickname Message goes here, maximum of 255 chars allowed.
, and the note will be sent to the specified nickname. NOTE: unread
notes are saved for 10 days, then automatically deleted. Read notes, that you haven't
deleted will lie around for 5 days before removing themselves.
If someone sent you a note (or more), you read these by typing:
/msg MemoServ read #, where # is the number of the message you want to
read. You have room for 50 notes in your MemoBox, if you exceed that number
noone can send you more notes unless some of them expire, or you delete them manually.
To delete a note from your MemoBox, type: /msg MemoServ
del #, where # is the number of the message you want to delete. When you
have deleted them you might want to purge them to remove them at once, instead of
having to wait. To do this, merely type: /msg MemoServ purge
and they will be removed.
There are some other things you can do with MemoServ too. Send memos to an entire channels
AOP, SOP and Founder for example. But to learn how to do this, either access MemoServs
online help: /msg MemoServ help, or visit http://www.dal.net/services/ and read the MemoServ
Useful things to know on DALnet
Well, that's about it. This is the final part of this little "
Newcomers guide to DALnet", and I hope you have had (or will have) some use
for it. If you liked it, please spread the URL around to your friends, and if you don't
like it, please send me a mail, telling me what you didn't like about it, and what you
would like me to change.
Finally I would like to give you some other references of help that you might want to
read if you want to know more about DALnet, and the things surrounding it.
- DALnets homepage.
- DALnets official homepage contains alot of useful information that
you can have use for as a user of DALnet. Documents that you can read,
information about the IRCopers you can read to perhaps get to know us
a little better. Or merely browse it because you are curious about what
you can find there.
- DALnet is called the "friendly network". If you have help with something, don't
doubt joining one of our helpchannels. There are several of them out there...
#mIRC for support for the mIRC client, #IRCLE for the IRCLE client, #help,
#irchelp and #help_channel for general help with IRC. If you need help with
something concerning the usage of Services, try #dalnethelp. And if you ever
need the assistance of an IRCoperator, please visit #dragonrealm where you
should be able to find a few of us.
- Help through mail.
- If you get no help through one of the above ways, you might want to send
an email to firstname.lastname@example.org, and someone
will do his, or her, best to provide you with a nice answer for your
[Visitors: [an error occurred while processing this directive]]
([an error occurred while processing this directive])