Re: resolving-problem

2013-07-23 Thread Liu Ganning
On 07/24/13 00:35, Shawn Bakhtiar wrote: Do you run your name servers from behind a firewall, or is your firewall (iptables) turned on? We run our name servers from behind a firewall, my network computers give the same problem when I run dig +trace www.fransiplus.com

Re: resolving-problem

2013-07-23 Thread Mark Andrews
In message , "Ejaz" writes: > > Thank you so much for your email and support, > > Pls, See, the dig + trace output when use ns1.nesma.net.sa, at the end it > say connection timedout. so please can you to find out the problem is from > where??? > > > [root@ns1 ~]# dig +trace www.fransiplus.

Re: resolving-problem

2013-07-23 Thread John Wingenbach
eing able to resolve the fransiplus.com <http://www.fransiplus.com/> from your PC From: me...@cyberia.net.sa To: sjc...@gmail.com Subject: RE: resolving-problem Date: Tue, 23 Jul 2013 11:36:46 +0300 CC: bind-users@

RE: resolving-problem

2013-07-23 Thread Shawn Bakhtiar
From: me...@cyberia.net.sa To: sjc...@gmail.com Subject: RE: resolving-problem Date: Tue, 23 Jul 2013 11:36:46 +0300 CC: bind-users@lists.isc.org Thank you so much for your email and support, Pls, See, the dig + trace output when use ns1.nesma.net.sa, at the end it say

RE: resolving-problem

2013-07-23 Thread Ejaz
il.com] Sent: Sunday, July 21, 2013 3:09 PM To: Ejaz Cc: Bind users Subject: Re: resolving-problem So the logs would seem to indicate that the server responded to your PC, the only way you can see exactly what happened with that response is with traffic captures on the name server and your PC

Re: resolving-problem

2013-07-22 Thread LiuGN
On 07/21/13 17:55, Ejaz wrote: I have similar problem recently. Ejaz, I think your server can resolve the domain name correctly because it's resolv.conf set to a public dns server, try to resolve by itself and see what happen. About two month ago, my dns server have the similar problem on

Re: resolving-problem

2013-07-21 Thread Matus UHLAR - fantomas
On 21.07.13 12:55, Ejaz wrote: This lately we have been receiving complain from our customer that domains "b2bdr.fransib2corp.com www.fransitadawul.com.sa www.fransiplus.com" are unable to resolve from our DNS server whereas it can be resolve from all over the world FYI, my name servers are a

Re: resolving-problem

2013-07-21 Thread Steven Carr
On 21 July 2013 14:24, Teerapatr Kittiratanachai wrote: > As I had resolve the IP address, the "212.71.32.19" which has configured > is point to "ns1.nesma.net.sa". > That seem that the DNS Server will listen only on itself, i think that the > configuration file also came from the `ns1` too. I'm n

RE: resolving-problem

2013-07-21 Thread Teerapatr Kittiratanachai
me for further knowledge if I got the misunderstanding. -- Te Date: Sun, 21 Jul 2013 13:58:07 +0100 Subject: Re: resolving-problem From: sjc...@gmail.com To: bind-users@lists.isc.org On 21 July 2013 13:42, Teerapatr Kittiratanachai wrote: In my opinion your 'listen-on' options s

Re: resolving-problem

2013-07-21 Thread Steven Carr
On 21 July 2013 13:42, Teerapatr Kittiratanachai wrote: > In my opinion your 'listen-on' options should be changed from > "212.71.32.19" to "any". > Actually I would disagree with that. There may be a very good reason that BIND is configured to listen on a specific IP address, the server may be m

RE: resolving-problem

2013-07-21 Thread Teerapatr Kittiratanachai
In my opinion your 'listen-on' options should be changed from "212.71.32.19" to "any". i wish that can help you. -- T. KITTIRATANACHAI From: sjc...@gmail.com Subject: Re: resolving-problem Date: Sun, 21 Jul 2013 13:09:24 +0100 To: me...@cyberia.net.sa CC: bind-us

Re: resolving-problem

2013-07-21 Thread Steven Carr
So the logs would seem to indicate that the server responded to your PC, the only way you can see exactly what happened with that response is with traffic captures on the name server and your PC. Steve On 21 Jul 2013, at 12:52, "Ejaz" wrote: I can resolve yahoo and here the snippet of lo

Re: resolving-problem

2013-07-21 Thread Steven Carr
172800 IN NS ns2.alfransi.com.sa. > > ;; Received 87 bytes from 192.5.6.30#53(192.5.6.30) in 202 ms > > > > ** ** > > *From My pc. Where I can’t resolve.* > > ** ** > > > fransiplus.com.sa > > Server: ns1.nesm

RE: resolving-problem

2013-07-21 Thread Ejaz
t to ns1.nesma.net.sa timed-out Ejaz _ From: Steven Carr [mailto:sjc...@gmail.com] Sent: Sunday, July 21, 2013 1:11 PM To: Ejaz Cc: Bind users Subject: Re: resolving-problem oops, typo... dig www.fransiplus.com dig +trace www.fransiplus.com On 21 July 2013 11:09, Steven Carr wrote: Ca

Re: resolving-problem

2013-07-21 Thread Steven Carr
oops, typo... dig www.fransiplus.com dig +trace www.fransiplus.com On 21 July 2013 11:09, Steven Carr wrote: > Can you post full output of the following dig commands ran on one of your > nameservers: > > dig www.franisplus.com > dig +trace www.franisplus.com > > Steve > > > > On 21 July 2013

Re: resolving-problem

2013-07-21 Thread Steven Carr
Can you post full output of the following dig commands ran on one of your nameservers: dig www.franisplus.com dig +trace www.franisplus.com Steve On 21 July 2013 10:55, Ejaz wrote: > ** ** ** > > Hello, All, > > ** ** > > This lately we have been receiving complain from our customer th