, Oct 13, 2020 at 1:34 PM Tony Finch wrote:
>
> Veaceslav Revutchi wrote:
>
> > Given this soa:
> >
> > fe80.info. 3600 IN SOA ns-538.awsdns-03.net.
> > awsdns-hostmaster.amazon.com. 1 7200 900 1209600 60
> >
> > I see bind caching negative answers for
Given this soa:
fe80.info. 3600 IN SOA ns-538.awsdns-03.net.
awsdns-hostmaster.amazon.com. 1 7200 900 1209600 60
I see bind caching negative answers for 3600 instead of 60. The rfc
and my google searches suggest that it should pick the MIN(soa ttl,
soa min ttl) for that purpose. What am I
I'm looking for a way to detect and alert when our monitoring team
starts pulling the stats from our resolvers by http://resolver:8080
instead of http://resolver:8080/xml/v3/server
as the short url results in a large download and can be service
impacting. Picking up the packets on the wire on
On Wed, Dec 14, 2016 at 10:35 AM, Barry S. Finkel <bsfin...@att.net> wrote:
> On 12/14/2016 Veaceslav Revutchi <slavarevut...@gmail.com> wrote:
>
>> Since this thread is still fresh, what is the current best practice
>> when slaving from AD? Do you pic
Since this thread is still fresh, what is the current best practice
when slaving from AD? Do you pick one DC and list it as master or is
it safe to list multiple? We are looking to do the same and just
started the conversation with our AD team. The serial numbers among
DCs authoritative for the
Hi, I have a statement in my recursive resolver (rr-server) similar to this:
zone "example.org" { type forward; forward only; forwarders {
10.64.1.1; 10.64.1.2; } ; };
When clients ask for "aaa.example.org" I would expect it to send the
same query to one of the IPs above and return the answer to
I need to provide DNS64 on a caching resolver for a project (MS direct
access). It will mostly be resolving internal names, most of which are
delegated to an LB. The requests will be arriving over v4 only (nat64
already in place).
Here is the setup:
for simplicity I will show one authoritative
A couple of days ago I received complaints from users that they could not
open netaddress.com for their email.
The caching resolver would return SrvFail for the name. After digging
through its cache I discovered the following entries:
There is a credit union website that our users access from work and
their dns has been broken for the past few days where the www. version
works, but the plain name (without the www.) points to some old IP
that's not responding. Tried to call them and all I got was that they
know they have some
Hello,
Having trouble resolving a name, hope someone can point me in the right
direction. All my caching resolvers running BIND
9.7.0-P2-RedHat-9.7.0-10.P2.el5_8.3 are returning ServFail for
www.solarwinds.com. For example:
-
10 matches
Mail list logo
