This position is an Application Administrator to support operations within our client’s department. This position has a critical role in delivering our services to clients and ensuring successful ongoing operation of our applications and services. It services a highly interactive software development build/release process as well as a rich operational environment with many interrelated applications/database services. The candidate should be self-motivated, detail oriented, adaptable to change and must work well in a flexible team environment with developers, QA, operations staff, system administrators and managers.

RESPONSIBILITIES:

Application and database support

• Provide on-going database administration in both back-end and front-end with application infrastructure support for our client’s administration systems, including the deployment of new applications.
• Review the physical design of existing databases for optimal database structures, database performance tuning, security, database backup/recovery strategy, implementing high-availability, and pro-active and reactive performance analysis, monitoring, troubleshooting and resolution of issues, capacity planning, monitoring data growth and system utilization, trend analysis and predicting future database resource requirements.
• Install web-base applications from ground up to full-ballooned implementation and support, including configuration at Unix/Linux/Windows system level, back-end integration with database, front-end integration with user-interface, final delivery to users to fulfill users’ requirement and on-going maintenance.
• Take the lead in ensuring that application and web services are configured and tuned according to application needs; provide troubleshooting as needed.
• Work with System Administrators to ensure test and production boxes conform to the software application configuration needs.
• Support the department-wide infrastructure application for database management, system monitoring and notification, job scheduling, deployment, provision and patching automation, application topology and service level management for campus-wide system performance.

Build/release activities

• Manage the build, tagging and release processes for a number of interdependent Java web applications and background processes in the QA and production environments. Ensure the build and release process is scalable and repeatable.
• Work with the development team to ensure efficient and understandable build procedures are adhered to and conform to a standard process for configuration and release management
• Develop and maintain tools that automate the building of software releases for an Agile-based development process. This is one of continuous integration, where the automated build process can be run many times a day if necessary.
• Work with and support the QA team to ensure automated test suites run as part of the continuous integration build process.

REQUIREMENT FOR SKILL AND COMPETENCIES:

• Expert hands-on with shell scripts, other scripting languages, preferably Perl, and tool automations
• Minimum 2 years database administration experience in Oracle and 3 years Application administration experience in Unix/Linux infrastructure environments is required.
• Hands-on experience of Oracle databases 10g for 24/7 database operations and tool automation in installation, configuration, backup/recovery, startup/shutdown, data refresh, and application integrations.
• Experience with OEM/Grid Control is highly desired.
• Knowledge and understanding of large scale ERP implementation and support like Oracle Financial and PeopleSoft systems.
• Expert knowledge of Apache and Tomcat, and other web/application servers such as JBoss
• Strong Unix and system administration skills with basic network and security knowledge
• Strong experience and ability in web applications deployment, configuration and integration from both OpenSource and Commercial based systems with or without sophisticated vendor support.
• Java/J2EE based programs
• Java/servlet/JSP based web applications
• Experience with Subversion, PVCS or similar source code repository
• Experience with Maven and familiarity with automated build processes
• Experience with the Agile development methodology and concepts of extreme programming and continuous integration
• Understanding of the layers/tiers of web applications and the communication protocol between the tiers with networking protocols (TCP/IP, HTTP, SSL, DNS, FTP, etc.)
• Ability to multi-task and work in a team environment is critical and should have excellent communication skills in both verbal and written forms.
• Ability to manage multiple competing priorities and work under pressure in high stress situations
• Excellent communication skills in both verbal and written
• Ability to work under pressure and to deliver results in a complex and dynamic operational environment

Qualifications

Minimum 5 years as an IT professional in build/release and application/database administration, plus one or more of the following areas: IT infrastructure operations 24/7, systems analysis and design, or application development.

Education
Bachelors Degree in Computer Science, Engineering or related field or equivalent experience

If you are interested, please send your resume to tsotelo@mindsource.com.

La settimana scorsa il governo inglese ha pubblicato il Digital Economy Bill:

