Re: Reverse IPv6

Alternatively you could just use update-policy and tcp-self and allow the clients that want PTR records to add them for the addresses they are using with nsupdate or similar. zone 3.0.0.0.1.0.0.A.8.B.D.0.1.0.0.2.IP6.ARPA { type master; file "3.0.0.0.1.0.0.A.8.B.D.0.1.0.0.2.IP6.ARP

RE: Reverse IPv6

> > > > > From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Bob > Harold > Sent: Friday, February 03, 2017 4:15 PM > To: Cathy Almond > Cc: bind-users@lists.isc.org > Subject: Re: Reverse IPv6 > > > On Thu, Feb 2, 2017 at 5:44 AM, Cathy Almond wrote: > > > On 02/02/2017 02:5

Re: named-checkzone with multiple $ORIGIN

Ok that was my misunderstanding of named-checkzone. I though I had to check for all $ORIGINs. I haven't played with IPv6 yet. I hope I'll have a chance to do it eventually. Thanks for your time guys! On Mon, Jun 5, 2017 at 9:49 AM, Mark Elkins wrote: > Most certainly - Yes. > > You have a s

Re: named-checkzone with multiple $ORIGIN

Most certainly - Yes. You have a single zone here, thus only: named-checkzone example.com example.com.zone ...should work. Wait till you play with a reverse IPv6 zone - where I personally use many $ORIGIN statements - saves hours of typing and makes reading the Zones s

Re: named-checkzone with multiple $ORIGIN

Bernard Fay wrote: > > should I understand while using named-checkzone I need to enter *only* > the top domain and named-checkzone will understand the subdomains > defined by the multiple $ORIGIN in the zone file? Yes, named-checkzone basically just loads the zone file (the whole thing) as if it

Re: named-checkzone with multiple $ORIGIN

I understand what $ORIGIN is doing by reducing the typing and making it easier to maintain the zone files. To Tony, should I understand while using named-checkzone I need to enter *only* the top domain and named-checkzone will understand the subdomains defined by the multiple $ORIGIN in the zone f

Re: named-checkzone with multiple $ORIGIN

In message , Bernard Fay writes: > Sorry keyboard problem... > > > I took control of a DNS based on Bind 9.9. One of the zone files have > multiple $ORIGIN for example: > > $ORIGIN example.com > ... > $ORIGIN sub1.example.com > ... > $ORIGIN sub2.example.com > ... > $ORIGIN sub3.example.com >

Re: named-checkzone with multiple $ORIGIN

Bernard Fay wrote: > > I took control of a DNS based on Bind 9.9. One of the zone files have > multiple $ORIGIN for example: The key thing to understand is that $ORIGIN just controls how unqualified domain names are expanded into fully-qualified domain names. In particular, $ORIGIN is completely

Re: named-checkzone with multiple $ORIGIN

Am 05.06.2017 um 14:36 schrieb Bernard Fay: Sorry keyboard problem... I took control of a DNS based on Bind 9.9. One of the zone files have multiple $ORIGIN for example: $ORIGIN example.com ... $ORIGIN sub1.example.com ... $ORIGIN sub2.example.com ... $ORIGIN s

Re: named-checkzone with multiple $ORIGIN

Sorry keyboard problem... I took control of a DNS based on Bind 9.9. One of the zone files have multiple $ORIGIN for example: $ORIGIN example.com ... $ORIGIN sub1.example.com ... $ORIGIN sub2.example.com ... $ORIGIN sub3.example.com ... While checking the zone file with: named-checkzone examp

named-checkzone with multiple $ORIGIN

Hi, I took control of a DNS based on Bind 9.9. One of the zone files have multiple $ORIGIN for example: $ORIGIN example.com ... $ORIGIN sub1.example.com ... $ORIGIN sub2.example.com ... $ORIGIN sub3.example.com ... While checking the zone file with: named-checkzone example.com example.com.zone

RE: Tuning suggestions for high-core-count Linux servers

So, different tact today, namely the monitoring of '/proc/net/softnet_stat' to try reduce potential errors on the interface. End result: 517k qps. Final changes for the day: sysctl -w net.core.netdev_max_backlog=32768 sysctl -w net.core.netdev_budget=2700 /root/nic_balance.sh em1 0 2 netdev_max