Hi,
as previously announced, the BIND 9.21 (development branch) has changed the
build
system from venerable autotools to meson build system. If you build BIND 9 from
sources
now would be a good time to try building the development version from sources
and report
any issues you find to our
; apt-cache policy bind9
> bind9:
> Installed: 1:9.18.28-1~deb12u2
> Candidate: 1:9.18.28-1~deb12u2
>
> To patch to 9.18.33 Extended Support (ES), what do you recommend in this
> case? Do I have to uninstall the ES version to install the Standard version,
> or can I stay wi
recommend in this case?
Do I have to uninstall the ES version to install the Standard version, or can I
stay with the ES version?
Thank you in advance
Best regards
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this
Hi,
this is a follow-up to the previous email. The change in the repositories will
happen
approximately after 15:00 UTC (17:00 CEST, 08:00 PDT, 11:00 EDT). We will start
upgrading the packages shortly after the time and it will take some time for the
packages to be built and published.
This appl
Hi,
following up on the today's BIND 9 releases:
On next Wednesday (2024-08-28), the following change will get implemented in
ISC repositories (both RPM and DEB):
* 'bind' repository will be upgraded from BIND 9.18 branch (9.18.29) to BIND
9.20 branch (9.20.1)
* 'bind-dev' repository will be u
my config.
From what I read on:
https://bind9.readthedocs.io/en/latest/reference.html#namedconf-statement-checkds
The “checkds” statement, if set to yes, will simply look at the parent NSes
with no need to create/maintain the parental-agents list.
Is this correct ? And also - what version of
:
https://bind9.readthedocs.io/en/latest/reference.html#namedconf-statement-checkds
The “checkds” statement, if set to yes, will simply look at the parent NSes
with no need to create/maintain the parental-agents list.
Is this correct ? And also - what version of BIND was this first introduced
(ex:
9.19.20, 9.19.21, 9.19.22 ) so we can select more precisely which
version we pull?
The Tags for the main branches can be kept as it is and still point to
the latest release, I’m only asking if it would be possible to add new
Tags for the past few minor releases as well.
[1] https
available (9.19.22 as of today).
Would it be possible to include Tags with the minor versions (ex: 9.19.20,
9.19.21, 9.19.22 ) so we can select more precisely which version we pull?
The Tags for the main branches can be kept as it is and still point to the
latest release, I'm only asking
On Sun, 2024-02-11 at 07:34 +, Ole Aamot wrote:
> I respect the ISC.ORG, but you are not treating me or Karl Auer with
> respect in trying to censor work on WikiDNS
Hullo Ole.
I apologise. I thought you were joking. I have no genuine interest in
WikiDNS.
Once again, I apologise for my misund
Tonight I saved DNS -
WikiDNS (version 1.0.0) - available with JSON records))
You both need to stop now.
Ondrej
--
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 11. 2. 2024, at
You both need to stop now.Ondrej--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 11. 2. 2024, at 4:44, Ole Aamot wrote:
On Sun, 2024-02-11 at 01:28 +, Ole Aamot wrote:
> T
On Sun, 2024-02-11 at 01:28 +, Ole Aamot wrote:
> Thanks for your insightful comments and suggestions for WikiDNS
> 1.0.0.
> I welcome feedback and invite you to test WikiDNS 2.1.2
The improvements are certainly comprehensive. The GPL3 licence is a
very welcome choice.
Excellent, I am glad yo
On Sun, 2024-02-11 at 01:28 +, Ole Aamot wrote:
> Thanks for your insightful comments and suggestions for WikiDNS
> 1.0.0.
> I welcome feedback and invite you to test WikiDNS 2.1.2
The improvements are certainly comprehensive. The GPL3 licence is a
very welcome choice.
Under the circumstances
ord_type, record_data)
print("Response from server:", response)
I am attaching the updated WikiDNS 2.1.2, update, client and server written in
Python in this email.
The WikiDNS License is GNU GPLv3 or any later version with owners
Copyright (C) 2024 Aamot Engineering
On Sat, 2024-02-10 at 23:28 +, Ole Aamot wrote:
> Tonight I saved DNS from further bind usage in the Internet Software
> Consortium.
> [...]
> https://en.wikipedia.org/wiki/Draft:WikiDNS
"Submission rejected on 10 February 2024 by CoconutOctopus.
This topic is not sufficiently notable for incl
Tonight I saved DNS from further bind usage in the Internet Software Consortium.
We will in the future just use JSON for records, it is as simple as that, and
serve with Python, update with Python and query JSON.
https://folk.ntnu.no/olekaam/wikidns-client.py (version 1.0.0)
https
You know, whenever I run over a spark plug as I'm driving down the road,
the first thing that goes through my mind is good on them for ruling out
the spark plug as the cause of rough running, and too bad they'll have
to have the valves and rings checked.
On 12/22/23 12:42 AM, Ondřej Surý wrote:
>
ind-9.18.21> sha256sum README.md
080e914decc2ed554d8887b0f719b82736c45380b987f23b3eba4ef7418f03f3 README.md
On 12/21/23 12:24 PM, Fred Morris
wrote:
No, I was correct the first time, but I had the wrong version.
It is a 9.18.9 tarball, not 9.18.21.
d Morris wrote:
>
> No, I was correct the first time, but I had the wrong version. It is a
> 9.18.9 tarball, not 9.18.21. Checksums are correct for that README.md.
>
> On 12/21/23 12:18 PM, Fred Morris wrote:
>>
>> I'm sorry 9.18.9 was the version where I discovered t
No, I was correct the first time, but I had the wrong version. It is a
9.18.9 tarball, not 9.18.21. Checksums are correct for that README.md.
On 12/21/23 12:18 PM, Fred Morris wrote:
>
> I'm sorry 9.18.9 was the version where I discovered that the build
> didn't build the PDF,
I'm sorry 9.18.9 was the version where I discovered that the build
didn't build the PDF, and all it says is
### Building BIND 9
For information about building BIND 9, see the
["Building BIND 9"](doc/arm/build.inc.rst) section in the BIND 9
Administrator Re
I agree! BIND 9.16.21 is working just fine for me on Windows Server 2019 with
either 8 or 12 vCPUs.
Thanks, ISC BIND team.
Richard.
From: Sami Leino
Sent: 17 September 2021 8:49 am
To: Richard T.A. Neal ; bind-us...@isc.org
Subject: VS: BIND 9.16.19 or any version newer than 9.16.15 does not
version newer than 9.16.15 does not start on
Windows Server 2019
Hi Sami,
I’m sorry but I’ve tried to do that again this evening but I can’t get it to
work.
named.exe can take command line arguments to limit the number of vCPUs it will
use, but I can’t get this to work when running named.exe as a
came up
with this workaround in the ticket referenced above, and I've confirmed that it
works on an 8-core test VM that I created:
C:\> sc start named -n 7
Best,
Richard.
From: Sami Leino
Sent: 08 September 2021 8:13 am
To: Richard T.A. Neal ; bind-us...@isc.org
Subject: VS: BIND 9.
Hi there,
On Wed, 8 Sep 2021, Sami Leino wrote:
I will return to this problem with 8 vCPU count. You wrote earlier
that there could be a way to have BIND run a specific number of vCPU
cores?
Have you tried searching something like "windows processor affinity"?
--
73,
Ged.
__
Sami Leino
Lähetetty: torstai 19. elokuuta 2021 12.58
Vastaanottaja: Richard T.A. Neal ; bind-us...@isc.org
Aihe: VS: BIND 9.16.19 or any version newer than 9.16.15 does not start on
Windows Server 2019
Hi Richard,
I did put up brand new, similar Windows 2019 server with 6 vCPU 's. And t
erver can be upgraded also. Thank you for pointing the problem for me!
BR, Sami Leino / Q-Net Oy
Lähettäjä: bind-users Puolesta Richard T.A.
Neal
Lähetetty: torstai 19. elokuuta 2021 9.39
Vastaanottaja: bind-us...@isc.org
Aihe: RE: BIND 9.16.19 or any version newer than 9.16.15 does not sta
.
From: Sami Leino
Sent: 19 August 2021 6:48 am
To: Richard T.A. Neal ; bind-us...@isc.org
Subject: VS: BIND 9.16.19 or any version newer than 9.16.15 does not start on
Windows Server 2019
Hi Richard, and thanks for your reply.
This Windows server 2019 runs on VMware and has 8 vCPU 's. Alt
Hi Richard, and thanks for your reply.
This Windows server 2019 runs on VMware and has 8 vCPU 's. Although any version
newer than 9.16.15 just doesn't want to start. I just tried the newest release
9.16.20 also, with exactly same problem.
BR, Sami Leino / Q-Net Oy
Lähettäjä:
t it's at least a starting point.
Best,
Richard.
From: bind-users On Behalf Of Sami Leino
Sent: 18 August 2021 10:56 am
To: bind-us...@isc.org
Subject: BIND 9.16.19 or any version newer than 9.16.15 does not start on
Windows Server 2019
Hello,
Our NS3.qnet.fi which is Windows Server 2019
Hello,
Our NS3.qnet.fi which is Windows Server 2019, does not start ISC Bind process
with any newer version than 9.16.15
I have tried to update to 9.16.17 , 9.16.18 and the latest 9.16.19, all those
versions refuse to start. Nothing reasonable in event viewer. Always same error
when trying to
On Mon, 21 Jun 2021, John W. Blue via bind-users wrote:
Have you seen the webinar videos on ISC's youtube channel?
https://www.youtube.com/user/ISCdotorg/search?query=DNSSEC
No! I would not have thought to look there for this -- although I learn
all kinds of other things on YT. Many thanks f
ons.
John
From: bind-users on behalf of Brett Delmage
Sent: Monday, June 21, 2021 2:58 PM
To: bind-users
Subject: Best DNSSEC documentation for current version?
I am looking to read the best documentation on DNSSEC
configuration for the current versions on
On Mon, 21 Jun 2021, Ondřej Surý wrote:
you haven’t said the version, but readthedocs.io has a version picker,
so you can go with the version you are interested in (v9.16 and up) with
“latest” referring to the latest stable branch (v9.16.xx).
Thanks for letting me know about this. I seem to
Brett,
you haven’t said the version, but readthedocs.io has a version picker, so you
can go with the version you are interested in (v9.16 and up) with “latest”
referring to the latest stable branch (v9.16.xx).
Ondřej
--
Ondřej Surý (He/Him)
ond...@isc.org
> On 21. 6. 2021, at 21:58, Br
I am looking to read the best documentation on DNSSEC
configuration for the current versions on BIND.
Is this comprehensive and up to date?
https://bind9.readthedocs.io/en/latest/dnssec-guide.html
This doc does not refer to any version - Am I missing that? It seems that
this is an important
Dominik,
please create issue in our GitLab (https://gitlab.isc.org/) and include
full logs (preferably run named with `-d 99` to get most diagnostic
output).
Thanks,
--
Ondřej Surý (He/Him)
ond...@isc.org
> On 17. 5. 2021, at 9:13, Dominik wrote:
>
> Hello,
>
> yesterday
Hello,
yesterday I tried version 9.17.12 because of the new TLS features.
My resolv.conf only contains the local resolver 127.0.0.1 and ::1.
The problem is that the new Bind9 doesn't start without having an
alternative resolver in resolv.conf. It looks like something in the
Bind9 st
> On Nov 10, 2020, at 11:29 PM, Jan Drobil wrote:
>
> Hi,
> will BIND support catalog zones version 2 -
> https://tools.ietf.org/html/draft-ietf-dnsop-dns-catalog-zones-00 ?
> Knot DNS introduces them in version 3 -
> https://www.knot-dns.cz/docs/3.0/singlehtml/#catalog
Hi,
will BIND support catalog zones version 2 -
https://tools.ietf.org/html/draft-ietf-dnsop-dns-catalog-zones-00 ?
Knot DNS introduces them in version 3 -
https://www.knot-dns.cz/docs/3.0/singlehtml/#catalog-zones
--
Jan Drobil
linux admin
===
ACTIVE 24
And for debian, I maintain https://packages.sury.org/bind/ for 9.16, replace
with bind-esv for 9.11 ESV or bind-dev for 9.17 for development version.
Ondrej
--
Ondřej Surý — ISC (He/Him)
> On 10. 11. 2020, at 19:45, John Thurston wrote:
>
>
>> On 11/8/2020 10:18 PM, Rob McEw
On 11/8/2020 10:18 PM, Rob McEwen wrote:
is there an */easier/simpler/* way to get the most common linux
operating systems (Debian, Ubuntu, CentOs, etc) - to a later version of
BIND - beyond what auto-installs when you issue a command like "apt-get
install bind9" - but /without/
On November 9, 2020 7:18:03 AM UTC, Rob McEwen wrote:
>Several weeks ago, Mark Andrews gave me an excellent suggestion about a
>particular BIND feature, but it is a somewhat recent feature that
>started to exist on a version of BIND that isn't yet distributed in the
>
s ago, Mark Andrews gave me an excellent suggestion about
a particular BIND feature, but it is a somewhat recent feature that
started to exist on a version of BIND that isn't yet distributed in
the default/main BIND distributions for many of the most common
linux-based operating systems. I th
Several weeks ago, Mark Andrews gave me an excellent suggestion about a
particular BIND feature, but it is a somewhat recent feature that
started to exist on a version of BIND that isn't yet distributed in the
default/main BIND distributions for many of the most common linux-based
oper
Hello
I built an internal DNS recursive server using version 9.11.4. I set the
recursive client rate limit according to the official tutorial
https://kb.isc.org/docs/aa-01304, the purpose is to prevent excessive client
resolution.
Excuse me
Each server cannot get 200;
Extract quota
.el7.x86_64 #1 SMP Thu Nov 8 23:39:32 UTC
2018
built by make with '--enable-threads' '--with-openssl=/usr/local/openssl'
compiled by GCC 4.8.5 20150623 (Red Hat 4.8.5-36)
compiled with OpenSSL version: OpenSSL 1.1.1d 10 Sep 2019
linked to OpenSSL version: OpenSSL 1.1.1d 10 Se
ent: Wednesday, June 19, 2019 1:28 PM
To: Mayer Hans
Cc: bind-users@lists.isc.org
Subject: Re: version 9.14.2 core dump
Hi Mayer (and other Solaris users),
could you please try following patch:
https://gitlab.isc.org/isc-projects/bind9/merge_requests/2053.patch
on your Solaris boxes with both GCC
...@isc.org
> On 17 Jun 2019, at 17:34, Mayer Hans wrote:
>
>
> Dear All,
>
> My environment:
> Solaris 11.4 on Sparc
> gcc version 5.5.0 (GCC)
> bind 9.14.2
> ./configure '--enable-shared' '--enable-static' '--enable-ipv6'
> On 18 Jun 2019, at 16:43, Witold Krecicki wrote:
>
> W dniu 17.06.2019 o 17:34, Mayer Hans pisze:
> (...)
>> My environment:
>> Solaris 11.4 on Sparc
>> gcc version 5.5.0 (GCC)
> (...)
>
> There's a bug in GCC on Solaris wrt thread-local storage -
W dniu 17.06.2019 o 17:34, Mayer Hans pisze:
(...)
> My environment:
> Solaris 11.4 on Sparc
> gcc version 5.5.0 (GCC)
(...)
There's a bug in GCC on Solaris wrt thread-local storage -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90912
As a fix for now I'd suggest using Solari
Dear All,
My environment:
Solaris 11.4 on Sparc
gcc version 5.5.0 (GCC)
bind 9.14.2
./configure '--enable-shared' '--enable-static' '--enable-ipv6'
'--without-libjson' '--with-gssapi=/usr/bin/krb5-config'
I tried to use bind 9.14.2
So fa
On 4/11/19 9:38 AM, Alan Clegg wrote:
> On 4/10/19 3:53 PM, Chandra Rao wrote:
>> lrwxrwxrwx 1 root root 6 Apr 2 13:30 /var/run -> ../run
>
> So, /var/run is a symlink to /var/run.
>
> That's probably not gonna work to well.
Ok, I'm an idiot.
Ignore me.
(but look at the permissions, etc. on /
On 4/10/19 3:53 PM, Chandra Rao wrote:
> lrwxrwxrwx 1 root root 6 Apr 2 13:30 /var/run -> ../run
So, /var/run is a symlink to /var/run.
That's probably not gonna work to well.
AlanC
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to
Hi Karl,
No.We are not running bind on Linux box with apparmor.
Thanks & Regards,
Chandra M
On Wed, Apr 10, 2019 at 8:40 PM Karl Lovink via bind-users <
bind-users@lists.isc.org> wrote:
> Alan,
>
> Are you running bind on a Linux box with apparmor. Check your apparmor
> configuration: /etc/ap
Hi Alan,
>>You've not shown how much of the /var/run directory structure exists.
Does /var/run exist? What are the permissions on it?
[Chandra] : /var/run directory structure is already exists and following
are the permissions it's having.
While launching the named service with the named user the
On 4/10/19 11:10 AM, Karl Lovink wrote:
> Alan,
>
> Are you running bind on a Linux box with apparmor. Check your apparmor
> configuration: /etc/apparmor.d/usr.sbin.named.
I'm not, but the OP might be.:-)
AlanC
___
Please visit https://lists.isc.o
Alan,
Are you running bind on a Linux box with apparmor. Check your apparmor
configuration: /etc/apparmor.d/usr.sbin.named.
Cheers,
Karl
> On 10 Apr 2019, at 16:31, Alan Clegg wrote:
>
>> On 4/10/19 10:19 AM, Alan Clegg wrote:
>>> On 4/3/19 5:26 AM, Chandra Rao wrote:
>>> While launching the
On 4/10/19 10:19 AM, Alan Clegg wrote:
> On 4/3/19 5:26 AM, Chandra Rao wrote:
>> While launching the named service coming from the latest bind as
>> mentioned below, We have observed that it's is not able to create
>> "/var/run/named" directory with the named user in the cluster. Due to
>> this we
On 4/3/19 5:26 AM, Chandra Rao wrote:
> While launching the named service coming from the latest bind as
> mentioned below, We have observed that it's is not able to create
> "/var/run/named" directory with the named user in the cluster. Due to
> this we are not able to store the files "named.pid"
Hi Niall O'Reilly,
Thanks for the response.
Still we are facing the same issue even after trying with the suggested
usage of the command.
# ps -eaf | grep -i named
root 32198 32197 0 04:59 ?00:00:00 sudo /usr/sbin/named -u
named -c /etc/ClusterDNS.conf -f
named32199 32198 5 04:5
On 3 Apr 2019, at 10:26, Chandra Rao wrote:
> exec /usr/sbin/named -u named -c "/etc/ClusterDNS.conf" -f
You may need to use
sudo /usr/sbin/named -u named ...
or, if you prefer
exec sudo /usr/sbin/named -u named ...
Best regards,
Niall O'Reilly
Hi Team,
Do we have any update on this issue ?
Thanks in Advance.
Regards,
Chandra M
On Wed, Apr 3, 2019 at 2:56 PM Chandra Rao
wrote:
> Hi Team,
>
> Earlier we have used bind-9.9.11-P1 in our platform and upgraded to
> 9.11.5-P4 due to the EOL received for the earlier used vers
Hi Team,
Earlier we have used bind-9.9.11-P1 in our platform and upgraded to
9.11.5-P4 due to the EOL received for the earlier used version.
After upgrading we are facing the below mentioned issue related to named
binary.
While launching the named service coming from the latest bind as mentioned
agday.net/) my domains are affected by
> the EDNS compliance update. I use the RMPs provided by 510 SG
> (https://www.five-ten-sg.com/mapper/bind) The last version is Bind 9.12.3-P1
> this version is ok? Or there is something else that i have to fix on the
> current setup?
>
>
&
Skype: ignios.corp
- Mensaje original -
De: "Reindl Harald"
Para: "gmolano" , "bind-users"
Enviados: Lunes, 28 de Enero 2019 12:54:48
Asunto: Re: DNS FlagDay bind version affected
i doubt that "IgniOS DNS v.1.0.3" is bind 9.12.3-P1
don't confuse rpm pac
Hi to all.
Checking on the website (https://dnsflagday.net/) my domains are affected by
the EDNS compliance update. I use the RMPs provided by 510 SG
(https://www.five-ten-sg.com/mapper/bind) The last version is Bind 9.12.3-P1
this version is ok? Or there is something else that i have to fix
able/even-stable" release numbering
convention. There will be no "alpha" or "beta" releases in the 9.13 branch,
only increasing version numbers. The first stable release from this development
branch will be renamed as 9.14.0. We plan to pull a 9.14.0 stable branch at the
end of 20
Hello All,
I am using BIND 9.10.2-P1.
I have a question.
[Situation]
In order to upgrade the version of BIND, I uninstalled BIND 9.10.2-P1 and
installed BIND 9.11.3.
I started the service, but the startup of the service failed.
? Error code
1067
? Application event log
managed-keys-directory &#
Tom wrote:
>
> What's the reason, that it isn't necessary to run modern version of bind in a
> jail?
chroot is a defence against privilege escalation following a remote code
execution vulnerability. It isn't a very solid defence. And BIND 9 tends
to die of a self-check fa
ns of BIND)".:
What's the reason, that it isn't necessary to run modern version of bind
in a jail?
that named got a complete rewrite and don't share any code with the
times where the quality was so bad that it was highly recommended to
chroot it?
__
the reason, that it isn't necessary to run modern version of bind
in a jail?
Kind regards,
Tom
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
http
I try to build from source this beta version for a test purpose but I am stuck
on this error below.
/usr/bin/install: cannot stat './lwres.3': No such file or directory
/usr/bin/install: cannot stat './lwres_buffer.3': No such file or directory
/usr/bin/install: cannot st
On Mon, Aug 24, 2015 at 07:41:27PM +, HARRIS, RAYMOND D wrote:
> When I query the server for version I get back "version: 9.9.7S5"
>
> The ics.org website lists the most current version as "9.9.7-P2"
Some of ISC's support customers run a limited-release &quo
If you're going to obscure your version _anyway_, might as well put a short
math problem in the text; keep them occupied, slow down the attack. Hey, it's
worth a try... :-)
- Kevin
-Original Message
On 2015-08-24 12:45, Reindl Harald wrote:
Am 24.08.2015 um 21:41 schrieb HARRIS, RAYMOND D:
When I query the server for version I get back “version: 9.9.7S5”
The ics.org website lists the most current version as “9.9.7-P2”
How do I interpret these numbers to ensure I have implemented the
Am 24.08.2015 um 21:41 schrieb HARRIS, RAYMOND D:
When I query the server for version I get back “version: 9.9.7S5”
The ics.org website lists the most current version as “9.9.7-P2”
How do I interpret these numbers to ensure I have implemented the most
current version?
besides that a
When I query the server for version I get back "version: 9.9.7S5"
The ics.org website lists the most current version as "9.9.7-P2"
How do I interpret these numbers to ensure I have implemented the most current
version?
Raymond D. Harris, Jr, CISA
Sr. Auditor -
Please don't reply to a message on the list and change the subject line.
Doing so causes your new topic to show "under" the previous one for
those using mail readers that thread properly, and may cause your
message to be missed altogether if someone has blocked that thread.
Instead, save the l
IPv6 address 2a01:111:f406:2400::13
But it doesn't, so I must be doing something wrong. The client has
(mostly) ipv6 connectivity, but cannot reach 2a01:111::/32. Of course I
could give up and just put the client in the filter- acl.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/
rt 53).
You can find the newest versions of the howto's here:
https://app.younited.com/?shareObject=6e808cfb-1640-d4b6-7d72-6d0bcbeb2e58
Amongst others I have added one line in the bind configuration so the
bind version also resolves dnssec.
I have been using this rpz firewall for a few mont
The nsdiff program examines the old and new versions of a DNS zone, and
outputs the differences as a script for use by BIND's nsupdate program. It
provides a bridge between static zone files and dynamic updates. If you
use BIND 9.7 or 9.8, you can use nsdiff as an alternative to the DNSSEC
inline-s
On 03.10.13 16:42, IT Support wrote:
Hi Mathus one thing more. I´m little bit lost in bind9. Can you tell
me which one those files where is defined the internal o external
host?
no. I would need to see those files to tell you where it is.
Simply check your named.copnf and resursively all incl
Hi Mathus one thing more. I´m little bit lost in bind9. Can you tell me
which one those files where is defined the internal o external host? If
is in mydomain.com.hosts.lan for internal and mydomain.com.hosts for
external I already put them in each configuration file. But I´m still
getting the
On 26.09.13 10:52, IT Support wrote:
Hi Matus thanks for your answer, can you do me a favor? can you tell
me how to looking for that configuration?
only clients that are supposed to get internal private addresses
should be in internal view. "...You mean, that I should to create a
internal and
:50 -0400
> From: br...@wadsworth.org
> To: a...@clegg.com
> Subject: Re: weird perfmonce BIND version 9.6
> CC: bind-users@lists.isc.org
>
>
> Alan,
>
> Apreciate the warning, these options are restricted in our
> public/internet facing servers.
>
> The se
Hi Matus thanks for your answer, can you do me a favor? can you tell me
how to looking for that configuration?
only clients that are supposed to get internal private addresses should
be in internal view. "...You mean, that I should to create a internal
and external record in each view? if this
On 25.09.13 14:58, IT Support wrote:
too many times I´ve got advices about to dns testing using dig
command, but I´m still using ping to check what ip address is
answering to me. In this case i´m testing host2.mydomain.com and i´m
getting the private ip address. I´m wondering how to fix this i
n open recursive resolver
> capable of being used as a DoS amplifier.
>
> Please don't use "any" in these ACLs. Set ACLs that include only the address
> ranges that you control.
>
> This public service announcement brought to you by those that care about the
> Int
nt brought to you by those that care about the
Internet.
(but thanks from upgrading to a relatively new version of BIND)
AlanC
--
Alan Clegg | +1-919-355-8851 | a...@clegg.com
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Hi Chuck, sorry for the mistake.
so i did the dig host2.mydomain.com and this is the result:
host2.mydomain.com @xxx.xxx.xxx.xxx
; <<>> DiG 9.6-ESV-R4 <<>>host2.mydomain.com @xxx.xxx.xxx.xxx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33734
;; flag
Hi--
On Sep 25, 2013, at 12:22 PM, IT Support wrote:
> Hi charles
I'm "Chuck", although I've also answered to worse things than my full name. :-)
> this is what i get from dig
>
> dig host2.mydomain.com
>
> ; <<>> DiG 9.6-ESV-R4 <<>> ost2.mydomain.com
> ;; global options: +cmd
> ;; Got ans
wrote:
On Sep 25, 2013, at 10:58 AM, IT Support wrote:
Hi brothers and sisters.
Hi, anonymous IT Support person-- :-)
I´m getting some weird perfomance on BIND version 9.6 I´m running on debian,
I have internal and external view created. there are records on internal and
external views,
2:58, IT Support wrote:
> >I´m getting some weird perfomance on BIND version 9.6 I´m running
> >on debian, I have internal and external view created. there are
> >records on internal and external views, so the records on external
> >view some of them are working and others
On 25.09.13 12:58, IT Support wrote:
I´m getting some weird perfomance on BIND version 9.6 I´m running
on debian, I have internal and external view created. there are
records on internal and external views, so the records on external
view some of them are working and others not working.
I
Hi brothers and sisters.
I´m getting some weird perfomance on BIND version 9.6 I´m running on
debian, I have internal and external view created. there are records on
internal and external views, so the records on external view some of
them are working and others not working.
I´m testing a
subscriptions to ISC mailing lists or to visit
the list archives.)
---
BIND 9.9-ESV and a New Naming Convention for ESVs
In addition to being the most feature-filled version of BIND
to date, BIND 9.9.3 is also the first version in the
sth...@nethelp.no wrote:
> > I have since learned that you get different version output from dig,
> > named -v, and a dns query and the version statement only affects
> > specific outputs.
>
> What is the difference between using dig and a DNS query?
Dig reports its o
In message <77c3c98b-001a-43c3-a56a-e672d4640...@starionline.com>, Jeff Justice
writes:
> Jeremy, it is exactly as you asked. Apparently the "real" version is display
> ed using certain commands, and the "user-defined" version is displayed in oth
> er places.
1 - 100 of 154 matches
Mail list logo
