On Sun, Aug 11, 2002 at 04:55:18AM -0600, [EMAIL PROTECTED] wrote: > >Seems OK now - after your DNS changes propogate. > > Yeah, now its working. But this problem is very strange.
I wouldn't call it "working"... There are still (minor) issues: dig swatee.com ns ;; ANSWER SECTION: swatee.com. 96635 IN NS SERVER.swatee.com. swatee.com. 96635 IN NS SERVER.MX-SOLUTIONS.CO.IN. swatee.com. 96635 IN NS SERVER2.MX-SOLUTIONS.com. dig @SERVER.swatee.com. swatee.com mx ;; ANSWER SECTION: swatee.com. 3600 IN MX 0 server.mx-solutions.co.in. dig @SERVER.MX-SOLUTIONS.CO.IN. swatee.com mx ;; ANSWER SECTION: swatee.com. 86400 IN MX 10 server.mx-solutions.co.in. dig @SERVER2.MX-SOLUTIONS.com. swatee.com mx ;; ANSWER SECTION: swatee.com. 25300 IN MX 10 server.mx-solutions.co.in. Look at that: The priority and the TTL are different when you use different name servers that claim to host the SOA for swatee.com. Though this would not cause any loss of functionality, it is still indicative of misconfiguration (for example, do the SOA records advertised by these three name servers match?); I suggest you keep one of the three as the master DNS server for swatee.com and let the other two perform DNS zone transfers from it. Binand -- If you found this helpful, please take some time off to rate it: http://svcs.affero.net/rm.php?r=binand ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
