For various testing reasons, I have been running a tld here of htt. It
has worked of old and continues to work on my new 9.8.2 Centos servers.
Problem came up from a namecaching server that 'forwards only' to my
internal server. It cannot resolve any hosts in this tld and on the
server forwarded to I see:
htt. is mastered on my servers and home.htt is slaved off of old server
(that will get upgraded later). The host I want to access is
repo.home.htt. From my 'regular' DNS servers this works well, but from
the namecaching server that 'forwards only' to this server I get on the
caching server:
Feb 27 09:52:48 klovia named[1703]: error (insecurity proof failed)
resolving 'repo.home.htt/AAAA/IN': 208.83.67.188#53
Feb 27 09:52:48 klovia named[1703]: error (insecurity proof failed)
resolving 'repo.home.htt/A/IN': 208.83.67.188#53
and on the main server (at 208.83.67.188) I see:
Feb 27 09:52:47 rigel named[9294]: error (chase DS servers) resolving
'htt/DS/IN': 208.83.67.188#53
what little research I have done directs me to htt is not signed? Of
course home.htt is not either as that server is rather old (bind 9.6.2)
Interestingly when 208.83.67.188 does a lookup in my regular domain I see:
Feb 27 11:16:14 rigel named[9294]: error (chase DS servers) resolving
'htt-consult.com/DS/IN': 208.83.67.188#53
So what am I missing here?
_______________________________________________
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
