Re: Query failed (timed out)

Thank you Ondrej. Hope this issue will reach Barclays Domain admin. Thank you all for the help and advise. On Wed, 6 Nov 2019, 18:50 Ondřej Surý wrote: > Hi Wilfred, > > BIND is not broken as Mark already pointed out, so we have no plan on > fixing this. > > The DNS load-balancers (most probab

Re: CNAME as an alias to a TXT record

Many thanks for all the responses. For the sake of completeness I am just reporting that every thing is working as expected. On 2019-11-04 12:30 p.m., Computerisms Corporation wrote: Hi, I am wondering if it is possible to create a CNAME in one zone to resolve as a TXT record in another zone

Re: CNAME as an alias to a TXT record

In article , Computerisms Corporation wrote: > Hi, > > I am wondering if it is possible to create a CNAME in one zone to > resolve as a TXT record in another zone. Can't find anything that says > it will work, but can't find any thing that says it won't, either. CNAME isn't type-specific. I

Re: Query failed (timed out)

Hi Wilfred, BIND is not broken as Mark already pointed out, so we have no plan on fixing this. The DNS load-balancers (most probably) that Barclays has deployed need to be fixed to be RFC compliant. Not to mention that dropping the queries is always **BAD** as it opens a bigger window to spoofi

Re: CNAME as an alias to a TXT record

On 04.11.19 12:30, Computerisms Corporation wrote: I am wondering if it is possible to create a CNAME in one zone to resolve as a TXT record in another zone. On 06.11.19 09:48, Matus UHLAR - fantomas wrote: CNAME will not resolve as a TXT. CNAME will make ALL types queries for original query b

Re: CNAME as an alias to a TXT record

On 04.11.19 12:30, Computerisms Corporation wrote: I am wondering if it is possible to create a CNAME in one zone to resolve as a TXT record in another zone. CNAME will not resolve as a TXT. CNAME will make ALL types queries for original query being resolved as the destination Can't find anyth

Re: Query failed (timed out)

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 i

Re: Query failed (timed out)

> 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 issue. There's probably no patch to "resolve" this, because the correct way to fix the problem is at the sourc

Re: Query failed (timed out)

Hi Mark, The workaround works very well, i also got the same response from Daniel of Switch. Thank you very much! *Wil* On Wed, Nov 6, 2019 at 3:52 PM Mark Andrews wrote: > The DNS servers for federate-secure.glbaa.barclays.com are *broken* which > is what federate.secure.barclays.com points

Re: bind-users Digest, Vol 3297, Issue 1

this communication in error, > please notify the sender and delete this E-mail message immediately. > > -- next part -- > An HTML attachment was scrubbed... > URL: > https://lists.isc.org/pipermail/bind-users/attachments/20191106/7228a0d3/attachment-0001.htm &g

Re: Query failed (timed out)

Hi Daniel, 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 issue. Thank you! *Wil* On Wed, Nov 6, 2019 at 3:50 PM Daniel Stirnimann < daniel.stirnim...@switch.