Hi, Stuart
Thank you for your reply.
But I still have a lot of doubts.
That's mean my Authoritative server can't use any acl of view to respond to dig
+subnet?
How can I use dig +subnet=interior_ip to get parsing in the view_interior of my
authoritative service??
And I had to use ip to d
Hi.
An ACL can match other ACLs, meaning that you can include the name of one
ACL in the definition of another.
Your config is being interpreted as:
acl "tsg_acl" {
Start the definition of an ACL called "tsg_acl", which will be followed by
a list of things to match, each of which must end with a s
1422807...@qq.com
-- --
??:
"stuart@registry.godaddy"
> From: bind-users on behalf of Duan Duan
> via bind-users
>
> Hey Guys,
>
> I am upgrading my bind version from 9.11.0 to 9.18.31.
>
> But I have some questions about Access Control Lists(acls).
>
> I am in version 9.11.0 acl file is like this
>
> root@hz#cat tsg_acl
> acl "tsg_acl" {
>
Hey Guys,
I am upgrading my bind version from 9.11.0 to 9.18.31.
But I have some questions about Access Control Lists(acls).
I am in version 9.11.0 acl file is like this
root@hz#cat tsg_acl
acl "tsg_acl" {
ecs 10.56.21.236/30;
};
But when I upgraded to version 9.18.31, it reported an
5 matches
Mail list logo