DLV verify issue
Hello I am trying to add a dnssec signed tomain to DLV isc. After I have added the DS and also set up the TXT record on my end when I trigger the recheck script I am getting the following error message: We're sorry, but something went wrong. We've been notified about this issue and we'll take a look at it shortly. Can someone help me fix this issue? Thanks in advance Peter___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Digging to the final IP
Anytime you see 'grep' and 'cut' used together, they can usually be
shortened to just 'awk', which requires starting one less process. And if
this case it splits fields the way a users sees them, so the same code
works in both cases:
$ dig +noall +answer home.kreme.com in a | awk '/[\t ]A[\t ]/ {print $NF}'
23.24.150.141
$ dig +noall +answer dave.knig.ht in a | awk '/[\t ]A[\t ]/ {print $NF}'
216.235.14.46
--
Bob Harold
hostmaster, UMnet, ITcom
Information and Technology Services (ITS)
rharo...@umich.edu
734-647-6524 desk
On Wed, Oct 22, 2014 at 6:58 PM, LuKreme wrote:
>
> > On 21 Oct 2014, at 22:46 , Jim Young wrote:
> >
> > On 10/22/14 12:08 AM, "LuKreme" wrote:
> >
> >>> On 21 Oct 2014, at 19:20 , Dave Knight wrote:
> >>>
> >>> $ dig +noall +answer dave.knig.ht in a | egrep 'IN\tA\t' | cut -f6
> >>> 216.235.14.46
> >>
> >> Interesting. This works for me:
> >>
> >> dig +noall +answer home.kreme.com in a | egrep '\tA' | cut -f5
> >>
> >> but on your example, it requires -f6
> >>
> >> And yet, the outputs appear to have the same number of fields.
> >>
> >> $ dig +noall +answer www.kreme.com in a
> >> www.kreme.com. 21139 IN CNAME cerebus.kreme.com.
> >> cerebus.kreme.com. 21141 IN A 23.24.150.141
> >> $ dig +noall +answer dave.knig.ht in a
> >> dave.knig.ht.13916 IN CNAME sb.sanxion.org.
> >> sb.sanxion.org. 222 IN A 216.235.14.46
> >>
> >> Very odd.
> >
> > Subtle formatting difference for human consumption. There are a variable
> > number of ASCII TABs inserted to visually align fields.
>
> Yeah, I saw the extra space after 222, but did not check for a second tab
> following sb.sanxion.org.
>
> > This is where output generated for human consumption can be tricky to
> > parse.
>
> That’s why I like dig +short
>
>
> --
> BART BUCKS ARE NOT LEGAL TENDER Bart chalkboard Ep. 8F06
>
> ___
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Digging to the final IP
In article ,
Bob Harold wrote:
> Anytime you see 'grep' and 'cut' used together, they can usually be
> shortened to just 'awk', which requires starting one less process. And if
> this case it splits fields the way a users sees them, so the same code
> works in both cases:
>
> $ dig +noall +answer home.kreme.com in a | awk '/[\t ]A[\t ]/ {print $NF}'
> 23.24.150.141
> $ dig +noall +answer dave.knig.ht in a | awk '/[\t ]A[\t ]/ {print $NF}'
> 216.235.14.46
$ dig +noall +answer cancer.ucs.ed.ac.uk | perl -ne ' /\sA\s/ && do {
@_=split; print "$_[$#_]\n" }'
129.215.166.13
129.215.200.7
Sam
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Digging to the final IP
At Thu, 23 Oct 2014 15:17:49 +0100,
Sam Wilson wrote:
>
> In article ,
> Bob Harold wrote:
>
> > Anytime you see 'grep' and 'cut' used together, they can usually be
> > shortened to just 'awk', which requires starting one less process. And if
> > this case it splits fields the way a users sees them, so the same code
> > works in both cases:
> >
> > $ dig +noall +answer home.kreme.com in a | awk '/[\t ]A[\t ]/ {print $NF}'
> > 23.24.150.141
> > $ dig +noall +answer dave.knig.ht in a | awk '/[\t ]A[\t ]/ {print $NF}'
> > 216.235.14.46
>
> $ dig +noall +answer cancer.ucs.ed.ac.uk | perl -ne ' /\sA\s/ && do {
> @_=split; print "$_[$#_]\n" }'
> 129.215.166.13
> 129.215.200.7
Which makes it easy, in either case, to return a status value, as
Frank Bulk seemed to want.
Something like
'... {print $NF; count++} END {exit ! count}'
or
| perl -ane ' /\sA\s/ && do { print "$F[$#F]\n"; $count++ } END
{exit ! $count }'
might work.
Niall
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Digging to the final IP
At Thu, 23 Oct 2014 15:17:49 +0100,
Sam Wilson wrote:
>
> In article ,
> Bob Harold wrote:
>
> > Anytime you see 'grep' and 'cut' used together, they can usually be
> > shortened to just 'awk', which requires starting one less process. And if
> > this case it splits fields the way a users sees them, so the same code
> > works in both cases:
> >
> > $ dig +noall +answer home.kreme.com in a | awk '/[\t ]A[\t ]/ {print $NF}'
> > 23.24.150.141
> > $ dig +noall +answer dave.knig.ht in a | awk '/[\t ]A[\t ]/ {print $NF}'
> > 216.235.14.46
>
> $ dig +noall +answer cancer.ucs.ed.ac.uk | perl -ne ' /\sA\s/ && do {
> @_=split; print "$_[$#_]\n" }'
> 129.215.166.13
> 129.215.200.7
Which makes it easy, in either case, to return a status value, as
Frank Bulk seemed to want.
Something like
'... {print $NF; count++} END {exit ! count}'
or
| perl -ane ' /\sA\s/ && do { print "$F[$#F]\n"; $count++ } END
{exit ! $count }'
might work.
Niall
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: DLV verify issue
There is a link that says "Contact Us" on the dlv.isc.org site. That does send email to the part of ISC that deals with the day to day running of DLV. Some of the newer DNSSEC algorithms are not supported yet as the underlying ruby libraries have not been updated to support them yet. The maintainer of those libraries is aware of the issue. Yes, it does actually check the DNSKEY records. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: DLV verify issue
I have sent an e-mail to contact us about a week a go but never got any answer. About 3 weeks a go I have signed another domain and I was able to run the re-check script with no issue and have it verified. Now I am running the same script on the a different domain using the exact same algorithm and I got that ruby error. I have added this new domain about 3 days a go if the script would work it would have been verified by now. > On 24 Oct 2014, at 02:47, Mark Andrews wrote: > > yet. The maintainer of those libraries is aware of the issue. Yes, ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
