Hi,
Querying the root servers for .sz reveals some problems:
a. ns.ripe.net which is listed as a root server for .sz does not serve the
.sz ccTLD
dig +norec @NS.RIPE.NET. sz. ns
; <<>> DiG 8.3 <<>> +norec @NS.RIPE.NET. sz. ns
; (2 servers found)
;; res options: init defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 13438
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;; sz, type = NS, class = IN
b. rip.psg.com and NS-SZ.RIPE.NET. have different Serials from
DNS.SISPA.ORG.sz as of this moment. This might not be a problem if you
have recently updated the primary which I suppose is DNS.SISPA.ORG.sz.
The secondaries should transfer the sz. zone file which reflects correct
records and changes to the skpe.co.sz which was deleted.
Otherwise both rip.psg.com and NS-SZ.RIPE.NET still have records for
skpe.co.sz because of the above reason.
dig +norec @rip.psg.com. skpe.co.sz ns
; <<>> DiG 8.3 <<>> +norec @rip.psg.com. skpe.co.sz ns
; (1 server found)
;; res options: init defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28803
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; QUERY SECTION:
;; skpe.co.sz, type = NS, class = IN
;; AUTHORITY SECTION:
skpe.co.sz. 4H IN NS ns.africaonline.co.sz.
skpe.co.sz. 4H IN NS ns2.africaonline.co.sz.
**Technically ns.africaonline.co.sz. & ns2.africaonline.co.sz. are lame
for the domain skpe.co.sz. since according to the secondary root servers,
the domain has been delegated to them and yet that domain is no longer
being served by your nameservers.
To solve this, make sure that the secondary nameservers for the sz. ccTLD
transfer the updated zone file from the primary nameserver which as of now
has correct information.
--
Joseph
On Sat, 21 Oct 2006, Gcinaphi Nqobile Maseko wrote:
Good day All,
On my /var/log/messages I've got, lame server resolving, 'skpe.co.sz'
almost
every other second. This is filling up our NS logs and sending queries
to
our .sz TLD server. We once hosted this domain a year ago and their
owners
ceased using it. All records for this domain were deleted. Why would our
NSes
continue to query this domain. What would be the effects of disabling
lame
server resolving?
_______________________________________________
LUG mailing list
[email protected]
http://kym.net/mailman/listinfo/lug
%LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
The above comments and data are owned by whoever posted them (including
attachments if any). The List's Host is not responsible for them in any way.
---------------------------------------
