RE: Reasons for not resolving

2009-11-01 Thread Alans
What happens if you try to resolve yarnandwaste.com directly from 96.31.75.113/96.31.75.114? I can't, not even able to ping it (.113 & .114) we'll check our connectivity with that network. As for gegreklam.com, I too when resolve from c.gtld-servers.net can get A record IP but not with +trac

Re: Reasons for not resolving

2009-10-29 Thread Kevin Darcy
Alans wrote: Kevin, Thanks for your explanation, yarnandwaste.com cannot be resolved, below is dig +trace result: [r...@ns2 ~]# dig yarnandwaste.com +trace ; <<>> DiG 9.4.2 <<>> yarnandwaste.com +trace ;; global options: printcmd . 437569 IN NS B.ROOT-SERVERS.N

RE: Reasons for not resolving

2009-10-28 Thread Alans
oint by "starting with no cache" since it gives us 2 different NS results, right? Best regards, Alans -Original Message- From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Kevin Darcy Sent: Wednesday, October 28, 2009 7:03 PM To: bind-users@lists.

Re: Reasons for not resolving

2009-10-28 Thread Kevin Darcy
ich means it’s not down fir everyone!! Any ideas? Kind regards, Alans *From:* bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] *On Behalf Of *Alans *Sent:* Wednesday, October 28, 2009 10:47 AM *To:* bind-users@lists.isc.org *Subject:* Reasons for not resolving Hello

RE: Reasons for not resolving

2009-10-28 Thread Alans
one!! Any ideas? Kind regards, Alans From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Alans Sent: Wednesday, October 28, 2009 10:47 AM To: bind-users@lists.isc.org Subject: Reasons for not resolving Hello, There are few websites that our DNS

Reasons for not resolving

2009-10-28 Thread Alans
Hello, There are few websites that our DNS (BIND 9.4.2 on CentOS 5) is not resolving while others like 4.2.2.2 does, I wonder what could be the reasons for this? Regards, Alans ___ bind-users mailing list bind-users@lists.isc.org https://lists.i