Date: Thu, 9 Dec 2010 17:51:41 -0500 From: Chris Brennan <xaero@xaerolimit.net> To: Paul Macdonald <paul@ifdnrg.com> Cc: FreeBSD Questions <questions@freebsd.org>, Andy Tornquist <andyt@afua.net> Subject: Re: more dns weirdness Message-ID: <AANLkTi=Vx_TaXqvzX0APG9j4xdS3K7qtDyUVJZVkzp0F@mail.gmail.com> In-Reply-To: <4D015517.3000901@ifdnrg.com> References: <4D013ECD.7090102@ifdnrg.com> <AANLkTikJZafHF5us8b8UszipHDGsVp2G58EkumNvd1s8@mail.gmail.com> <4D015517.3000901@ifdnrg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 9, 2010 at 5:15 PM, Paul Macdonald <paul@ifdnrg.com> wrote: > the wider issue is that freebsd whois will use tld.whois-servers.netcnames to resolve appropriate whois servers and that > whois-servers.net has nameservers from one sole provider (ultradns), > which is still having problems. > > I'm not overally bothered about amazons' whois, but i am concerned about > freebsd's whois being tied to one NS provider (ultradns) which affects dig's > Indeed, whois on 2 freebsd boxes reports the faulty search but on my linux box (gentoo) it worked fine.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=Vx_TaXqvzX0APG9j4xdS3K7qtDyUVJZVkzp0F>