Today, the Bill is published. It is made up of the actions in the Digital Britain Final Report that need primary legislation. That means it covers a really wide range of areas – from digital radio, to copyright reform, to spectrum, and then some – all focused on supporting the nation’s digital future

Le sezioni 18 e 19, in particolare, parlano della gestione dei nomi di dominio (quindi di Nominet). Sono un po’ lunghe, però il concetto è che il governo può nominare il “manager” (credo intenda il CEO) del registry inglese, se creda sia opportuno e, in generale, se pensa che questo abbia “fallito in relazione ai suoi doveri”. Per fallimento si intende:

A relevant failure is serious, for the purposes of this section, if it has adversely affected or is likely adversely to affect—

• the reputation or availability of electronic communications networks or electronic communications services provided in the United Kingdom or a part of the United Kingdom, or
• the interests of consumers or members of the public in the United Kingdom or a part of the United Kingdom.

In altre parole, se Nominet non si attiva per proteggere l’interesse degli utenti finali di internet il governo potrebbe decidere che Internet non riesce a auto-regolamentarsi e che ha bisogno dell’intervento diretto del governo per funzionare come si deve.

A stretto giro di posta, la risposta di Nominet.

Vedremo come andrà a finire. La sensazione, qui, è che c’é in gioco qualcosa di più dello statuto di un’azienda.

Three Charged in Comcast Cyber-Attack

Three men were charged by federal indictment Nov. 19 in connection with attacking Comcast.net and redirecting traffic to sites under their control. The group altered Comcast’s DNS records and is estimated to have cost the company more than $128,000.

From the RIPE DNS Lameness Statistics site:

The RIPE NCC runs a lameness check once a month on all DNS servers listed as delegation points within the RIPE NCC delegated zones. If a server fails this test, the test will be retried five times over a period of ten days, at varying times of day. If, after ten days, the server continues to fail the test, it is classed as lame.

Related document: RIPE-400

[via dns-wg]

What’s that you say? I can speed up my internet without doing anything? Surely not?

Well you’re kind of right, technically we’re not going to “speed it up”, however pages and websites will appear to load much faster, making better use of your connection.

Here’s how the Internet works:

Every computer has an Address that consists of up to 12 digits. Those addresses may look something like: 210.48.100.45

DNS is the name of the “protocol” that changes what you type (Such as Pressf1.co.nz or google.co.nz) in to that computers IP Address (210.48.100.45 or 64.233.169.104). Regardless of if you noticed this or not in the past, you’re using DNS every time you go to a new website, or Ads get loaded from a different server on the website you’re using. You’re most likely just using your ISP’s default servers, the details of them are given to your PC / Modem / Router and it’s told to use your ISP’s DNS servers every time you connect to the Interent.

The problem is that many DNS Servers like your ISP’s aren’t always setup as well as they could be.  That’s not specifically your ISP’s fault, it just seems to be the way it is. They’re just not always as reliable as they could be, nor as fast.

Here’s where OpenDNS comes in. It’s free for anybody to use, it’s super fast, incredibly reliable, and it’s got some other cool features you can play with later such as blocking pornographic websites or known malware sites. Here’s a little bit about OpenDNS:

http://www.opendns.com/solutions/overview/

Basically, some people at times  have issues with websites taking their time to load certain parts (Like the Ads seem to always stop the page from loading completely), and mostly people try to blame the website itself. However, what I’ve found in NZ is that it’s more often than not DNS that’s causing the issues if you’re trying to go to somewhere like TradeMe and find it’s slow (or that your PC may have spyware / malware / viruses etc), and not the actual website itself.

Anyway, here’s some useful documentation to get you up and running:

If you’re a Home User trialling it on a single PC

If you’re on a Network and want to change your Router settings

I suggest you try it on just your PC first, and be amazed at the difference it can really make to your browsing!

When you’re done, you can come back to this page and see if the Button up the top of the screen has changed to say that you’re now using OpenDNS, or not.

