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
Alans, Why would you use Google to determine whether a web site is up or not? It's not even clear to me that you're having a DNS problem. It's rather bad practice to have lots of reverse-records in the DNS for a given address (e.g. 96.31.75.113), and can even cause problems with oversized resp

RE: Reasons for not resolving

2009-10-28 Thread Alans
I looked more and I figure out that we can't ping or browse any of these hosts http://www.ip-adress.com/reverse_ip/96.31.75.113 (they all are on one IP) it's confusing because when I search in google for host names it appears in the result which means it's not down fir everyone!! Any ideas? Kin