Re: hhs.gov resolvers broken, or BIND misconfigured?

2016-03-08 Thread James Ralston
On Fri, Mar 4, 2016 at 1:25 PM, John Wobus wrote: > > Our recursive resolver periodically returns SERVFAIL for lookups > > for hhs.gov records, which are served by these nameservers: > > > > rh202ns1.355.dhhs.gov. 168 IN A 158.74.30.98 > > rh202ns1.355.dhhs.gov. 14260 IN A

Re: hhs.gov resolvers broken, or BIND misconfigured?

2016-03-02 Thread James Ralston
On Wed, Mar 2, 2016 at 7:08 AM, Tony Finch wrote: > James Ralston wrote: > > > We're running a recursive resolver on RHEL6, using the latest > > RHEL-provided BIND package, bind-9.8.2-0.37.rc1.el6_7.6. The > > recursive resolver only has an IPv4 interface;

hhs.gov resolvers broken, or BIND misconfigured?

2016-03-01 Thread James Ralston
We have a mystery. We're running a recursive resolver on RHEL6, using the latest RHEL-provided BIND package, bind-9.8.2-0.37.rc1.el6_7.6. The recursive resolver only has an IPv4 interface; it does not have an IPv6 interface. DNSSEC is enabled (by default). Our recursive resolver periodically re