If this helps you, please let me know, leave a brief comment, I’d love to hear from you.

Search Engine Optimization and SEO Tools

Langsung saja :

# userdel -r named
# rm -rf /var/named

# wget ftp://ftp.isc.org/isc/bind9/9.2.2rc1/bind-9.2.2rc1.tar.gz
# tar -xzvf bind-9.2.2rc1.tar.gz
# cd bind-9.2.2rc1
# ./configure –prefix=/usr/local/named
# make
# make install
# adduser -d /var/named -s /bin/false named

# cd /var/named
# wget ftp://internic.net/domain/named.root
# vi db.127.0.0
isinya adalah :

$TTL 86400
@ IN SOA localhost. root.localhost. (
2003021500 ; serial
28800 ; refresh
14400 ; retry
3600000 ; expiry
86400 ) ; minimum

IN NS localhost.
1 IN PTR localhost.

# cp db.127.0.0 db.10.126.24
# vi db.localhost
isinya adalah :
$TTL 86400
$ORIGIN localhost.
@ IN SOA localhost. root.localhost. (
2003021500 ; serial
28800 ; refresh
14400 ; retry
3600000 ; expiry
86400 ) ; minimum

IN NS localhost.
IN A 127.0.0.1

# mkdir /usr/local/named/etc
# vi /usr/local/named/etc/named.conf
isinya adalah :

options {
directory “/var/named”;
allow-transfer { 10.126.24.2/32; };
pid-file “/var/named/named.pid”;
};

logging {
category lame-servers { null; };
};

zone “.” IN {
type hint;
file “named.root”;
};

zone “localhost” IN {
type master;
file “db.localhost”;
allow-update { none; };
};

zone “0.0.127.in-addr.arpa” IN {
type master;
file “db.127.0.0″;
allow-update { none; };
};

zone “24.126.10.in-addr.arpa” IN {
type master;
file “db.10.126.24″;
};

Kemudian meng-generate file konfigurasi yang akan digunakan oleh program rndc, ingat hasil dari perintah rndc-confgen bisa jadi berbeda dengan apa yang ditampilkan disini :

# /usr/local/named/sbin/rndc-confgen

Kemudian copy-paste dari hasil perintah tersebut diatas mulai dari baris “# Start of rndc.conf” sampai dengan baris “# End of rndc.conf”, simpan dengan nama file /usr/local/named/etc/rndc.conf . Kemudian copy-paste lagi dengan menghilangkan tanda “#”, mulai dari baris “# key “rndc-key”…” sampai dengan baris yang hampir paling bawah diatas baris “# End of named.conf ” yaitu sampai dengan baris “};” kemudian tambahkan pada file /usr/local/named/etc/named.conf . Sebagai contohnya adalah sebagai berikut ini, isi dari file /usr/local/named/etc/rndc.conf misalnya :

# Start of rndc.conf
key “rndc-key” {
algorithm hmac-md5;
secret “2LCJImnMimOwc1odWR6jfg==”;
};

options {
default-key “rndc-key”;
default-server 127.0.0.1;
default-port 953;
};
# End of rndc.conf

Sedangkan pada file /usr/local/named/etc/named.conf ditambahkan sebagai berikut :

key “rndc-key” {
algorithm hmac-md5;
secret “2LCJImnMimOwc1odWR6jfg==”;
};

controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { “rndc-key”; };
};

# /usr/local/named/sbin/rndc-confgen > confgen.tmp
# grep -v “^#” confgen.tmp > /usr/local/named/etc/rndc.conf
# grep “^#” confgen.tmp | sed 1,3d | sed -e “s/\# //g” | sed -e “s/End of named.conf//g” >> /usr/local/named/etc/named.conf
# rm -rf confgen.tmp

# chown -R named.named /var/named
# /usr/local/named/sbin/named -u named -c /usr/local/named/etc/named.conf

