dns server

Unbound 1.0 is a recursive DNS server as well as recursive, and caching DNS resolver.

{ 0 comments }

DNS server can be attacked using various techniques such as [a] DNS spoofing [b] Cache poisoning [c] Registration hijacking One of the simplest ways to defend is limit zone transfers between nameservers by defining ACL. I see many admin allows BIND to transfer zones in bulk outside their network or organization. There is no need […]

{ 3 comments }

One of my client runs dedicated NS1 and NS2 to host more than 3000+ domains. Recently they upgraded their servers to latest Dual Core Dual AMD server with CentOS 5.0 and BIND server. By default BIND / named will try to determine the number of CPUs present and create one thread per CPU. If it […]

{ 0 comments }

I am getting error that read as No Route to Host. I am trying to ping my ISP gateway as well as DNS server but I am getting this error. How do I solve this problem? This problem indicate networking conflicts or some sort of networking configuration problem. Here are things to check: Can you […]

{ 27 comments }

One of my friend recently send me an email. It reads as follows: “…My DSL service providers DNS server seems to be little slow, they have two servers it takes little time (some time upto 2 seconds) to resolve a domain name, once domain resolved, browsing speed remains the same, what should I do to […]

{ 7 comments }

BIND is the Berkeley Internet Name Domain, DNS server. It is wildly used on UNIX and Linux like oses. You can use following tools to troubleshoot bind related problems under UNIX or Linux oses. Task: Port 53 open and listing requests By default BIND listen DNS queries on port 53. So make sure port 53 […]

{ 14 comments }