Re: rpz_rewrite(): failure

2023-05-15 Thread Wilfred Sarmiento via bind-users
t has been > deprecated. > > As to this specific issue, I'm not sure. You might get more help from > others, however, if you share your configuration. You can get a > configuration scrubbed of keys using `named-checkconf -px` > > Thank you, > > Darren Ankney > > O

rpz_rewrite(): failure

2023-05-09 Thread Wilfred Sarmiento via bind-users
Hi Bind Users, Any one familiar with the error we encountered on DNS BIND 9.18.2 Ubuntu for DNS Caching, below; We are using RPZ for redirecting domains (porn sites) where we already have 20k+ entries. The domain (globem2m.com.ph) from below logs is not in the RPZ list but was processed for RPZ

Re: SRV Record Server Availability

2021-01-06 Thread Wilfred Sarmiento via bind-users
Hi Tale, Happy new year! Your understanding is correct, i just thought that SRV can detect whose server is alive so it can choose and provide an answer with the available Server. Thank you! On Tue, 5 Jan 2021, 23:53 tale wrote: > On Tue, Jan 5, 2021 at 4:30 AM Wilfred Sarmiento via b

SRV Record Server Availability

2021-01-05 Thread Wilfred Sarmiento via bind-users
Hi, Is DNS Bind SRV record can detect the Server's availability? If yes, how? Thank you, Wil -- This e-mail message (including attachments, if any) is intended for the use of the individual or the entity to whom it is addressed and may contain information that is privileged, proprietary,

Re: Query failed (timed out)

2019-11-06 Thread Wilfred Sarmiento via bind-users
ie @157.83.102.245 > > ;; global options: +cmd > > ;; Got answer: > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20094 > > ;; flags: qr aa rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 > > ;; WARNING: recursion requested but not available >

Re: Query failed (timed out)

2019-11-06 Thread Wilfred Sarmiento via bind-users
Hi Steinar, Noted and thank you very much. Regards. *Wil* On Wed, Nov 6, 2019 at 4:21 PM wrote: > > The workaround works, does BIND 9.14 has a patch to resolve this? Since > we > > have a multiple Cache server, we need to do this every time we encounter > > another domain that has this same

Re: Query failed (timed out)

2019-11-06 Thread Wilfred Sarmiento via bind-users
d; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 > ;; WARNING: recursion requested but not available > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 4096 > ;; QUESTION SECTION: > ;federate-secure.glbaa.barclays.com. IN A > > ;; ANSWER SECTION: > fed

Re: Query failed (timed out)

2019-11-06 Thread Wilfred Sarmiento via bind-users
rver 157.83.102.245 { send-cookie false; }; > > See also > > https://ftp.isc.org/isc/bind9/9.14.0/doc/arm/Bv9ARM.ch05.html#server_statement_grammar > > Daniel > > > On 06.11.19 08:32, Wilfred Sarmiento via bind-users wrote: > > Hi Bind Users, > >

Query failed (timed out)

2019-11-05 Thread Wilfred Sarmiento via bind-users
Hi Bind Users, Anyone have a similar issue we are encountering with the subdomain of Barclays.com specifically federate.secure.barclays.com Our cache server could not resolve the said subdomain, but was able to resolve their root domain barclays.com and any other known domains. Debug just showed

Query CNAME failed

2019-07-06 Thread Wilfred Sarmiento via bind-users
Hi Mark, Another findings i got in the server is that it intermittently cannot resolve an external domain. Any more idea to what i should be checking here? Thank you, Wil -- This e-mail message (including attachments, if any) is intended for the use of the individual or the entity to whom it

Query CNAME failed

2019-07-03 Thread Wilfred Sarmiento via bind-users
IN A > > ;; ANSWER SECTION: > book.cebupacair.cust.lldns.net. 300 IN CNAME cebupacair-dd.lldns.net. > cebupacair-dd.lldns.net. 60 IN A 68.142.70.27 > cebupacair-dd.lldns.net. 60 IN A 68.142.68.27 > > Mark > > > O

Query CNAME failed

2019-07-03 Thread Wilfred Sarmiento via bind-users
Hi Bind Users, Currently drained my brain troubleshooting where could be the cause of my issue on one of our Authoritative DNS server. When querying a CNAME directly to the server, where a CNAME is pointed to an external domain, results failed with timeout error and no server could be reached.