# echo “/usr/local/named/sbin/named -u named -c /usr/local/named/etc/named.conf” >> /etc/rc.local
# echo “nameserver 127.0.0.1″ > /etc/resolv.conf

Testing query menggunakan name server localhost dengan perintah host :
# host 127.0.0.1
1.0.0.127.in-addr.arpa domain name pointer localhost.
[root@wedus named]# host localhost
localhost has address 127.0.0.1

Atau dengan menggunakan perintah dig :

# dig -x 127.0.0.1
; <<>> DiG 9.2.2rc1 <<>> -x 127.0.0.1
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64212
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa. IN PTR

;; ANSWER SECTION:
1.0.0.127.in-addr.arpa. 86400 IN PTR localhost.

;; AUTHORITY SECTION:
0.0.127.in-addr.arpa. 86400 IN NS localhost.

;; ADDITIONAL SECTION:
localhost. 86400 IN A 127.0.0.1

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Feb 15 13:58:48 2003
;; MSG SIZE rcvd: 93

Demikian semoga dapat membantu rekan2 sekalian

kutipan : www.layangan.com/asfik/writings/dns-bind.html

Bir bilgisayara uzaktan ulasmak aslinda cok kolay. Yani evdeki bilgisayariniza isten, istekine tatilden, vs. Benim de bu sistemi kullanmaktaki amacim yazilarimin farkli bilgisayarlarda olusan gereksiz kopyalarini yok etmek ve mesela hangi yazinin nerdeki hali daha güncel probleminden kurtulmak. Bir nevi GoogleDocs’un bircok kisi arasinda gidip gelen dökümanlara getirdigi kolayligi ben kendime getiriyorum.

Öncelikle kisa tanimlarla baslayalim. Kullanacagimiz programin adi OpenSSH.

I. Peki, OpenSSH nedir?

SSH ya da Secure Shell ag (yerel veya internet) üzerinden birbirine bagli iki bilgisayar arasindaki veri alisverisi icin gerekli baglantiyi saglar.  Telnet veya Rlogin gibi ayni islevi gören programlardan daha güvenli sayilmasinin da nedeni, makineler arasinda degis tokus edilmis bilgileri sifrelenmis olarak saklamasidir.

OpenSSH‘de SSH’nin acik kaynak implementasyonudur ve OpenBSD’nin gelistiricileri tarafindan olusturulmustur. Her ne kadar daha sonra depodan yüklerden terminale “ssh” de yazacak olsak yüklenecek program aslinda OpenSSH.

II. OpenSSH Kurulumu ve Kullanimi

$ sudo aptitude install ssh

bu kadar. “ssh” üst paketi (meta package) client ve server icin gerekli her seyi bilgisayara yükledi. Bundan sonrasi onun nasil kullanilacagini bilinmesine kaliyor. Unutulmamasi gereken sey diger bilgisayarda da bu paketin yüklü olmasi gerekliligi.

$ ssh uzak_pc’deki_kullanici_adi@sunucu_ismi (örn. $ ssh debiantr@debian-sid)

Teoride bu böyle ama ben kullanici ismi yerine ip numarasi kullaniyorum, yani

$ ssh kullanici_adi@192.168.2.101 gibi.

Yalniz burdaki sorun 192.168.2.101 gibi ip’lerin yerel aglarda bulunmasi ve yerel aglarda genellikle ip’lerin degismemesi. Eger yerel agda degilseniz ve uzaktaki bilgisayara internet üzerinden erismek istiyorsaniz o zaman bilgisayarin statik bir ip’ye ihtiyaci var. Bu da genelde görülen bir sey degil. Bilgisayarlarin ip adresleri bir sekilde hep degisiyor. Modem yeniden baslatiliyor, sorunlar cikiyor, vs. Bu yüzden DNS kullanmak mantikli yani basitce bir web adresi almak mantikli olan. DynDns.com ip’lere bedava isim atayabileceginiz bir hizmet. DynDNS.com’da bir hesap olusturduktan sonra “Free Dynamic DNS” bölümünden kendinize istediginiz ismi alin: debiantr.homelinux.com, besiktas1903.dyndns.biz gibi. Ismi aldiktan sonra da simdiki ip adresinizi atayin, zaten otomatik olarak gösterecek adresinizi size. Sonra terminale dönüp:

