On 5/8/19 11:06 PM, Greg Rivers wrote:
On Wednesday, May 8, 2019 1:49:38 PM CDT Matthew Richardson wrote:
I have been using the isc-bind-esv repository on Centos 7 since it was
created. On each upgrade, a "yum update" has done the correct thing by
upgrading from the running version to the lates
On Wednesday, May 8, 2019 1:49:38 PM CDT Matthew Richardson wrote:
> I have been using the isc-bind-esv repository on Centos 7 since it was
> created. On each upgrade, a "yum update" has done the correct thing by
> upgrading from the running version to the latest version.
>
> Today (happily on a
Thanks for your reply Chris,
When querying the SOA for that domain I successfully receive the full
SOA details including the addition NS and A record for the authoritative
server of the domain.
The stub server can contact the primary zone but only by IP, DNS
resolution fails unless I add in
I have been using the isc-bind-esv repository on Centos 7 since it was
created. On each upgrade, a "yum update" has done the correct thing by
upgrading from the running version to the latest version.
Today (happily on a cloned test server!) I repeated this with the upgrade
being from 9.11.6 to 9.
Remembering that a stub zone is a cache hint, more information is needed.
o What do the two "master" DNS servers say when asked for the SOA record of
'benlavender.co.uk'?
o Are there A or records in the Additional section? If so, can the
indicated IP addresses be reached?
It may be tha
FreeBSD 11.2
Bind 9.12.3-P1
I have a server which runs several nameservers, each in its own chroot with
its own assigned IP-address.
They run like this:
/usr/local/sbin/named -4 -t /resolver -u bind -c /etc/namedb/named.conf
In named.conf:
statistics-channels {
inet port 5 allow
6 matches
Mail list logo
