HIP record

2012-02-19 Thread Miek Gieben
Hello, While playing with the HIP record I wanted to place some test records in a zone. I used the examples from RFC 5205 (Section 6.). ;; Tests t IN HIP ( 2 200100107B1A74DF365639CC39F1D578 AwEAAbdxyhNuSutc5EMzxTs9LBPCIkOFH8cIvM4p 9+LrV4e19Wz

Re: Assistance with SPF Records for BIND

2012-02-19 Thread ml
to simply is better my TXT record ~]$ host -t txt fakessh.eu 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: fakessh.eu descriptive text "spf2.0/pra ip4:46.105.34.177 ip4:91.121.7.86 ?all" fakessh.eu descriptive text "spf2.0/mfrom ip4:46.105.34.177 ip4:91.121.7.86 ~all"

Re: HIP record

2012-02-19 Thread Mark Andrews
Both records are malformed. Remove the whitespace from the public key. The Public Key field is represented as the Base64 encoding [RFC4648] of the public key. The encoding MUST NOT contain whitespace(s) to distinguish it from the Rendezvous Servers field. In message <20120219135619.ga

Re: named.conf splitting

2012-02-19 Thread Michelle Konzack
Hello Noel Butler, Am 2012-02-18 11:25:10, hacktest Du folgendes herunter: > If the OP is trying to avoid inline editing, does not the above become > pointless? Yes, and the wish of the OP is my wish too! > Still requires inline editing to remove the > include "/path/to/etc/zone1.conf", else nam

Re: HIP record

2012-02-19 Thread Miek Gieben
[ Quoting at 07:09 on Feb 20 in "Re: HIP record..." ] > Both records are malformed. Remove the whitespace from the public key. > >The Public Key field is represented as the Base64 encoding [RFC4648] >of the public key. The encoding MUST NOT contain whitespace(s) to >distinguish it f

Re: HIP record

2012-02-19 Thread Mark Andrews
In message <20120219202216.ga17...@miek.nl>, Miek Gieben writes: > [ Quoting at 07:09 on Feb 20 in "Re: HIP record..." ] > > Both records are malformed. Remove the whitespace from the public key. > >=20 > >The Public Key field is represented as the Base64 encoding [RFC4648] > >of the pub

Re: HIP record

2012-02-19 Thread Miek Gieben
[ Quoting at 07:45 on Feb 20 in "Re: HIP record..." ] > > But I have another query then. Is there a difference between: > > > > blah ( bla1 > > bla2 > > ) > > > > and: > > > > blah ( bla1 > > bla2 > > ) > > > > In other words: is the space significant in the second example? > > no. Ok, that

Re: named.conf splitting

2012-02-19 Thread Alan Clegg
While not _exactly_ what was asked for, "rndc addzone" and "rndc delzone" seem to be able to do what you want... Just an idea.. AlanC -- a...@clegg.com | 1.919.355.8851 signature.asc Description: OpenPGP digital signature ___ Please visit https://li

Re: HIP record

2012-02-19 Thread Mark Andrews
In message <20120219210232.gb6...@miek.nl>, Miek Gieben writes: > [ Quoting at 07:45 on Feb 20 in "Re: HIP record..." ] > > > But I have another query then. Is there a difference between: > > > > > > blah ( bla1 > > > bla2 > > > ) > > > > > > and: > > > > > > blah ( bla1 > > > bla2 > > > ) >

Re: Assistance with SPF Records for BIND

2012-02-19 Thread Noel Butler
On Sun, 2012-02-19 at 17:00 +0100, ml wrote: > > fakessh.eu descriptive text "spf2.0/pra ip4:46.105.34.177 > ip4:91.121.7.86 ?all" > fakessh.eu descriptive text "v=spf1 ip4:46.105.34.177 ip4:91.121.7.86 > ?all" > Why did you bother with the record at all? "Question mark" indicat

Re: HIP record

2012-02-19 Thread Miek Gieben
[ Quoting at 10:51 on Feb 20 in "Re: HIP record..." ] > The presence of white space is significant, not whether the whitespace > is "" or " + " or even "". You > asked me if there was any difference between "" or > " + " and there isn't. Where is this specified? The closest I can find is 1035, b