$ sudo aptitude install ddclient

Bu uygulama degisen ip’nizi “web adresi”nizle güncel tutacak. Kurulum sirasinda karsiniza bir sihirbaz cikacak burda ilk soruda
www.dyndns.com deyin, sonra hesabinizin kullanici adi ve sifresini girin,
ip adresinizi bulmasi icin kullanilacak servise “yes”,
web sitenizin ismini listeden bulmasina “yes”,
PPP connect?’e “yes”,
“ddclient as deamon”a “yes” deyin, bu sayede her bilgisayar acildiginda bu uygulama da baslayacak
programin ne kadar zaman adresi kontrol etmesini istediginizi girin, ve son olarak listedeki adresi “space” (bosluk) tusu ile secin.

Arkasindan /etc/ddclient.conf dosyasini acin

$ sudo gedit /etc/ddclient.conf

use=if, if=debiantr.homelinux.com

satirini silip o satira sadece

use=web

(burdaki amac ddclient’in network kartinin yerel adresini kullanmasi yerine internet üzerinde yayimlanan adresinizi kullanmasini saglamak.)

yazin, kayedip cikin. Sonra $sudo ddclient dediginizde sorunsuz olarak adresiniz güncellenmis olmasi lazim.
Son yapilmasi gereken seyde ulasilmak istenen bilgisayarin router’inin 22 numarali TCP ve UDP portlarini acmak. Cünkü ssh’nin varsayilan kullandigi port 22. “Port forwarding” yapmayi bilmiyorsaniz Portforward.com‘a bir bakin.

“ddclient” disinda baska alternatifler de var. Bunlardan bir tanesi yine bir ip güncelleme programi ve debian depolarinda olan “inadyn”. Ancak bunun kullanimina burada deginmeyecegim. Baska bir alternatif ise, benim kullandigim, direkt router’in dns adresi kullanmasini saglamak. Her router bu servisi desteklemiyor, ancak destekleyen routerlarda sadece DynDns hesabinizin ismini, sifresini ve kullanmak istediginiz web adresini girip router’in ip’nizi güncellemesini saglayabilirsiniz.

Artik uzaktaki bir bilgisayara ya da sunucuya ulasmak icin yapmaniz gereken tek sey

$ ssh kullanici_adi@aldiginiz_adres.dyndns.com

ssh ayni zamanda opsiyonlar da aliyor bunlardan bir tanesi -X, eger uzaktaki alete

$ ssh -X kullanici_adi@aldiginiz_adres.dyndns.com

diye baglanirsaniz ve baglandiktan sonra terminalde $ iceweasel www.google.com yazarsaniz iceweasel uzaktaki bilgisayarda calisip Google’a baglanmis olacak ama siz onu kendi ekraninizda göreceksiniz. Ofis programlarini böyle calistirarak, islemi uzaktaki bilgisayarda yapmis olacak ama programin resmini ve yaptiklarinizi o an kullandiginiz bilgisayarda görmüs olacaksiniz.

III. SSH’de Dosya Kopyalama

$ scp kullanici_adi@aldiginiz_adres.dyndns.com:/dosyanin/yeri/dosyanin_ismi uzaktaki_pc@adresi.dyndns.com:/kopyalanan/yer/dosyanin_ismi

eger kopyalanacak sey klasörse “scp -r” yazin sonra ayni sekilde devam edin. “-r” takisi recursive anlamina gelmekte ve klasörün icindeki her dosya kopyalanana kadar islemin devam etmesini saglamaktadir.

IV. SSH’de Sifreyi Kaldirmak

