Re: Origin of reverse lookup
* techli...@phpcoderusa.com: > I had my ISP configure a reverse lookup years ago. They say they no > longer offer that service and there is no reverse lookup for my IP. And what exactly is "my IP"? One could hazard a guess based on your message's headers, but it would be easier if you told us. > Any thoughts on how I might resolve this or find who is hosting this > reverse lookup? Have you tried using a utility like "dig" to execute reverse lookups along the responding domain name server chain? Verbose output should offer clues about where the data originates. -Ralph ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Origin of reverse lookup
Hi, I had my ISP configure a reverse lookup years ago. They say they no longer offer that service and there is no reverse lookup for my IP. I keep running into this old reverse lookup and do not know where it is coming from. When I run https://intodns.com/ it shows this reverse lookup and not the one I just configured on my local box. Any thoughts on how I might resolve this or find who is hosting this reverse lookup? Thanks!! ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RE: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
The next Event Log entry on my system immediately after "using 1 UDP listener per interface" is: loading configuration from 'C:\BIND\etc\named.conf' (because that's my BIND installation folder obviously). If I intentionally make a typo in any of my config files (eg named.conf, named.conf.options etc) and try and start the ISC BIND service I get: Windows could not start the ISC BIND service on local computer. Error 1067: The process terminated unexpectedly. And that’s exactly the same error message that you’re getting. Have you tried dropping to a command prompt and then running "named-checkconf" from within the "bin" subfolder of your BIND installation folder? That will tell you if it detects an error in any of your configuration files. I know you may not have changed them between upgrading from 9.16.12 to 9.16.18, but maybe there's something in there that BIND 9.16.12 was OK with but which 9.16.18 is not happy. For example if I intentionally add a simple 'x' at the very end of my named.conf and then run C:\BIND\bin\named-checkconf I get: C:\BIND\bin>named-checkconf C:\BIND\etc\named.conf:8: unknown option 'x' C:\BIND\etc\named.conf:8: unexpected token near end of file Richard. From: bind-users On Behalf Of Peter via bind-users Sent: 18 June 2021 5:49 pm To: bind-users@lists.isc.org Subject: Re: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14) It shows 17 information with the last showing "using 1 UDP listener per interface" maybe it don't like my intel VLAN's? ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Only zones with wildcards affected on authoritative servers
John, yes, all ISC packages have fix to W problem either as a full release or a patch set. Ondřej -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 18. 6. 2021, at 21:33, John Thurston wrote: > > On 6/17/2021 11:03 PM, Ondřej Surý wrote: >> # Are the ISC packages affected? >> The packages with the hotfix applied were pushed into the repository and are >> either already built >> or are building and will be available shortly > > The Ubuntu and Centos Copr packages are showing different version numbers, > though I suspect they both contain the updated code. Can someone confirm my > suspicion? > > > The CentOS 8 Copr went from > 9.16.17-1.1.el8 > to > 9.16.17-1.2.el8 > > While the Ubuntu "Personal Package Archive" ppa:isc/bind went from > 9.16.17-1 > to > 9.16.18-1 > > from 'named -v' the two return > BIND 9.16.17 (Stable Release) > BIND 9.16.18-Ubuntu (Stable Release) > > > -- > Do things because you should, not just because you can. > > John Thurston907-465-8591 > john.thurs...@alaska.gov > Department of Administration > State of Alaska > ___ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Only zones with wildcards affected on authoritative servers
On 6/17/2021 11:03 PM, Ondřej Surý wrote: # Are the ISC packages affected? The packages with the hotfix applied were pushed into the repository and are either already built or are building and will be available shortly The Ubuntu and Centos Copr packages are showing different version numbers, though I suspect they both contain the updated code. Can someone confirm my suspicion? The CentOS 8 Copr went from 9.16.17-1.1.el8 to 9.16.17-1.2.el8 While the Ubuntu "Personal Package Archive" ppa:isc/bind went from 9.16.17-1 to 9.16.18-1 from 'named -v' the two return BIND 9.16.17 (Stable Release) BIND 9.16.18-Ubuntu (Stable Release) -- Do things because you should, not just because you can. John Thurston907-465-8591 john.thurs...@alaska.gov Department of Administration State of Alaska ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
do I need to configure a Caching Server
I am building a home PHP hosting server for learning. I have a
commercial connection to the Internet so no blocked ports and my ISP
allows servers.
I believe I only need a Primary Master Server. Is this the case?
My question is, do I need to configure a Caching Server?
In /etc/bind/named.conf.options:
[...]
forwarders {
1.2.3.4;
5.6.7.8;
};
[...]
Do I need to set the forwarders?
Thank you for all your help!!
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
It shows 17 information with the last showing "using 1 UDP listener per interface" maybe it don't like my intel VLAN's? On 18/06/2021 5:21 pm, Richard T.A. Neal wrote: When you say “in Application logs show fine” – how far does named actually get (if at all)? For example whenever I (re)start the “ISC BIND” service on my Windows server I get **loads** of entries in the Application log, starting with these three: starting BIND 9.16.18 (Stable Release) running on Windows 10 0 build 17763 1879 for x64 [it’s actually Windows Server being misdetected as Windows 10, but the build numbers are correct] built with 'with-tools-version=15.0 with-platform-toolset=v141 with-platform-version=10.0.17763.0 with-vcredist=C:/Program\ Files\ (x86)/Microsoft\ Visual\ Studio/2017/BuildTools/VC/Redist/MSVC/14.16.27012/vcredist_x64.exe with-openssl=C:/OpenSSL with-libxml2=C:/libxml2 with-libuv=C:/libuv without-python with-system-tests x64' Richard. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RE: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
When you say “in Application logs show fine” – how far does named actually get (if at all)? For example whenever I (re)start the “ISC BIND” service on my Windows server I get *loads* of entries in the Application log, starting with these three: starting BIND 9.16.18 (Stable Release) running on Windows 10 0 build 17763 1879 for x64 [it’s actually Windows Server being misdetected as Windows 10, but the build numbers are correct] built with 'with-tools-version=15.0 with-platform-toolset=v141 with-platform-version=10.0.17763.0 with-vcredist=C:/Program\ Files\ (x86)/Microsoft\ Visual\ Studio/2017/BuildTools/VC/Redist/MSVC/14.16.27012/vcredist_x64.exe with-openssl=C:/OpenSSL with-libxml2=C:/libxml2 with-libuv=C:/libuv without-python with-system-tests x64' Richard. From: bind-users On Behalf Of Peter via bind-users Sent: 18 June 2021 3:51 pm To: bind-users@lists.isc.org Subject: Re: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14) I go back to BIND 9.17.12 and is starts fine install BIND 9.16.18 changed log on to “local system account” like I have done for years go to start BIND get error 1067 in: system logs The ISC BIND service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6 milliseconds: Restart the service. And in Application logs show fine Maybe its just windows 10 pro? Or is it possible to have bind coded to no longer run in win 10? On 18/06/2021 3:08 pm, Richard T.A. Neal wrote: ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Limit actions on control channel?
It ought to be possible to write a front-end to listen on the standard control channel and only forward (properly-keyed) 'status' requests to the "real" port that BIND listens to. >From looking at the RNDC exchange via Wireshark however, you'd have to adapt >some of BIND's code that does the encryption / key-signing of RNDC requests. >Still, for us users, that might be safer -- and more update resistant -- than >modifying BIND itself. On Thu, 17 Jun 2021 11:48:36 -0800 John Thurston wrote: > I see I can define (using the 'controls' statement) a 'read-only' inet > channel. I suspect I could define a couple of channels on the same > address if I put them on different ports. Is there a way to define a > single 'read-write' channel, and then limit certain keys to read-only > access on it? > > Here's the scenario: > > I'd like to have a single control channel listening (on port 953, for > example). I'd like to say the key named "foo" can do lots of things, but > the key named "bar" can only submit a "status" message. This would let > our monitoring application ask for "status" without also letting it ask > for "reload" or "flushname". > ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
I go back to BIND 9.17.12 and is starts fine install BIND 9.16.18 changed log on to “local system account” like I have done for years go to start BIND get error 1067 in: system logs The ISC BIND service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6 milliseconds: Restart the service. And in Application logs show fine Maybe its just windows 10 pro? Or is it possible to have bind coded to no longer run in win 10? On 18/06/2021 3:08 pm, Richard T.A. Neal wrote: On 18/06/2021 2:48 pm, Peter wrote: Even BIND9.16.18 will not run on windows 10 same error I can't reproduce this error - I've just successfully upgraded from BIND 9.16.15 to BIND 9.16.18 on my Windows (2019) server. Do you see a more detailed error in Computer Management > Windows Logs > Application? If your Application log is too busy you can also filter by event source "named" to remove some of the noise. Richard. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
Neither can we. Testing the Windows release is part of release process and both 9.16 and 9.17 passed the test suite. -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 18. 6. 2021, at 16:08, Richard T.A. Neal wrote: > > On 18/06/2021 2:48 pm, Peter wrote: > >> Even BIND9.16.18 will not run on windows 10 same error > > I can't reproduce this error - I've just successfully upgraded from BIND > 9.16.15 to BIND 9.16.18 on my Windows (2019) server. > > Do you see a more detailed error in Computer Management > Windows Logs > > Application? > > If your Application log is too busy you can also filter by event source > "named" to remove some of the noise. > > Richard. > ___ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RE: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
On 18/06/2021 2:48 pm, Peter wrote: > Even BIND9.16.18 will not run on windows 10 same error I can't reproduce this error - I've just successfully upgraded from BIND 9.16.15 to BIND 9.16.18 on my Windows (2019) server. Do you see a more detailed error in Computer Management > Windows Logs > Application? If your Application log is too busy you can also filter by event source "named" to remove some of the noise. Richard. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
Even BIND9.16.18 will not run on windows 10 same error On 18/06/2021 2:21 pm, Ondřej Surý wrote: Hi Peter, the Windows support in 9.17 has been discontinued (as discussed on this very mailing list). So, while technically the BIND 9.17.14/9.17.15 still includes the Windows binaries, the code has been removed in the git repository, and the issue you are experiencing will not get a fix. If you want to keep running BIND 9 on Windows, you will have to downgrade to the lastest stable 9.16 release. Ondrej -- Ondřej Surý (He/Him) ond...@isc.org On 18. 6. 2021, at 14:46, Peter via bind-users wrote: Well I don't know about anyone else but BIND 9.17.14 did not want to start in win 10 “windows could not start the ISC BIND service on local computer Error 1067: the process terminated unexpectedly.” ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
Hi Peter, the Windows support in 9.17 has been discontinued (as discussed on this very mailing list). So, while technically the BIND 9.17.14/9.17.15 still includes the Windows binaries, the code has been removed in the git repository, and the issue you are experiencing will not get a fix. If you want to keep running BIND 9 on Windows, you will have to downgrade to the lastest stable 9.16 release. Ondrej -- Ondřej Surý (He/Him) ond...@isc.org > On 18. 6. 2021, at 14:46, Peter via bind-users > wrote: > > Well I don't know about anyone else but BIND 9.17.14 did not want to start in > win 10 “windows could not start the ISC BIND service on local computer Error > 1067: the process terminated unexpectedly.” > ___ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14
Well I don't know about anyone else but BIND 9.17.14 did not want to start in win 10 “windows could not start the ISC BIND service on local computer Error 1067: the process terminated unexpectedly.” ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Only zones with wildcards affected on authoritative servers (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
Hi again, let me give you quick update again: the development and support teams has found other use cases that would affect both `w` and `W` letters in authoritative zones. The linked issue currently talks just about the wildcards and we are going to update the issue shortly, but I wanted to give you an update in case you already read the issue (and/or my previous email). Ondrej -- Ondřej Surý (He/Him) ond...@isc.org > On 18. 6. 2021, at 9:03, Ondřej Surý wrote: > > Hi, > > let me add more details to the issue. > > # Who’s affected > > Authoritative server operators operating zones with wildcard records (f.e. > *.example.com) > > # What’s affected > > Queries hitting the wildcard records with capital `W` > > # How to test? > > dig IN A W.example.com @127.0.0.1 > > You need to adjust this to match your zone name, server IP address and the > rrclass and rrtype of the wildcard record. > > # Is there a hotfix? > > The patch to fix this issue is available at: > https://gitlab.isc.org/isc-projects/bind9/-/commit/52cc9ff372ba637289d1e8f35d1f3f35d46ea25f.patch > > # Are the ISC packages affected? > > The packages with the hotfix applied were pushed into the repository and are > either already built > or are building and will be available shortly > > # When there will be official upstream release fixing this? > > We are working on preparing the release tarball as of this moment and the > fixed tarballs will be published as soon as they are ready. > > Sorry for any inconvenience this might have caused, we wish we would have > caught this during our extensive testing, but alas we didn’t. > > Thanks, > Ondrej > -- > Ondřej Surý (He/Him) > ond...@isc.org > >> On 18. 6. 2021, at 5:56, Michael McNally wrote: >> >> Dear BIND users: >> >> Yesterday, 16 June 2021, we released monthly maintenance snapshot releases of >> our currently supported release branches of BIND. >> >> Specifically, we released BIND 9.11.33, 9.16.17, and 9.17.14 >> >> There's no way to say this that isn't embarrassing, but only after the >> release >> was an error in a recently optimized routine discovered by a user -- an error >> that will definitely cause operational problems for almost all server >> operators >> who upgrade to either of these affected versions: >> >> - BIND 9.16.17 >> - BIND 9.17.14 >> >> BIND 9.11.33 is NOT affected. >> >> If you have not yet updated to the 16 June releases, we ask that you hold off >> on any plans to install 9.16.17 or 9.17.14 until replacement releases can be >> prepared and tested. >> >> The specific issue in question is being tracked in our issue tracker: >> >> https://gitlab.isc.org/isc-projects/bind9/-/issues/2779 >> >> and more information about our plans for issuing replacement releases will be >> provided later; at the moment our priority is getting the news to parties as >> quickly as possible so that those who have not already adopted the new >> releases >> can postpone until corrected versions are available. >> >> Michael McNally >> Internet Systems Consortium >> ___ >> Please visit https://lists.isc.org/mailman/listinfo/bind-users to >> unsubscribe from this list >> >> ISC funds the development of this software with paid support subscriptions. >> Contact us at https://www.isc.org/contact/ for more information. >> >> >> bind-users mailing list >> bind-users@lists.isc.org >> https://lists.isc.org/mailman/listinfo/bind-users > ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Only zones with wildcards affected on authoritative servers (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
Hi, let me add more details to the issue. # Who’s affected Authoritative server operators operating zones with wildcard records (f.e. *.example.com) # What’s affected Queries hitting the wildcard records with capital `W` # How to test? dig IN A W.example.com @127.0.0.1 You need to adjust this to match your zone name, server IP address and the rrclass and rrtype of the wildcard record. # Is there a hotfix? The patch to fix this issue is available at: https://gitlab.isc.org/isc-projects/bind9/-/commit/52cc9ff372ba637289d1e8f35d1f3f35d46ea25f.patch # Are the ISC packages affected? The packages with the hotfix applied were pushed into the repository and are either already built or are building and will be available shortly # When there will be official upstream release fixing this? We are working on preparing the release tarball as of this moment and the fixed tarballs will be published as soon as they are ready. Sorry for any inconvenience this might have caused, we wish we would have caught this during our extensive testing, but alas we didn’t. Thanks, Ondrej -- Ondřej Surý (He/Him) ond...@isc.org > On 18. 6. 2021, at 5:56, Michael McNally wrote: > > Dear BIND users: > > Yesterday, 16 June 2021, we released monthly maintenance snapshot releases of > our currently supported release branches of BIND. > > Specifically, we released BIND 9.11.33, 9.16.17, and 9.17.14 > > There's no way to say this that isn't embarrassing, but only after the release > was an error in a recently optimized routine discovered by a user -- an error > that will definitely cause operational problems for almost all server > operators > who upgrade to either of these affected versions: > > - BIND 9.16.17 > - BIND 9.17.14 > > BIND 9.11.33 is NOT affected. > > If you have not yet updated to the 16 June releases, we ask that you hold off > on any plans to install 9.16.17 or 9.17.14 until replacement releases can be > prepared and tested. > > The specific issue in question is being tracked in our issue tracker: > > https://gitlab.isc.org/isc-projects/bind9/-/issues/2779 > > and more information about our plans for issuing replacement releases will be > provided later; at the moment our priority is getting the news to parties as > quickly as possible so that those who have not already adopted the new > releases > can postpone until corrected versions are available. > > Michael McNally > Internet Systems Consortium > ___ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
