mIRC Home    About    Download    Register    News    Help

Print Thread
Joined: May 2009
Posts: 1
G
Mostly harmless
OP Offline
Mostly harmless
G
Joined: May 2009
Posts: 1
I dont know if this the appropriate section to ask this but ive been getting this error recently and its only for DALnet servers, i could connect to other servers with no problem. What should i tweak to fix this problem?

Awaiting for your help, thanks in advance

Joined: Oct 2003
Posts: 3,918
A
Hoopy frood
Offline
Hoopy frood
A
Joined: Oct 2003
Posts: 3,918
what server are you connecting to?


- argv[0] on EFnet #mIRC
- "Life is a pointer to an integer without a cast"
Joined: Apr 2009
Posts: 4
M
Self-satisified door
Offline
Self-satisified door
M
Joined: Apr 2009
Posts: 4
i think he did mention DALnet which i've been getting since last week ago n yet this problem is still here..

Joined: Oct 2003
Posts: 3,918
A
Hoopy frood
Offline
Hoopy frood
A
Joined: Oct 2003
Posts: 3,918
dalnet is not a server, it's a network. I'm able (and have been able since the original reply) to connect to dalnet's main roundrobin server irc.dal.net, but the OP might be trying to connect directly to one of the servers that may still be down.


- argv[0] on EFnet #mIRC
- "Life is a pointer to an integer without a cast"
Joined: Dec 2002
Posts: 2,031
R
Hoopy frood
Offline
Hoopy frood
R
Joined: Dec 2002
Posts: 2,031

No problems connecting to irc.dal.net here either.

~ Edit ~

Connected immediately on 6661 & 6667


Joined: May 2009
Posts: 1
S
Mostly harmless
Offline
Mostly harmless
S
Joined: May 2009
Posts: 1
i got the same problem like GGspoofer...dns pool on Dalnet only...but others server is ok...hope any1 got the resolution for it...thank q

Joined: Nov 2006
Posts: 1,559
H
Hoopy frood
Offline
Hoopy frood
H
Joined: Nov 2006
Posts: 1,559
It's preferable to use the general network alias (hostname), but as DalNet announces it's list of servers, you may connect using a specific server's address - via /server <specific server here>

The following is more a general reply to the "dns pool error" issue... smile

Some info
DNS - If you try to connect to an IRC network via the hostname (like "irc.dal.net"), mIRC has to look up the IP address(es) associated with that hostname. The actual lookup is done by windows, querying the DNS server of your current network connection. It's a very common procedure - the same thing happens if you enter some url in your webbrowser to open a website.

Pool - "DNS pool" describes the fact that more than one IP is associated with some hostname. Big IRC networks consist of many IRC servers, of which some but not necessarily all accept "regular" client connections. Those people running the IRC network will put some out of the available IP addresses in the "pool", so if for example a single server fails, you're still able to connect as usual using the IRC network's host address. It's a common method to change the IPs (servers) in the DNS pool frequently - to distribute "load" equally on the networks' servers - often called "round robin". And you may not take for granted that a specific server is available at all, be it under it's "name" or it's IP.

So what?
- Make sure neither a firewall nor an AntiVirus software is blocking IRC communication (that is: you've been able to chat on that network previously, and you didn't change any FW/AV/Router settings since). You could e.g. disable your firewall temporarily for testing purposes.

- mIRC may have used "old" (cached) pool data. Clear windows' local DNS resolving cache: in windows: "start" > "run" execute the command: "cmd /k ipconfig /flushdns" (without the quotation marks). After you've cleared the cache, retry connecting to the network: /server irc.dal.net

- The problem may also be on the "network's side". Maybe the "pool" is simply not up to date (it contains "dead" servers).

- Another possible souce of error: mIRC will try to connect on the port(s) specified in the settings for this server (mIRC options > connect > servers), or at the "default port" (mIRC options > connect > options). And maybe not all the servers in the pool accept a connection on your "usual" port.
While virtually every IRC network will accept connections on ports 6667 or 6669, you may try another port (e.g. in the range of 6665-7000). You can "enforce" a specific port by adding the port number to the server address, e.g.: /server irc.dal.net 7000

- Though very unlikely, the problem may also be caused on the "ISP's side": if the DNS server isn't working properly, you may get wrong DNS replies. But in case you're frequently unable to open websites, you should check the DNS server settings of your network connection, and maybe use another DNS server.


Link Copied to Clipboard