[swinog] SwiNOG-BE87 - Beer Event 87 - 12th of July 2010 @ Pumpstation / ZH
hi everybody here's the announcement for the next beer event. i hope weather will be good, if not we have to go to the outback lodge. please check the WEBSITE until 12:00 on the event-day to be sure about the place. the facts for the next event: - Date: 12th of July 2010 Time: starting around 18.30 o'clock Location: @lake in restaurant "Pumpstation" (see image; www.pumpstation.ch) backup location if bad weather: Outback Lodge. Registration deadline: 10.07.2010 12:00:00 - Please register here: http://swinog.mrmouse.ch/ since we have to make reservations, i need to know who's coming and who not. If you cannot attend and you're registered please inform me asap (+41 79 277 92 35). -steven ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] Huge delays in 1.4.e164.arpa NAPTR lookups?
Hi out there The last few days I noticed quite a large delay when I first dial a number from my asterisk server. I found that the problem is that the 1.4.e164.arpa lookup takes enormous time to return a NXDOMAIN == ast_get_enum(num='+41618269309', tech='sip', suffix='e164.arpa', options='', record=1 == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.arpa, 5148 ms compared to the e164.org or e164.info lookups: == ast_get_enum(num='+41618269309', tech='sip', suffix='e164.org', options='', record=1 == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.org, 141 ms == ast_get_enum(num='+41618269309', tech='sip', suffix='e164.info', options='', record=1 == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.info, 167 ms Of course, as soon as the NXDOMAIN is in the local DNS cache, dialing the same number is fast again. Also the previously working ETHZ e164.arpa test-tone number cannot be resolved anymore: == ast_get_enum(num='+41446580004', tech='sip', suffix='e164.arpa', options='', record=1 == ast_get_enum() profiling: FAIL, 4.0.0.0.8.5.6.4.4.1.4.e164.arpa, 5150 ms Has switch ceased to offer e164.arpa entries? 1.4.e164.arpa does not seem to be delegated anymore: ; <<>> DiG 9.6-ESV-R1 <<>> NS 1.4.e164.arpa. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49396 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;1.4.e164.arpa. IN NS ;; AUTHORITY SECTION: e164.arpa. 10784 IN SOA ns-pri.ripe.net. e164-contacts.ripe.net. 2010062458 14400 3600 2419200 14400 Deleagions found by dnsbajaj: Subdomains: 0.1.8.7.8.e164.arpa , 0.2.4.e164.arpa , 0.3.e164.arpa , 0.4.e164.arpa , 0.6.e164.arpa , 0.7.3.e164.arpa , 0.8.3.e164.arpa , 0.9.2.e164.arpa , 0.9.5.e164.arpa , 1.2.4.e164.arpa , 1.3.e164.arpa , 1.6.e164.arpa , 1.7.9.e164.arpa , 1.8.e164.arpa , 2.6.2.e164.arpa , 2.6.9.e164.arpa , 2.6.e164.arpa , 2.8.e164.arpa , 3.2.4.e164.arpa , 3.3.e164.arpa , 3.4.e164.arpa , 3.5.3.e164.arpa , 3.6.e164.arpa , 4.3.2.8.8.e164.arpa , 4.4.e164.arpa , 4.5.3.e164.arpa , 4.7.3.e164.arpa , 4.8.e164.arpa , 4.9.5.e164.arpa , 5.5.2.e164.arpa , 5.5.e164.arpa , 5.6.e164.arpa , 6.3.e164.arpa , 6.4.2.e164.arpa , 6.4.e164.arpa , 6.6.e164.arpa , 6.8.3.e164.arpa , 6.8.8.e164.arpa , 6.8.e164.arpa , 6.9.5.e164.arpa , 7.4.2.e164.arpa , 7.4.e164.arpa , 8.0.5.e164.arpa , 8.4.e164.arpa , 8.5.3.e164.arpa , 9.3.e164.arpa , 9.4.e164.arpa , 9.5.3.e164.arpa -Benoît- ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] IronPort E-Mail Reputation
> 4) Loopback* > > MSN/Hotmail > http://postmaster.msn.com/Services.aspx#SenderSolutions Has anyone managed to register their AS or simply some networks with SNDS ? I keep getting the very helpful "We're sorry! An error has occurred" error on the registration page, and requesting (repeated) help from the contact email msn-s...@microsoft.com returns zip/null/nada... It's like sending mail into a black hole... Cheers, Markus ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] IronPort E-Mail Reputation
* on the Wed, Jun 23, 2010 at 03:33:00PM +0200, Patrick Studer wrote: > So, we tried to get some help from the cisco ironport support. There > answer wasn't very helpful either. They told us, that senderbase.org > is a complete other company and they don't have any contact and > we should try their website www.senderbase.org. Otherwise, if we don't > have a IronPort box, they will not help us. Sounds much alike to Microsofts "Smartscreen" (which, of course, is very stupid indeed, as everytime Microsoft calls something "smart"): http://seegras.discordia.ch/Blog/abused-by-microsoft/ Most solutions were already mentionned, I consider the rotating of IP-addresses (every time after you end up in blacklists AND you have fixed the problem) the most useful one. If this is too much a chore, you probably should ditch MDaemon for some other MTA which hasn't any problems with hat, like Exim or Postfix... Cheers Seegras -- "Those who give up essential liberties for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin "It's also true that those who would give up privacy for security are likely to end up with neither." -- Bruce Schneier ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
