Hey Guys,
I have a cache, which can cache the client's domain name request and forward
the client ip to my bind authority service in the form of ecs to hit views.
But I know that after bind 9.13, authoritative ecs functionality is not
supported.
So I've been unable to upgrade the bind versi
Hey Guys,
I am using bind version 9.11.0.
There are many views and zones running inside.
bind can run normally and resolve domain names normally.
But when I execute rndc reload, I I received an error message.
./server.c:3799: unexpected error:
unable to obtain neither an IPv4 nor
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
1422807...@qq.com
-- --
??:
"stuart@registry.godaddy"
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
Hey , guys
I have been studying DOH-related content recently.
The bind version I use is 9.18.31.
bind does not seem to support http1.1 requests.
Generally speaking, what is the appropriate form of a client's doh request? Do
we have to base 64 encoding the domain name?
How can I get the r
Hi,
I'm sorry for my misrepresentation.
It is ecs.
How do I use my native bind to support ecs recursive requests ??
I saw a document describing this, saying that the subscriber version is
required to support ecs recursive requests.
BIND 9 -S Edition 1123.pages
If I want ues client ip to
7 matches
Mail list logo