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
nslookup www.tcs.co.in
Name: www.tcs.co.in Address: 198.36.215.160
at home i've configured BIND to resolve domains on its own. then there's my ISP's DNS (Primus AFAIK). i was not able to resolve "irayon.co.in" using both of them, however when i did
nslookup -sil irayon.co.in 202.56.230.5 Server: 202.56.230.5 Address: 202.56.230.5#53
Name: irayon.co.in Address: 203.200.181.162
it showed the desired result. that means if i send a mail to irayon.co.in, my nameserver would not be able to resolve the IP and hence will be unable to send it? doing a "dig mx irayon.co.in" also didn't show any results.
--
\|||/
(o o)
--------------------------------ooO-----(_)-Ooo-
| vivek | GPG Key: |
| [EMAIL PROTECTED] | http://exain.net/vike |
|------------------------------------------------|
| Registered Linux User: #305493 |
------------------------------------------------
( _ )
_| | | |_
(___| |___)
_______________________________________________ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
