Re: problem domains host in ns1/ns2.planetdomain.com (Eric Yiu)

t; would be to contact them and point out it appears some zone data was lost > when service was transferred. Trying to use Google isn't going to help if > the data isn't on the designated authoritative servers. > > Hope this helps. > John > > - > Date: Thu

problem domains host in ns1/ns2.planetdomain.com

Hi, Someday ago netregistry.com bought planetdomain.com. And there are a number of domains (not sure if all) host at ns1/ns2.planetdomain.com ns point to ns1/ns2/ns3.netregistry.net. However these netregistry.net do not host these domain. Then if the records of these domain expired and refresh

Re: resolving from loopback is much smooth?

Hi Graham, Thx for your great tip, it seems it fix my problem. Eric On Tue, Jun 7, 2016 at 5:45 PM, Graham Clinch wrote: > Hi Eric, > > > I run bind dns server 9.9 now with around 3000query/s. I recently > > upgrade our server to Fujitsu M10-1 Solaris 10 with

resolving from loopback is much smooth?

Hi, I run bind dns server 9.9 now with around 3000query/s. I recently upgrade our server to Fujitsu M10-1 Solaris 10 with bind9.10. I feel that the server serving bind is not as fast as old one in intel solaris which was more than 8 years ago. I tried a few test and found that dig @localhost is

servfail when refresh aws.amazon.com

Hi, I am using bind9.7.3-P1 with solaris10x86. I notice that sometimes our bind server will reply servfail when querying a zone aws.amazon.com which is expiring, while this aws.amazon.com only 60sec cache lifetime, eg. /usr/local/bin/dig a aws.amazon.com ; DiG 9.7.3-P1 a aws.amazon.com ;;

Re: servfail when refresh aws.amazon.com

:25 AM, Kevin Darcy k...@chrysler.com wrote: ** On 6/22/2011 7:26 AM, Eric Yiu wrote: Hi, I am using bind9.7.3-P1 with solaris10x86. I notice that sometimes our bind server will reply servfail when querying a zone aws.amazon.com which is expiring, while this aws.amazon.com only 60sec