> I tried: nslookup sripelangi.com (default DNS server 220.127.116.11)
The dns entries for sripelangi.com are messed up. The first time
a name server does a lookup, it will use the glue records in the
root servers, to find it.
$ whois sripelangi.com|grep "Name Server"
Name Server: NS101.MSCHOSTING.COM
Name Server: NS102.MSCHOSTING.COM
$ dig -4 +trace sripelangi.com any
sripelangi.com. 172800 IN NS ns101.mschosting.com.
sripelangi.com. 172800 IN NS ns102.mschosting.com.
;; Received 115 bytes from 18.104.22.168#53(k.gtld-servers.net) in 137 ms
sripelangi.com. 14400 IN MX 0 sripelangi.com.
sripelangi.com. 86400 IN SOA ns1.my-rialto.com.
ssleng.ec-partners.com. 2010031900 86400 7200 3600000 86400
sripelangi.com. 86400 IN NS ns1.my-rialto.com.
sripelangi.com. 86400 IN NS ns2.my-rialto.com.
sripelangi.com. 14400 IN A 22.214.171.124
The primary master server (ns1.my-rialto.com), does not exist,
so when the A record expires after 14400 seconds (4 hours),
the attempt to refresh the A record from ns1.my-rialto.com will
fail. It will continue to fail until the SOA record gets purged
from that name servers cache, which will happen after 86400 seconds
I would expect the site to only be accessible, for 4 hours per day,
given the above errors, unless you change name servers. Whoever
maintains the dns for sripelangi.com should fix the name server in
the SOA record.
Regards, Dave Hodgins
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)