> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @x.com abcd.com.sg mx
> ; (1 server found)
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
> [andrew@oc8163211842 ~]$ dig @.com abcd.com.sg mx
>
&
On Wed, Oct 2, 2013 at 9:56 PM, 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 .com from my pc.
> You can see the reply as below. Done this mean tha
t.
>
> Please help.
>
> Thanks & Regards
> Nagaraj
>
>
>
>
>
> *Kevin Oberman *
> Sent by: kob6...@gmail.com
>
> 10/03/2013 12:47 PM
> To
> Balanagaraju Munukutla/Singapore/AT&T/IDE@IBMSG
> cc
> bind-users , Subramaniam Raju
> Subj
nnection timed out; no servers could be reached
On Wed, Oct 2, 2013 at 9:18 PM, Balanagaraju Munukutla <9ba...@sg.ibm.com>
wrote:
Hi
Any one could help on the error below.
[andrew@oc8163211842 ~] $ dig @.com abcd.com.sg mx
; <<>> DiG 9.3.6-P1-RedHat-9.3.6
lt;>> @x.com abcd.com.sg mx
> ; (1 server found)
> ;; global options: printcmd
> ;;* connection timed out; no servers could be reached*
>
> [andrew@oc8163211842 ~]$ dig @.com abcd.com.sg mx
>
> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @xxxxx
@x.com abcd.com.sg mx
> ; (1 server found)
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
Yes, it means the nameserver at .com could not be reached.
FYI, that version of dig (and presumably BIND) was deprecated back in 2009:
https://www.isc.org/
options: printcmd
> ;; connection timed out; no servers could be reached
Looks like the connection is timing out to me. Maybe no servers could be
reached.
Check the logs on the server (x.com).
Note that it times out for me as well:
SNIP
aclegg@ossatura ~ $ dig @.com
Hi
Any one could help on the error below.
[andrew@oc8163211842 ~] $ dig @.com abcd.com.sg mx
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @x.com abcd.com.sg mx
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers co
On Jul 28, 2011, at 8:27 AM, uifid...@gmail.com wrote:
> I'm trying to config a bind server which could answering queries (at
> least from 127.0.0.1 and 192.168.18.128) like "dig kia.czj" but I
> failed to. perhaps my ignorance about match-clients and
> match-destinations statements failed my att
On Jul 28, 2011, at 4:39 AM, Daniel McDonald wrote:
> On 7/28/11 3:16 AM, "uifid...@gmail.com" wrote:
>
>> my czj.zone
>> $TTL 86400
>> czj. IN SOA localhost. root.localhost. (
>> 1997022700 ; Serial
>> 2880
>
> -Original Message-
> From: bind-users-bounces+jlightner=water@lists.isc.org
> [mailto:bind-users-bounces+jlightner=water....@lists.isc.org] On Behalf Of
> Danilo Godec
> Sent: Friday, July 29, 2011 5:38 AM
> To: bind-users@lists.isc.org
> Subject: Re: no servers
On Behalf Of
Danilo Godec
Sent: Friday, July 29, 2011 5:38 AM
To: bind-users@lists.isc.org
Subject: Re: no servers could be reached
On 07/29/2011 10:36 AM, uifid...@gmail.com wrote:
> the zones file is located at /var/named/chroot/var/named/domainx.zones.
> #cat var/domainx.zone
On 07/29/2011 10:36 AM, uifid...@gmail.com wrote:
the zones file is located at /var/named/chroot/var/named/domainx.zones.
#cat var/domainx.zones should be var/named/domainx.zones
#cat var/domainx.zone should be var/named/domain.zone
Sorry for my typo.
So this should be OK then.
Your view state
the zones file is located at /var/named/chroot/var/named/domainx.zones.
#cat var/domainx.zones should be var/named/domainx.zones
#cat var/domainx.zone should be var/named/domain.zone
Sorry for my typo.
2011/7/29 Danilo Godec :
> On 07/29/2011 08:17 AM, uifid...@gmail.com wrote:
>>
>> cat var/named
On 07/29/2011 08:17 AM, uifid...@gmail.com wrote:
cat var/named/named.conf
//
// named.caching-nameserver.conf
//
options {
listen-on port 53 { 192.168.18.128; 127.0.0.1; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/da
#hostname
CentOS3
Is it matter?
2011/7/29 uifid...@gmail.com :
> still get "no servers could be reached", need help.
>
> #dig @127.0.0.1 nsc1.domainx
>
> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @127.0.0.1 nsc1.domainx.
> ; (1 server f
still get "no servers could be reached", need help.
#dig @127.0.0.1 nsc1.domainx
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @127.0.0.1 nsc1.domainx.
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
c
8)
>> ;; WHEN: Thu Jul 28 11:42:34 2011
>> ;; MSG SIZE rcvd: 45
>
>
> With resolv.conf in the wrong place:
>
>
>> Chickamin-River:~ $ mv /etc/resolv.conf /etc/resolv.conf.moved
>> Chickamin-River:~ $ dig www.isc.org
>>
>> ; <<>> DiG 9.6.0-APPLE
-users@lists.isc.org
Subject: Re: no servers could be reached
On 7/28/11 12:16 AM, uifid...@gmail.com wrote:
> my /etc/resolve.conf
Note: ^^^
>
> named-checkzone named-checkconf passed, I suppose the configure works
> but only get no servers could be reached.What's wrong with
cvd: 45
With resolv.conf in the wrong place:
Chickamin-River:~ $ mv /etc/resolv.conf /etc/resolv.conf.moved
Chickamin-River:~ $ dig www.isc.org
; <<>> DiG 9.6.0-APPLE-P2 <<>> www.isc.org
;; global options: +cmd
;; connection timed out; no servers could be reached
I'm trying to config a bind server which could answering queries (at
least from 127.0.0.1 and 192.168.18.128) like "dig kia.czj" but I
failed to. perhaps my ignorance about match-clients and
match-destinations statements failed my attempt, or more likely, "SOA
and NS of localhost. seems wrong". I
On 7/28/2011 4:16 AM, uifid...@gmail.com wrote:
> view localhost_resolver {
> match-clients { localhost; };
> match-destinations { localhost; };
> recursion yes;
> include "/etc/named.rfc1912.zones";
> };
> view czj {
> match-clients { 192.168.18.128; localhost
On 7/28/11 3:16 AM, "uifid...@gmail.com" wrote:
> my czj.zone
> $TTL 86400
> czj. IN SOA localhost. root.localhost. (
> 1997022700 ; Serial
> 28800 ; Refresh
>
dig kia.czj
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> kia.czj
;; global options: printcmd
;; connection timed out; no servers could be reached
my ip is 192.168.18.128
my named.conf
options {
listen-on port 53 { 192.168.18.128; 127.0.0.1; };
li
found what the problem is, i stop bind completely and re-run it again
and the hintlist worked again. bug? maybe I'm running OpenBSD 4.2 and
it's built-in bind server.
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listi
box
$ dig @1.1.1.11 www.yahoo.com
; <<>> DiG 9.3.4 <<>> @1.1.1.11 www.yahoo.com
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
both boxes sit on the same subnet, and they both have the same hints
file. no fw(pf) install
On Sat, 07 Mar 2009 22:03:14 -0500, R Dicaire faxed us with
> On Sat, Mar 7, 2009 at 8:44 PM, Bill Landry wrote:
>> I have to admit that I am a bit baffled by this one. =A0I can query
>> against my bandwidth providers name servers (Comcast) and get name
>> resolution just fine for the hostnam
On Sat, Mar 7, 2009 at 8:44 PM, Bill Landry wrote:
> I have to admit that I am a bit baffled by this one. I can query
> against my bandwidth providers name servers (Comcast) and get name
> resolution just fine for the hostname www.malware.com.br:
Check firewall settings. Connection timed out is
t-9.5.1-1.P1.fc10 <<>> www.malware.com.br
;; global options: printcmd
;; connection timed out; no servers could be reached
A tshark packet capture sees this:
1 3.362200 10.20.30.25 -> 192.228.79.201 DNS Standard query A
www.malware.com.br
2 3.405447 192.228.79.201 -> 10.20.30.
29 matches
Mail list logo
