Re: Could DNS help solve this?

On Nov 10, 2010, at 5:53 PM, Sten Carlsen wrote: > Hi > > This is not a bind problem, not really a DNS problem. I still hope that these > might be able to help provide the solution. > > With the growing number of registrars of e.g. .com domains, it becomes > difficult or even almost impossible

Re: Could DNS help solve this?

Well, this points the finger at me, I have normally used whois with a specific server to ask the question, never thinking it could be that simple. Does anybody know how whois works? Big thanks to everybody who responded, I feel embarrassed that the solution was that simple and I did not figure th

Re: Could DNS help solve this?

Hi Sten, >Yes, I do use whois, my problem is which of the many dozens of whois >servers to ask. Apologies, sometimes I can be a bit short in my answers. > The whois command line utility I pointed you to comes with a lot of Linux distro's, and it trys a variet

Re: Could DNS help solve this?

On Thursday 11 November 2010 03:59, Sten Carlsen wrote: > Yes, I do use whois, my problem is which of the many dozens of whois > servers to ask. > > E.g. if you want to know who owns telephone.com(random example), do you > ask whois.moniker.com, whois.markmonitor.com, whois.enum.com or ???. W

Re: Could DNS help solve this?

Ian was propably talking about jwhois which is part of almost all Linux distibutions. This whois client "automagically" selects the correct whois server for you. It comes with a configuration file with lots of known tld => whois server pairs. For .com/.net domains it selects the whois server by fir

Re: Could DNS help solve this?

Hi Yes, I do use whois, my problem is which of the many dozens of whois servers to ask. E.g. if you want to know who owns telephone.com(random example), do you ask whois.moniker.com, whois.markmonitor.com, whois.enum.com or ???. If you don't know who to ask, it can take maybe 20 attempts before

Re: Could DNS help solve this?

Hi Sten, >With the growing number of registrars of e.g. .com domains, it becomes >difficult or even almost impossible to figure out which whois server you >should ask for information about a domain name. Use Whois (first under the 'Other software:' heading) from the command prompt.

Could DNS help solve this?

Hi This is not a bind problem, not really a DNS problem. I still hope that these might be able to help provide the solution. With the growing number of registrars of e.g. .com domains, it becomes difficult or even almost impossible to figure out which whois server you should ask for information a