Re: Query failed (timed out)

2019-11-05 Thread Mark Andrews
The DNS servers for federate-secure.glbaa.barclays.com are *broken* which is what federate.secure.barclays.com points to. They do not respond to queries with EDNS options present and named sends a DNS COOKIE EDNS option by default. You can work around this by specifying server 157.83.102.245 { s

Re: Query failed (timed out)

2019-11-05 Thread Daniel Stirnimann
federate.secure.barclays.com. is a CNAME pointing to federate-secure.glbaa.barclays.com The authoritative name servers for federate-secure.glbaa.barclays.com are broken: glbaa.barclays.com. 900 IN NS ns24.barclays.net. glbaa.barclays.com. 900 IN NS ns22.barclay

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 b