Re: Access external hosts with internal split DNS resolver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.08.2015 um 06:58 schrieb Josh Kuo: > Add www.mydomain.co.nz to your internal zone, that is one common > way to deal with it. With BIND you can keep the common records in a > separate file and use "include" statement to avoid double entry. > > >

Re: tsig zone sharing between zones check + scream

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 08.08.2015 um 03:06 schrieb Lawrence K. Chen, P.Eng.: > > > On 2015-08-07 10:08, Heiko Richter wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> Am 07.08.2015 um 08:52 schrieb Lawrence K. Chen, P.Eng.

Re: configuration error in lists.isc.org

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.08.2015 um 08:03 schrieb Lawrence K. Chen, P.Eng.: > In looking through the received headers I see that there's no SPF > for lists.isc.org Wether or not lists.isc.org was never in question. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.2

Re: [OT] Re: configuration error in lists.isc.org

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.08.2015 um 08:29 schrieb Matus UHLAR - fantomas: >>> On Aug 6, 2015, at 4:25 PM, Heiko Richter >>> mailto:em...@heikorichter.name>> >>> wrote: >>>> Whenever I post something to the list (I'm not

Re: tsig zone sharing between zones check + scream

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.08.2015 um 08:52 schrieb Lawrence K. Chen, P.Eng.: > Gjust noticed that about 12 hours ago, the business office > person finally update our KSK with registrar. (where window was > last month.) > > Well, apparently history must repeat...

Re: do not stupidly delete ZSK files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.08.2015 um 07:16 schrieb Lawrence K. Chen, P.Eng.: > > > On 2015-08-06 19:26, Heiko Richter wrote: > >>> Though back then I was still building bind 32-bit, and the >>> hardware as much slower. A full signing was

Re: do not stupidly delete ZSK files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.08.2015 um 03:36 schrieb Carl Byington: > -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > On Fri, 2015-08-07 at 02:46 +0200, Heiko Richter wrote: >> Sadly automated KSK rollover isn't supported by most registrars, >

Re: [OT] Re: configuration error in lists.isc.org

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.08.2015 um 02:03 schrieb Charles Swiger: > On Aug 6, 2015, at 4:25 PM, Heiko Richter <mailto:em...@heikorichter.name>> wrote: >> Whenever I post something to the list (I'm not using SMTP, I'm >>

Re: do not stupidly delete ZSK files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.08.2015 um 02:35 schrieb Dave Warren: > On 2015-08-06 17:26, Heiko Richter wrote: >> Root is signed with RSASHA256 at the moment. There is no sence in >> having a more secure algorithm because anybody who can't crack that &

Re: do not stupidly delete ZSK files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.08.2015 um 01:55 schrieb Lawrence K. Chen, P.Eng.: > > > On 2015-08-06 17:54, Heiko Richter wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> Am 07.08.2015 um 00:23 schrieb Lawrence K. Chen, P.Eng.: >

configuration error in lists.isc.org

er has. So ISC: please fix your list servers, let them rewrite the From headers! Yours, Heiko Richter -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJVw+zvAAoJECKEz6pWghImwr4P+wb6hzvJTFK3WYOIpoj5Vw0B CEV4vhkj0vKYaAvui6rwJAtUkcM8C8IvbdhxdM4TiM6Av7wCBi+uhb

Re: do not stupidly delete ZSK files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.08.2015 um 00:23 schrieb Lawrence K. Chen, P.Eng.: > > > On 2015-07-31 06:33, Tony Finch wrote: >>> Most zones have four authoritative nameservers, only one of >>> which I manage. Of the three I don't manage, I'm pretty sure at >>> least two ha

Re: separation of authoritative and recursive functions on internal networks

Am 05.08.2015 um 16:18 schrieb Gary Carr: > Hello, > > I understand the importance of separating authoritative and recursive > functions on public facing systems. How crucial is it on internal > systems? > > My clients today resolve against internal servers that do recursion > and also hold autho

Re: DNSSec KSK problem

Am 05.08.2015 um 06:15 schrieb Mark Andrews: > In message , Heiko Richter writes: >> Hi! >> >> I'm hoping someone here can help me with a problem in my DNSSec >> configuration. >> >> I'm running Bind 9 in Debian Jessie and just finished confi

Re: Block propagation for a specific record A

Am 29.07.2015 um 10:59 schrieb Job: > Hello, > > for a test page purpuose, we would like to avoid propagation only for a > specific record A, example: > test.domain.com > > We need to test if users set up our DNS server in ethernet configuration, and > they display correctly the test page. > Bu

DNSSec KSK problem

Hi! I'm hoping someone here can help me with a problem in my DNSSec configuration. I'm running Bind 9 in Debian Jessie and just finished configuring it with DNSSec for my zones. Everything including automatic key rollover for the ZSKs is working, except for a slight anomaly with my KSKs: For som

Re: ERROR : - writeable file 'data/udalgurijudiciarygov.hosts': already in use: /etc/nicnet2007.govdomain:15424 - loading configuration: failure

Am 03.08.2015 um 08:08 schrieb Mukund Sivaraman: > Hi Prakash > > On Mon, Aug 03, 2015 at 10:14:50AM +0530, prakash wrote: >> Aug 3 09:59:34 govindnsvm named[7436]: /etc/nicnet2007.govdomain:15424: >> writeable file 'data/udalgurijudiciarygov.hosts': already in use: >> /etc/nicnet2007.govdomain

Re: Order and Preference Priority in DNS Responses

Am 03.08.2015 um 13:44 schrieb Reindl Harald: > > > Am 03.08.2015 um 13:38 schrieb Harshith Mulky: >> I wanted to understand how Order and Preference Values have an impact on >> the answers Received from the DNS Server >> >> I am asking because, I have 4 records for NAPTR Query, as below >> >> ca

Re: Order and Preference Priority in DNS Responses

Am 03.08.2015 um 13:38 schrieb Harshith Mulky: > I wanted to understand how Order and Preference Values have an impact on > the answers Received from the DNS Server > > I am asking because, I have 4 records for NAPTR Query, as below > > carrier1.com 86400 IN NAPTR 50 50“s” “SIPS+D2T”