Uzaktaki bilgisayariniza veya sunucuya baglandiginiz bilgisayar gercekten güvenliyse (örn. sizden baskasi kullanmiyorsa) iki de bir sifre yazimini ortadan kaldirabilirsiniz.  Yani iki bilgisayari birbilerine güvenebilir hale getirebilirisiniz. “ssh-keygen” burda kullanacagimiz program. Öncelikle

$ ssh-keygen -t rsa (veya dsa) -t sifreleme (encryption) tipini belirten bir etiket ve rsa ile dsa sifreleme tiplerinden bazilari. Cikan ilk soru dosya ismi ona direkt bir sey yazmadan (ya da yazin siz bilirsiniz) enter’a basin sonra da gercekten güvenli oldugunu düsündügünüz bir sifre verin. Sonra yapilmasi gereken sey yaratilmis dosyanin uzaktaki bilgisayara/sunucuya kopyalanmasi. Varsayilan ayarlara göre:

$ cd /home/kullanici_adi/.ssh

$ su

# scp id_rsa/dsa.pub uzaktaki_bilgisayar:~/.ssh/authorized_keys, yalniz dikkat edilmesi gerekn nokta önceden olusturulmus bir “authorized_keys” dosyasinin olmamasi, eger varsa bu sekilde önceden verilmis bilgiler silinir. Öyle bir durumda sifrelenmis dosya önce kendi uzantisiyla kopyalanir:
# scp id_rsa/dsa.pub uzaktaki_bilgisayar:~/.ssh/simdiki_bilgisayarin_ismi.pub
# cat bilgisayarin_simdiki_ismi.pub >> authorized_key bu gerekli bilgileri authrized_keys’in icine kopyalar.

V. SSH Portunu Degistirmek

Daha önce de söyledigim gibi 22 ssh’nin varsayilan portu. Bu yüzden bircok hacker(!) burdan bu portu acik olan bilgisayarlara girmeye calisiyor. Bir sunucuyu ya da pc’yi korumanin bircok yolu var ancak portu degistirmek de bence cok etkili bir yöntem, cünkü karsi tarafin kullandiginiz portu arayacagina 22′yi kullananlara yönelmesini saglayabilirsiniz.

$ sudo nano /etc/ssh/sshd_config yaptignizda karsiniza cikan sayfada asagidai satirlari bulun

# What ports, IPs and protocols we listen for
Port 22

ve buraya istediginiz bir port numarasini (tabi baska bir programla cakismayacak) ekleyin. Örn. 1903.

# What ports, IPs and protocols we listen for
Port 22
Port 1903

Burda Port 22′yi silmedim. Böylece ssh’yi iki portu dinleyecek sekilde ayarlamis oldum, eger 22′den direkt kurtulmak isterseniz dogrudan 22 yerinde 1903 yazin, kaydedin ve cikin.

Önceden belirttigim gibi 22 varsayilan port numarasi oldugu icin $ssh uzaktaki@pc seklinde yapilan denemelerde Port 22 kullanilmaya calisilacak, 1903′ten girmek icin -p takisinin kullanilmasi gerek. Bu taki hangi portun kullanilacagini gösteriyor.

$ssh uzaktaki@pc -p 1903 gibi.

Rekan-rekan Warnet dan Masyarat IT Indonesia, Tim DNS Awari / Nawala Project saat ini sudah mengaktifkan dua server untuk melayani kepentingan layanan DNS Filter. Bagi warnet dan masyarakat yang ingin menggunakan layanan ini silahkan mengubah setting DNS server ke:

* 203.34.118.10 (primary)
* 203.34.118.12 (secondary)

Petunjuk Penggunaan untuk berbagai sistem:

* MS Windows
* Apple Mac
* Linux dan ADSL/DSL Modem

Dapat di unduh di http://awari.or.id/docs/

Selamat menikmati kehidupan internet yang lebih bersih dan aman
sumber : www.nawala.org

