On Friday, May 30, 2003 1:24 PM [GMT+0800=SGT],
Tarun Dua <[EMAIL PROTECTED]> wrote:
> You don't need anything more to resolve the .co.in domains.
> Mostly its mis-configured DNS about which the ISP's DNS can't
> do much.
>
> nslookup tcs.co.in
> *** Can't find tcs.co.in: No answer
This is OK. By default, nslookup looks up A records, and tcs.co.in
does not have an A record. Perfectly OK.
> nslookup www.tcs.co.in
>
> Name: www.tcs.co.in
> Address: 198.36.215.160
Well, www.tcs.co.in is a host, so has an A record.
Try:
kansas:~# nslookup -type=soa -sil tcs.co.in
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
tcs.co.in
origin = ns.tcs.co.in
mail addr = helpdesk.mx.delhi.tcs.co.in
serial = 2001190730
refresh = 10800
retry = 3600
expire = 604800
minimum = 86400
Authoritative answers can be found from:
tcs.co.in nameserver = ns.tcs.co.in.
tcs.co.in nameserver = ns.mumbai.tcs.co.in.
tcs.co.in nameserver = gg2ns.tcs.co.in.
tcs.co.in nameserver = tcsnda.tcs.co.in.
ns.tcs.co.in internet address = 203.190.137.35
gg2ns.tcs.co.in internet address = 202.54.61.36
> So much for the clueless domain admins. There is no hope when
> our official whois registry doesn't run proper whois services.
--
Sanjeev
_______________________________________________
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd
