DNS propagation time

[James Griffin]

those who know me have no need of my name wrote:
> 
> in comp.protocols.dns.bind i read:
> 
> >May I make use of this opportunity to have mine tested instead
> >my domain is   http://bps.lk
> 
> no, your domain is `bps.lk'.
> 
> >I am told that it is not yet up, but I should think that it is working.
> >It should take you to the web-page of 203.115.29.130 (metta.lk)
> >It is of-cause working within my network.
> 
> it appears to be working.  a quick check of a few large providers all
> provide the same answers.
> 

'doc' reports an error.
Doc-2.2.3: doc -v bps.lk.
Doc-2.2.3: Starting test of bps.lk.   parent is lk.
Doc-2.2.3: Test date - Sat Aug 31 16:18:55 EDT 2002
soa @ns.eu.net. for lk. has serial: 300372
soa @ns.nic.lk. for lk. has serial: 300372
soa @pendragon.cs.purdue.edu. for lk. has serial: 300372
SOA serial #'s agree for lk. domain
Found 2 NS and 0 glue records for bps.lk. @ns.eu.net. (non-AUTH)
Found 2 NS and 2 glue records for bps.lk. @ns.nic.lk. (non-AUTH)
Found 2 NS and 0 glue records for bps.lk. @pendragon.cs.purdue.edu.
(non-AUTH)
DNServers for lk.
   === 0 were also authoritatve for bps.lk.
   === 3 were non-authoritative for bps.lk.
Servers for lk. (not also authoritative for bps.lk.)
   === agree on NS records for bps.lk.
NS list summary for bps.lk. from parent (lk.) servers
  == ns1.secondary.com. ns2.secondary.com.
soa @ns1.secondary.com. for bps.lk. serial: 2002092605
soa @ns2.secondary.com. for bps.lk. serial: 2002092605
SOA serial #'s agree for bps.lk.
Authoritative domain (bps.lk.) servers agree on NS for bps.lk.
ERROR: NS list from bps.lk. authoritative servers does not
  === match NS list from parent (lk.) servers
NS list summary for bps.lk. from authoritative servers
  == dhamma.metta.lk. ns1.secondary.com. ns2.secondary.com.
Checking 0 potential addresses for hosts at bps.lk.
  ==
Summary:
   ERRORS found for bps.lk. (count: 1)
Done testing bps.lk.  Sat Aug 31 16:20:13 EDT 2002

Do you intend that dhamma.metta.lk. be a "hidden master"?

The SOA lists a MNAME which is not a name server and has bad email
address.

$ dig +short bps.lk. soa
bps.lk. root.dhamma.metta.lk. 2002092605 3600 900 1209600 43200
^MANME^ -----^^^^^^^^^^^^^^^^ Not a domain either as an MX or A record

; <<>> DiG 9.2.1 <<>> dhamma.bps.lk. mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1092
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;dhamma.bps.lk.                 IN      MX

and
; <<>> DiG 9.2.1 <<>> dhamma.bps.lk.
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39598
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;dhamma.bps.lk.                 IN      A

There is no reverse zone.

$ dig +short bps.lk.
203.115.29.130


; <<>> DiG 9.2.1 <<>> -x 203.115.29.130
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46094
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

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

;; AUTHORITY SECTION:
29.115.203.in-addr.arpa. 10551  IN      SOA     ns1.slt.lk.
postmaster.slt.lk. 2000062600 10800 3600 864000 86400

Hope this helps.

Regards,
Jim