banned from efnet

[TeRrA]

I've been banned off efnet, I haven't got a clue as to what I've done to deserve this. I think someone else using the same hostname got me in to this mess.

[12:28pm] * Connecting to irc.efnet.net (6667)
————————————————————
[12:28pm] Closing Link: fia**-**.dsl.******.** (*** Banned )

I'm using the invision mirc client, latest version. Is there any way I can get back onto efnet? Its been a week now...[/quote]

[Beige]

Hello. Shame to hear about your problems. It's curious to note that you're using the irc.efnet.net round robin and end up rejected even so (in theory, connecting to irc.efnet.net should give you a new pseudo-random EFnet server every time you try to reconnect).

Try connecting at irc.blessed.net or irc.foxlink.net, and if either server rejects you, message me your actual hostname either via the PRIVATE forum message function (or alternatively via an e-mail to beige(AT)blessed(DOT)net), and I'll investigate what might be causing the problem.

In any case, our apologies for the trouble you're experiencing.

[TeRrA]

thanks that worked

[munky]

depending on the SOA record, the round robin effect won't work to get a pseudo-random server with each connection attempt. the users nameserver will cache the response for whatever time the SOA specifies, so he/she may be connecting to the same server for hours or days before the chance of a new pseudo-random response from the DNS query.

C:\>nslookup -q=soa efnet.net
Server: ns02.taylor01.mi.comcast.net
Address: 68.42.244.6

Non-authoritative answer:
efnet.net
primary name server = ns1.cet.net
responsible mail addr = hostmaster.cet.net
serial = 980630143
refresh = 1800 (30 mins)
retry = 900 (15 mins)
expire = 3600000 (41 days 16 hours)
default TTL = 3600 (1 hour)

efnet.net nameserver = ns1.cet.net
efnet.net nameserver = ns2.txic.net
ns1.cet.net internet address = 209.247.110.151
ns2.txic.net internet address = 207.44.132.57

in this case, it looks like 1 hr

[Beige]

(...) this case, it looks like 1 hr

Whereas the above is true for the authoritative query (e.g. affecting how quickly a newly added IP propagates), typically the caching DNS servers continue to honour the round robin structure of the original query. For example, a few non-authoritative lookups in a row with unix nslookup (with a caching bind8) look like this:

Non-authoritative answer:
Name: irc.efnet.net
Addresses: 206.128.219.244, 198.252.195.2, 198.175.186.5, 65.57.234.3, 194.109.129.220, 65.77.140.140, 216.32.207.207, 193.163.220.3, 217.17.33.10, 208.178.231.190, 204.92.73.10
Non-authoritative answer:
Name: irc.efnet.net
Addresses: 65.57.234.3, 194.109.129.220, 65.77.140.140, 216.32.207.207, 193.163.220.3, 217.17.33.10, 208.178.231.190, 204.92.73.10, 206.128.219.244, 198.252.195.2, 198.175.186.5
Non-authoritative answer:
Name: irc.efnet.net
Addresses: 204.92.73.10, 206.128.219.244, 198.252.195.2, 198.175.186.5, 65.57.234.3, 194.109.129.220, 65.77.140.140, 216.32.207.207, 193.163.220.3, 217.17.33.10, 208.178.231.190
Non-authoritative answer:
Name: irc.efnet.net
Addresses: 217.17.33.10, 208.178.231.190, 204.92.73.10, 206.128.219.244, 198.252.195.2, 198.175.186.5, 65.57.234.3, 194.109.129.220, 65.77.140.140, 216.32.207.207, 193.163.220.3

However, your reply (which was intuitively correct) prompted me to look at the Windows environment, and after a bit of testing and research it would indeed appear as if Windows has its own local caching for all DNS lookups.

For instructions on how to disable the local lookup cache in Windows, Microsoft has offered the following KB article:

http://support.microsoft.com/default.as ... bContent=1

It would also seem as if the local lookup cache can be flushed with the CMD tool ipconfig, and specifically "ipconfig /flushdns"

So, the moral of the story? I guess that it's no longer a good idea to recommend reconnecting to irc.efnet.net for Windows IRC users (who also are the clear majority of our userbase), unless they've disabled the local OS DNS lookup cache OR are willing to run "ipconfig /flushdns" in the CMD prompt between every reconnection attempt. They'll keep reconnecting to the same server for a good 15-30 minutes otherwise.

Anyway, relating to the question in the original post, if you're using Windows, please try connecting to individual EFnet servers directly (e.g. via this web page's Servers list) rather than via the irc.efnet.net round robin.

Beige

[seiki]

I notice that list is pretty outdated, and is missing some open I servers (such as 66.150.99.99), and contains some dead servers.

Please use these, as they're apparently the most accurate and up-to-date.

Random US EFnet servers:

irc.us.efnet.info. 3188 A 65.77.140.140
irc.us.efnet.info. 3188 A 66.150.99.99
irc.us.efnet.info. 3188 A 198.51.77.22
irc.us.efnet.info. 3188 A 198.175.186.5
irc.us.efnet.info. 3188 A 207.45.69.69
irc.us.efnet.info. 3188 A 208.178.231.190
irc.us.efnet.info. 3188 A 208.247.17.2
irc.us.efnet.info. 3188 A 216.32.207.207
irc.us.efnet.info. 3188 A 64.124.0.204
irc.us.efnet.info. 3188 A 65.57.234.3


Random EU EFnet servers:

irc.eu.efnet.info. 3601 A 193.216.236.142
irc.eu.efnet.info. 3601 A 194.109.129.220
irc.eu.efnet.info. 3601 A 194.159.164.195
irc.eu.efnet.info. 3601 A 195.149.88.251
irc.eu.efnet.info. 3601 A 195.159.0.90
irc.eu.efnet.info. 3601 A 213.8.254.10
irc.eu.efnet.info. 3601 A 213.239.111.2
irc.eu.efnet.info. 3601 A 217.17.33.10
irc.eu.efnet.info. 3601 A 80.240.238.17
irc.eu.efnet.info. 3601 A 193.11.251.5
irc.eu.efnet.info. 3601 A 193.163.220.3


Random CA EFnet servers:

irc.ca.efnet.info. 3601 A 198.163.216.60
irc.ca.efnet.info. 3601 A 204.92.73.10
irc.ca.efnet.info. 3601 A 205.210.145.2


Regards,
-douglas

[kemal]

our channel jupped drones from server / automatically bannde when join
#semarang

[Pills]

our channel jupped drones from server / automatically bannde when join
#semarang

How about we don't bump 9 month dead threads for a question that's asked and answered on the same page?

Locked.