Chiesa Stefano wrote:
Hi all.
Maybe it's not a new issue, but...
I have a Windows 2003 SP2 with a 9.4.2 release that worked fine for
years.
Today I wanted to upgrade my release to 9.6.
I installed it but when I try to start the service the system says:
Event Type: Error
Event Source: Service
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mark,
Anyone done this recently who can give me a suggestion to where I
may
go wrong?
NXDOMAIN + OPTOUT - AD=0
Doh! I reversed the logic for OPTOUT in my apparently confused head.
Many thanks for the quick correction. Everything
Jukka Pakkanen wrote:
Chiesa Stefano wrote:
Hi all.
Maybe it's not a new issue, but...
I have a Windows 2003 SP2 with a 9.4.2 release that worked fine for
years.
Today I wanted to upgrade my release to 9.6.
I installed it but when I try to start the service the system says:
Event Type:
Jukka Pakkanen wrote:
Chiesa Stefano wrote:
Hi all.
Maybe it's not a new issue, but...
I have a Windows 2003 SP2 with a 9.4.2 release that worked fine for
years.
Today I wanted to upgrade my release to 9.6.
I installed it but when I try to start the service the system says:
Event Type:
When I do a nslookup or dig I only see the first two servers and not sec2:
--
ns-1: nslookup
set type=ns
_tcp.utmck.edu
Non-authoritative answer:
_tcp.utmck.edu nameserver = pri1.utmck.edu
_tcp.utmck.edu nameserver = sec1.utmck.edu
Authoritative answers can be
I know what ISC will say on this -- that we should be tracking down
people whose DNS servers or network infrastructure blocks or impedes
EDNS... this is fine and well, and we do make such efforts, but often
times networ owners are unresponsive and our own customer demands
compel us to disable EDNS
I am in the process of developing a DR (disaster recovery) plan for my primary
masters. Could someone please confirm (or correct me) that a second server in
the masters {} statement of a slave zone will only be used in the event that
the first master cannot be reached? Example:
zone
On Tue, Jan 13, 2009 at 04:35:46PM -0800, Mark Andrews wrote:
The number of nameservers that fail to respond to EDNS
queries is miniscule. The majority of nameservers on the
net actually talk EDNS.
I suggest that you re-analyse the failures to determine
their
See http://ftp.isc.org/www/bind/arm95/Bv9ARM.ch06.html#id2593348
(Sorry that is for a different version of BIND, but it does cover more
statistics info.)
If you need any specific clarifications, please let us know.
___
bind-users mailing list
In message 20090114021016.ga24...@esri.com, Ray Van Dolson writes:
On Tue, Jan 13, 2009 at 05:00:38PM -0800, Ray Van Dolson wrote:
On Tue, Jan 13, 2009 at 04:35:46PM -0800, Mark Andrews wrote:
The number of nameservers that fail to respond to EDNS
queries is miniscule. The majority
10 matches
Mail list logo