Re: Zone file got updated via named process unexpected

2023-12-17 Thread Nick Tait via bind-users
On 17/12/2023 5:30 pm, liudong...@ynu.edu.cn wrote: I found this zone file got updated in about 15 minutes when I made changes or restarted named, and this behavior seems match the docs bind9.readthedocs.io/en/latest/chapter6.html#dynamic-update, but I can confirm I DO NOT configure

RE: unable-resolve-bank=domain

2023-12-17 Thread MEjaz via bind-users
Some additional information 17-Dec-2023 11:14:20.737 queries: debug 3: client @0x7f2a1027d6f8 88.213.90.92#64617 (www.services.online-banking.gslb.sabbnet.com): looking for relevant NSEC 17-Dec-2023 11:14:20.737 queries: debug 3: client @0x7f2a1027d6f8 88.213.90.92#64617

RE: unable-resolve-bank=domain

2023-12-17 Thread MEjaz via bind-users
My queries logs shows the below, [root@ns10 ~]# tail -f /var/log/querylog | grep www.services.online-banking.gslb.sabbnet.com. 17-Dec-2023 11:06:03.438 queries: info: client @0x7f29940013a8 167.86.165.83#64231 (www.services.online-banking.gslb.sabbnet.com): query:

Re: unable-resolve-bank=domain

2023-12-17 Thread Ondřej Surý
> On 17. 12. 2023, at 8:20, MEjaz via bind-users > wrote: > > Any hint would be highly appreciated.. Paraphrasing: Logs or it didn’t happen… Always start with logs. The dig output is useless as we can’t possibly know what is happening inside named on that server. Ondrej -- Ondřej Surý —

Re: unable-resolve-bank=domain

2023-12-17 Thread Marco Moock
Am 17.12.2023 um 10:21:05 Uhr schrieb MEjaz via bind-users: > One of the banking domain www.services.online-banking.gslb.sabbnet.com > unable to > resolve with our primary namservers 212.119.64.2 whearas as my > another server 212.119.64.3