Grant Taylor wrote:
>
> Is there anything that the networking team can do to help alleviate some of
> the pain? I.e. make sure that equipment returns no route to host error
> messages? Will this make named abort queries before they would otherwise
> timeout?
Dunno :-)
One of the outages we had
On 21.02.16 19:07, blrmaani wrote:
the cache dump also has this entry (myname.mydomain.com is name I am interested
in)
myname.mydomain.com 10324 \-ANY ;-$NXDOMAIN
Which probably means if anyone requests for myname.mydomain.com, they will be
handed NXDOMAIN for upto 10324 seconds from now
This may be a case of my not understanding what this command should do.
Our domain, adi.com, is signed. But when I issue the following command:
rndc signing -list adi.com in external
I get 'No signing records found'
Note that we use views and view external is what the world sees. I expected
tha
On Mon, Feb 22, 2016 at 10:52:25AM -0500, Thomas Schulz wrote:
> rndc signing -list adi.com in external
>
> I get 'No signing records found'
>
> Note that we use views and view external is what the world sees. I expected
> that the rndc signing command would show that the zone is signed.
When a
> On Mon, Feb 22, 2016 at 10:52:25AM -0500, Thomas Schulz wrote:
> > rndc signing -list adi.com in external
> >
> > I get 'No signing records found'
> >
> > Note that we use views and view external is what the world sees. I expected
> > that the rndc signing command would show that the zone is si
Barry and others:
Thanks for the help!
It's my bad that the slave zone's subnet range was missing from
allow-query. I also added the slave IP explicitly to the
allow-transfer option. Now it's seems to be working.
Another issue that I haven't quite figured out is the errors in the
syslog. I have
The Internet roots publish both A (IPv4) and (IPv6) address records.
The log noise you show is what happens when you enable IPv6 but don't have the
necessary routing in place to the IPv6 Internet, either natively or through
some sort of tunnel mechanism.
You could certainly turn IPv6 *off*
This is named trying to talk to nameservers over IPv6 and being
told by the OS that they are unreachable.
At this point in time you should be yelling at your ISP to supply
you with IPv6 connectivity if they aren't already as the world ran
out of IPv4 addresses years ago and the network is only ru
Hi Mark,
Thanks for the explanation!
At this time all my stuff are internal to the data center so I just
added an option to listen to the IPv4 only. This seems to have made
these error messages gone away.
I do have another question: If I don't need to do reverse lookup, do
I still need PTR reco
I've yet to see a system that doesn't do reverse lookups automatically.
Lots of tools do it so, yes, you should be configuring the nameserver
to return PTR records.
Mark
In message
, David Li writes:
> Hi Mark,
>
> Thanks for the explanation!
>
> At this time all my stuff are internal to the
10 matches
Mail list logo
