RE: forwarding zone to another DNS server problem

hi tony, I 'm not familiar with'stub'. The description of 'stub' is hard to understand. What do you mean is to configure 'stub' in the registered authoritative server and to configure zone file with A records in other not registered authoritative servers. Is it all right? Thanks, Guanghua

RE: forwarding zone to another DNS server problem

houguanghua wrote: > I 'm not familiar with'stub'. The description of 'stub' is hard to > understand. Yes it's a bit weird. Think of it like the root hints but for other zones: i.e. a hint zone configuration in a recursive server tells named that instead of using a referral from the parent zon

unexpected loopback srrt

Hi everyone, I try to set up an authentic bind server in the loopback address(127.0.0.1) in our recursive server of our testbed for test reason. When I send a large number of junk queries(5000QPS), the srrt of loopback server in cash is unexpectedly large. Does anyone know the reason? The srrt is n

Re: forwarding zone to another DNS server problem

In article , Tony Finch wrote: > houguanghua wrote: > > > I 'm not familiar with'stub'. The description of 'stub' is hard to > > understand. > > Yes it's a bit weird. Think of it like the root hints but for other zones: > i.e. a hint zone configuration in a recursive server tells named that

DANE record rejected by named-checkzone

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 named keeps refusing my zone file in which I included a DANE record: [root]# named-checkzone offerman.com db.offerman.com db.offerman.com:59: _443._tcp.offerman.com: bad owner name (check-names) db.offerman.com:60: _443._tcp.offerman.com: bad owner n

Re: DANE record rejected by named-checkzone

In message <545954b0.8080...@offerman.com>, "Adrian (Aad) Offerman" writes: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > named keeps refusing my zone file in which I included a DANE record: > > [root]# named-checkzone offerman.com db.offerman.com > db.offerman.com:59: _443._tcp.offer