<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<body text="#000000" bgcolor="#ffffff">
On 1/28/2011 5:11 AM, Torinthiel wrote:
<pre wrap="">Dnia 2011-01-28 10:52 bangla desh napisał(a):
<pre wrap="">I believed so that com.bd is broken. It only has 1 ns server and
<pre wrap="">hsbc.com.bd, whois.com.bd and even google.com.bd they are all delegate
directly from bd and not from com.bd.
I am wondering, is there a dns rule/standard (or RFC) that explains about
For the fact that com.bd is broken - that's just how DNS works. Zone cuts
are there for purpose. Most of this can be read from RFC 1034 and 1035,
which form the grounds for DNS standards. Also RFC 2181 clarifies:
A server for a zone should not return authoritative answers for queries
names in another zone, which includes the NS, and perhaps A, records
at a zone cut, unless it also happens to be a server for the other
And a mere presence of NS records indicates a zone cut (again, RFC 2181):
The existence of a zone cut is indicated in the parent zone by the
existence of NS records specifying the origin of the child zone.
As for number of authorative servers per domain, I don't remember where, but
at leas one RFC stated that there should be at least two, and preferably 3-7
nameservers per domain. It's quite possible that one of those I've already
pointed to contains this information, but also that a different one states
this information. But it was RFC for certain.
RFC 1034, Section 4.1:<br>
<blockquote>A given zone will be available from several name servers
to insure its
availability in spite of host or communication link failure. By
administrative fiat, we require every zone to be available on at
two servers, and many zones have more redundancy than that.