As others have already commented, it could mean either, there isn't enough information provided to try to identify where the fault lies.
Are these systems accessible from the Internet? if so then please provide the correct names so we can also run tests from our locations to see if we get the same results. If you can't provide this information then you are on your own to solve your own problem. Steve On 3 October 2013 05:56, Balanagaraju Munukutla <9ba...@sg.ibm.com> wrote: > > Hi All > > To explain more on the below. We are trying to do a query on MX record for > abcd.com.sg. domain to the Authoritative nameserver xxxx.com from my pc. > You can see the reply as below. Done this mean that the Authoritative > nameserver xxxx.com failure or this PC where I am doing the query is > blocking to communicate that local DNS server configured on it. > > Please help. > > Thanks & Regards > Nagaraj > > > > > > *Kevin Oberman <rkober...@gmail.com>* > Sent by: kob6...@gmail.com > > 10/03/2013 12:47 PM > To > Balanagaraju Munukutla/Singapore/AT&T/IDE@IBMSG > cc > bind-users <bind-us...@isc.org>, Subramaniam Raju <subrr...@in.ibm.com> > Subject > Re: Dig gives ;; connection timed out; no servers could be reached > > > > > On Wed, Oct 2, 2013 at 9:18 PM, Balanagaraju Munukutla <*9ba...@sg.ibm.com > * <9ba...@sg.ibm.com>> wrote: > > Hi > > Any one could help on the error below. > > > [andrew@oc8163211842 ~] $ dig @*xxxx.com* <http://xxxx.com/> > *abcd.com.sg*<http://abcd.com.sg/>mx > > ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> > @*xxxxx.com*<http://xxxxx.com/> > *abcd.com.sg* <http://abcd.com.sg/> mx > ; (1 server found) > ;; global options: printcmd > ;;* connection timed out; no servers could be reached* > > [andrew@oc8163211842 ~]$ dig @*xxxx.com* <http://xxxx.com/> > *abcd.com.sg*<http://abcd.com.sg/>mx > > ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> > @*xxxxx.com*<http://xxxxx.com/> > *abcd.com.sg* <http://abcd.com.sg/> mx > ; (1 server found) > ;; global options: printcmd > ;; *connection timed out; no servers could be reached* > --------------------------- > > Thanks & Regards > Nagaraj > > This message is virtually content free. You basically said "Something in > DNS failed at a very basic level, but I will remove any information that > might provide even a slight clue to determine why." You hide the query and > the server. All that can really be said is that your client failed to get a > response from the specified server. > > Is the specified system even running DNS? Is a firewall blocking the > query? The response? Is the server yours or someone else's? Is routing > allowing bi-directional communication? Is these an outage that is blocking > communication? The list of possibilities just goes on and on. > > If you want help, you have to tell us something more than that it failed. > -- > R. Kevin Oberman, Network Engineer > E-mail: *rkober...@gmail.com* <rkober...@gmail.com> > > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users >
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
