resolving-problem

2013-07-21 Thread Ejaz
Hello, All, 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 as listed b

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

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 Ejaz
Thank you so much. Let me tell you, it resolve from the server without any problem, but when I tried to resolve these domain from my PC by using the ns1.nesma.net.sa which I can't how ever as you said, the below is the output of dig. Nslookup etc.. >From the server, it is ok

Re: resolving-problem

2013-07-21 Thread Steven Carr
Can you resolve other websites using ns1.nesma.net.sa from your PC or is it just these few sites that you can't resolve? Are you able to share your BIND configuration? Steve On 21 July 2013 11:24, Ejaz wrote: > ** ** ** > > Thank you so much. > > ** ** > > Let me tell you, it resolve fro

FW: resolving-problem

2013-07-21 Thread Ejaz
Thanks you once again for your quick response. Yes, I can resolve all other webistes without any problems. As well as requested, find the attached only main the configuration file, Ejaz _ acl trusted { 92.48.0.0/18; 212.119.65.0/24; 212.71.32.0/19; 213.181

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 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-users@lists.isc.org So the logs

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
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 not sure about this. Can you explain me for further knowledge i

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 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

New warning message...

2013-07-21 Thread SH Development
I just started noticing these in my log: 7/21/13 11:33:13 PM named[355] 21-Jul-2013 23:33:13.646 general: warning: zone domain.com/IN: 'domain.com' found SPF/TXT record but no SPF/SPF record found, add matching type SPF record The zone does have an SPF record. I'm not sure I understan

Re: New warning message...

2013-07-21 Thread Mark Andrews
In message , SH Development writes: > I just started noticing these in my log: > > 7/21/13 11:33:13 PM named[355] 21-Jul-2013 23:33:13.646 general: > warning: zone domain.com/IN: 'domain.com' found S > PF/TXT record but no SPF/SPF record found, add matching type SPF record > > The zone

Re: New warning message...

2013-07-21 Thread Jason Hellenthal
It's exactly as it says... Instead of ... TXT "SPF ..." You now do ... SPF "SPF ..." -- Jason Hellenthal Inbox: jhellent...@dataix.net Voice: +1 (616) 953-0176 JJH48-ARIN On Jul 22, 2013, at 0:48, SH Development wrote: > I just started noticing these in my log: > > 7/21/13 11:33:13

Re: New warning message...

2013-07-21 Thread Noel Butler
On Mon, 2013-07-22 at 02:51 -0400, Jason Hellenthal wrote: > It's exactly as it says... > > > Instead of > ... TXT "SPF ..." > > > You now do > > > ... SPF "SPF ..." > > Mark Andrews wrote: No. It has a legacy SPF TXT record. It SHOULD have record of type SPF as per RFC 4408. Named w

Re: New warning message...

2013-07-21 Thread Jason Hellenthal
Basically a SPF record type in place that's new but you could carry both for new and older clients. -- Jason Hellenthal Inbox: jhellent...@dataix.net Voice: +1 (616) 953-0176 JJH48-ARIN On Jul 22, 2013, at 0:48, SH Development wrote: > I just started noticing these in my log: > > 7/21/