PLANNED IN-ADDR.ARPA NAMESERVER CHANGE
This is a courtesy notification of an upcoming change to the
nameserver set for the IN-ADDR.ARPA zone.
There is no expected impact on the functional operation of the DNS
due to this change.
There are no actions required by DNS server operators or end users.
For more information about this work, please see
The IN-ADDR.ARPA zone is used to provide reverse mapping (number
to name) for IPv4. The servers which currently provide authoritative
DNS service for the IN-ADDR.ARPA zone are as follows:
On Wednesday 2010-02-16 processing will begin to change the nameserver
set to the following, as described in RFC 5855:
A.IN-ADDR-SERVERS.ARPA (operated by ARIN)
B.IN-ADDR-SERVERS.ARPA (operated by ICANN)
C.IN-ADDR-SERVERS.ARPA (operated by AfriNIC)
D.IN-ADDR-SERVERS.ARPA (operated by LACNIC)
E.IN-ADDR-SERVERS.ARPA (operated by APNIC)
F.IN-ADDR-SERVERS.ARPA (operated by RIPE NCC)
The usual IANA process for a change in the ARPA zone involves a
series of technical checks and the gathering of various authorisations,
and may take several days to complete.
Following this, the IN-ADDR.ARPA zone will be dropped from root
servers in two groups:
1. Week of 2011-02-21 -- 2011-02-25
B, C, E, G, I, M
2. Week of 2011-02-28 -- 2011-03-11
A, D, F, H, K, L
Individual root server operators will choose a time for the maintenance
within their respective window and follow their usual procedures
to carry out the change.
Courtesy notification will be sent to this list once this change
has been fully implemented.
Director DNS Operations
please suggest to microsfot, and relase hyperterminal for windows7 OS...
this will be very usefull for all IT.
> From: swinog-request(a)lists.swinog.ch
> Subject: swinog Digest, Vol 72, Issue 9
> To: swinog(a)lists.swinog.ch
> Date: Sat, 22 Jan 2011 12:00:01 +0100
> Send swinog mailing list submissions to
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> You can reach the person managing the list at
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of swinog digest..."
> Today's Topics:
> 1. Slightly Off-Topic, but hosters may know ... Zend optimizer
> (Matthias Hertzog)
> Message: 1
> Date: Fri, 21 Jan 2011 16:32:08 +0100
> From: "Matthias Hertzog" <m.hertzog(a)mhs.ch>
> Subject: [swinog] Slightly Off-Topic, but hosters may know ... Zend
> To: <swinog(a)swinog.ch>
> Message-ID: <E7041053CA2B4E21B6041B2CBD68F31F@mhertzog>
> Content-Type: text/plain; charset="iso-8859-1"
> Hi there!
> Did anyone in here has a reference of the "optimization passes" of Zend optimizer? (What is Level 1, What is Level 2, etc...)
> Thanks & have a good weekend,
Any information why we can't reach cablecom phone numbers, their website
or their DNS servers ?
Network & Security Engineer, HES-SO Fribourg
Mobile: +41 (0)78 619 73 53
I'm asking the list because someone might have experienced the same problems as we do atm.
It looks like Orange Mobile customers are denied access via HTTP to one of our (AS49983) prefixes and it very much looks like there's some sort of proxy in between blocking these requests. They always get a HTTP 403 error but according to Apache logs and tcpdump this clearly isn't generated by our servers. This doesn't happen on our other prefixes though, just 220.127.116.11/21
Has someone else perhaps seen this or a similar problem in the past with AS15796 / AS5511 ?
Does anyone know the "correct" contact at Orange for things like this? If so please contact me off-list.
MiroNet GmbH, Strassburgerallee 86, CH-4055 Basel
T +41 61 201 30 90, F +41 61 201 30 99