Hi all,
Thank you for you efforts on this.
I would like to give you all a few details of the problems with my DNS
I had response from yahoo postmaster
and he forwarded the problem to the systems manager.
The system manager pointed out that my ISP's DNS was defective.
I am greateful for the help he has given in this connection,
and think some of the info he gave may be useful to some of you.
below are some snips from his emails
Jacob (Mettavihari)
-----------------------------
> Kindly put an DNS enty in your server
> so that your customers can send email to us.
No. We are the DNS client. You have the DNS server.
Kindly put a DNS entry in your DNS server so that our customers
can send email to you.
Your delegation is 50% unusable.
% dig any metta.lk @PENDRAGON.CS.PURDUE.EDU
; <<>> DiG 2.1 <<>> any metta.lk @PENDRAGON.CS.PURDUE.EDU
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd ra; Ques: 1, Ans: 2, Auth: 2, Addit: 1
;; QUESTIONS:
;; metta.lk, type = ANY, class = IN
;; ANSWERS:
metta.lk. 604800 NS server1.tradenetsl.lk.
metta.lk. 604800 NS edb.tradenesl.lk.
;; AUTHORITY RECORDS:
metta.lk. 604800 NS server1.tradenetsl.lk.
metta.lk. 604800 NS edb.tradenesl.lk.
;; ADDITIONAL RECORDS:
server1.tradenetsl.lk. 604800 A 204.143.107.34
;; Total query time: 105 msec
;; FROM: ns.yahoo.com to SERVER: PENDRAGON.CS.PURDUE.EDU 128.10.2.5
;; WHEN: Fri May 28 14:26:11 1999
;; MSG SIZE sent: 26 rcvd: 133
% dig any tradenesl.lk @PENDRAGON.CS.PURDUE.EDU
; <<>> DiG 2.1 <<>> any tradenesl.lk @PENDRAGON.CS.PURDUE.EDU
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10
;; flags: qr aa rd ra; Ques: 1, Ans: 0, Auth: 1, Addit: 0
;; QUESTIONS:
;; tradenesl.lk, type = ANY, class = IN
;; AUTHORITY RECORDS:
lk. 604800 SOA ns.nic.lk. hostmaster.nic.lk. (
219060 ; serial
43200 ; refresh (12 hours)
14400 ; retry (4 hours)
2592000 ; expire (30 days)
604800 ) ; minimum (7 days)
;; Total query time: 114 msec
;; FROM: ns.yahoo.com to SERVER: PENDRAGON.CS.PURDUE.EDU 128.10.2.5
;; WHEN: Fri May 28 14:23:28 1999
;; MSG SIZE sent: 30 rcvd: 86
The one remaining nameserver lists an unusable NS-set and an
unusable MX record, which qmail correctly complains about.
% dig any metta.lk @server1.tradenetsl.lk
; <<>> DiG 2.1 <<>> any metta.lk @server1.tradenetsl.lk
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr aa rd ra; Ques: 1, Ans: 4, Auth: 1, Addit: 0
;; QUESTIONS:
;; metta.lk, type = ANY, class = IN
;; ANSWERS:
metta.lk. 86400 NS 204.143.107.34.
metta.lk. 86400 SOA dhamma.metta.lk. root.metta.lk. (
1 ; serial
28800 ; refresh (8 hours)
7200 ; retry (2 hours)
604800 ; expire (7 days)
86400 ) ; minimum (1 day)
metta.lk. 86400 A 204.143.107.46
metta.lk. 86400 MX 10 204.143.107.46.
;; AUTHORITY RECORDS:
metta.lk. 86400 NS 204.143.107.34.
;; Total query time: 612 msec
;; FROM: ns.yahoo.com to SERVER: server1.tradenetsl.lk 204.143.107.34
;; WHEN: Fri May 28 14:27:09 1999
;; MSG SIZE sent: 26 rcvd: 162
This DNS response has the wrong number of NS records. It lists one NS.
Section 4.1 of RFC 1034 requires a minimum of two NS records.
The "metta.lk. 86400 NS 204.143.107.34." record is unusable because "34"
is not a TLD (lk, net, org, & com are TLDs) and because it does not conform
to section of 3.3.9 of the DNS spec. A <domain-name> must be a name in
the domain name system. There is no "107" subdomain of "34" in the DNS.
The "metta.lk. 86400 MX 10 204.143.107.46." record is similarly unusable.
"46" is not a Top Level Domain, and the MX record must list a <domain-name>.
RFC 1035 Domain Implementation and Specification November 1987
3.3.9. MX RDATA format
EXCHANGE A <domain-name> which specifies a host willing to act as
a mail exchange for the owner name.
MX records cause type A additional section processing for the host
specified by EXCHANGE. The use of MX RRs is explained in detail in
[RFC-974].
3.3.11. NS RDATA format
NSDNAME A <domain-name> which specifies a host which should be
authoritative for the specified class and domain.
NS records cause both the usual additional section processing to locate
a type A record, and, when used in a referral, a special search of the
zone in which they reside for glue information.
Please notify me when you have repaired your nameservers.
Thank you.
Cheers
jh
---------------------------------------------------
from:yahoo after a few corrections
==========
An NS record may not contain a numeric dotted-quad IP, like 204.143.107.34.
An NS record must contain a domain name, like server1.tradenetsl.lk.
I wasn't trying to convince you to get "34" added as a TLD; I was trying to
point out that it is not a TLD and never will be, while "lk" and "com" are.
So instead of
metta.lk. NS 204.143.107.34.
metta.lk. NS 204.143.96.17.
you want
metta.lk. NS server1.tradenetsl.lk.
metta.lk. NS lakdiva.slt.lk.
But don't include lakdiva in your NS-set until it is configured
to secondary metta.lk. That is, it should regularly zone transfer
the metta.lk data and store it on disk, so it can hand out DNS
answers even when it doesn't have network connectivity to you.
Currently, it is not configured to do that.
Be sure to ask <[EMAIL PROTECTED]> to delete the edb.tradenesl.lk
glue record, if you can't get a proper A-record (IP address)
associated with that name. Currently there isn't one, so the
name edb.tradenesl.lk is unusable.
If you do want edb.tradenesl.lk in your NS-set, be sure that it is
configured to secondary metta.lk. That is, it should regularly zone
transfer the metta.lk data and store it on disk.
When you're done, ns.nic.lk and server1.tradenetsl.lk should
hand out the identical NS-set; that is called "glue agreement".
Here is the instruction manual that comes with your name daemon:
http://www.ora.com/catalog/dns3/
Cheers
jh
-------------------------------------