Late last night I received a SCOM alert indicating that a production database server was unavailable. Like any dedicated DBA I quickly remoted into my work computer and attempted to connect to the instance using SSMS. No dice. “Login failed. This user is not associated with a trusted connection” or something like that. I also noticed that Outlook was prompting me for credentials since I left it running at the end of that work day.

I figured there was some sort of network blip that caused the Outlook authentication prompt and was also somehow responsible for the inability to connect to the instance using SSMS. I tried to remote desktop to the database server and noticed a serious delay as it tried to process my credentials. And yes, I was incredibly relieved at this point since the database server was at least up and running.

While waiting for the desktop to appear I started poking around the network and noticed that one of our many DNS servers was unavailable. Our standard practice is to have a backup DNS entry on all servers and workstations. Somehow this guy slipped through the cracks because when I finally got to the desktop and was able to view the network settings, I saw that the only DNS entry on the main network card for this server was, of course, the DNS server that crashed.

Why am I talking about DNS issues on a SQL blog? Besides the fact that it’s good to be well-rounded when it comes to troubleshooting, I learned something last night. Well, maybe I already knew it but never thought about it until this issue arose. During this mini outage I checked the primary application that talks to that instance and it was running smoothly. No funky errors about not being able to connect to the database. No timeouts. It just worked. It turns out that the application uses SQL authentication rather than Windows authentication to connect to the database. For this reason, the application connectivity was unaffected by the DNS server going down.

I verified this by trying to connect to the instance, via SSMS, using SQL authentication. In there like swimwear. So I guess the lesson to be had here is if you rely solely on Windows authentication for your applications to connect to your SQL database, make sure you have A. a backup DNS server and B. an entry for it in your DNS settings on the database server.

Hope this helps someone.

- Κάποτε, μπορούσαμε να στείλουμε mail μέσω του sendmail που έτρεχε κάποιος άλλος, μόνο και μόνο για να παρακάμψουμε routing problems, πχ. dimitris%hypernet.hyper.gr@info.forthnet.gr.
- Τώρα δε μπορούμε, οι mail servers αυτοί ονομάστηκαν open relays και χρησιμοποιήθηκαν για να στέλνουν spam..

- Κάποτε, μπορούσαμε να χρησιμοποιήσουμε το DNS που έτρεχε κάποιος άλλος, ακόμα κι αλλάζαμε providers..
- Τώρα δε μπορούμε, γιατί χρησιμοποιήθηκαν σε “reflector attacks” και όχι μόνο recursion, αλλά ούτε καν την cache τους δε μας δείχνουν..

- Κάποτε, μπορούσαμε να κάνουμε zone tranfers ελεύθερα, και να βγάλουμε στατιστικά με το Xray που έκανε ο @kangelos για το .GR domain και τους top hosting providers.
- Τώρα πια δε μπορούμε, και το μόνο που μπορούμε να γνωρίζουμε για το .GR TLD είναι ότι πλέον έχει ξεπεράσει τα 290.000 domains (από επιστολή της ΕΕΤΤ προς το @papaki).

(triggered-by)

Ενδιαφέροντα στατιστικά για το DNS σήμερα, εμφανίζονται στο October 2009 DNS Survey (sponsored by Infoblox).

Khắc phục lỗi không vào được Facebook

Fix DNS để vào được Facebook

Rất nhiều bạn dùng Internet (đặc biệt là của Viettel) không thể vào Facebook. Nhiều người hoang mang, cho rằng sự cố này là do các ISP chặn Facebook để tạo điều kiện cho mạng xã hội VN “phát triển”. Tuy nhiên, đây là lỗi DNS chả liên quan gì việc chặn nào cả !

Đơn giản là sử dụng OpenDNS : http://tangtocnet.com/index.php?showtopic=67

Hoặc Toonel : http://tangtocnet.com/index.php?showtopic=48

What does DNS or Domain Name Refer To? Find out more – http://ping.fm/PC16F