Recursive Client Rate limiting in BIND applicable in forward mode
Hello Is the function of Recursive Client Rate limiting in BIND applicable in forward mode? My concern is that the client request is too large, resulting in a forward in the global limit my request, such as 8.8.8.8 Thank you___ 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: New BIND releases ... 9.16.4: build, 'fatal error: lmdb.h: No such file or directory'
> but whether lmdb inclusion/usage now _functions_ correctly with that^ > cleanup, i have yet to verify. > checking now ... iiuc @ https://bind9.readthedocs.io/en/latest/manpages.html "The configuration is saved in a file called viewname.nzf (or, if named(8) is compiled with liblmdb, an LMDB database file called viewname.nzd)." the 'nzd2nzf' system/nzd2nzf/prereq.sh if [ -z "$NZD" ]; then echo_i "This test requires LMDB support (--with-lmdb)" exit 255 fi tests that lmdb function -- 1st to create, then convert, the .nzd. complete? dunno ... in any case, with that^ workaround, lmdb test looks ok sh run.sh nzd2nzf S:nzd2nzf:2020-06-18T22:10:47-0700 T:nzd2nzf:1:A A:nzd2nzf:System test nzd2nzf I:nzd2nzf:PORTRANGE:5300 - 5399 I:nzd2nzf:starting servers I:nzd2nzf:querying for non-existing zone data (1) I:nzd2nzf:adding a new zone into default NZD using rndc addzone (2) I:nzd2nzf:querying for existing zone data (3) I:nzd2nzf:stopping ns1 I:nzd2nzf:dumping _default.nzd to _default.nzf (4) I:nzd2nzf:checking that _default.nzf contains the expected content (5) I:nzd2nzf:deleting _default.nzd database I:nzd2nzf:starting ns1 which should migrate the .nzf to .nzd I:nzd2nzf:querying for zone data from migrated zone config (6) I:nzd2nzf:exit status: 0 I:nzd2nzf:stopping servers R:nzd2nzf:PASS E:nzd2nzf:2020-06-18T22:10:54-0700 ___ 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: New BIND releases ... 9.16.4: build, 'fatal error: lmdb.h: No such file or directory'
${LMDB_CFLAGS} is missing from make/includes.in or bin/named/Makefile.in
diff --git a/make/includes.in b/make/includes.in
index 9ff1bd8cf1..9eaf1d3dd5 100644
--- a/make/includes.in
+++ b/make/includes.in
@@ -28,7 +28,7 @@ ISCCFG_INCLUDES = @BIND9_ISCCFG_BUILDINCLUDE@ \
DNS_INCLUDES = @BIND9_DNS_BUILDINCLUDE@ \
-I${top_srcdir}/lib/dns/include \
${FSTRM_CFLAGS} ${PROTOBUF_C_CFLAGS} \
- ${OPENSSL_CFLAGS}
+ ${OPENSSL_CFLAGS} ${LMDB_CFLAGS}
NS_INCLUDES = @BIND9_NS_BUILDINCLUDE@ \
-I${top_srcdir}/lib/ns/include
As for ‘lib64’ vs ‘lib' the complier should adjust the -L paths to match the
architecture as needed usually by appending “/../lib64” to account for given
path being a symbolic link.
The pkg-config output is architecture dependent and it should be architecture
independent.
> On 19 Jun 2020, at 03:25, PGNet Dev wrote:
>
> this
>
> configure.ac
> AC_MSG_CHECKING(for lmdb library)
> AC_ARG_WITH(lmdb,
> AS_HELP_STRING([--with-lmdb[=PATH]],
> [build with LMDB library [yes|no|path]]),
> use_lmdb="$withval", use_lmdb="auto")
>
> have_lmdb=""
> case "$use_lmdb" in
> no)
> LMDB_LIBS=""
> ;;
> auto|yes)
> for d in /usr /usr/local /opt/local
> do
> if test -f "${d}/include/lmdb.h"
> then
> if test ${d} != /usr
> then
> LMDB_CFLAGS="-I ${d}/include"
> !!LMDB_LIBS="-L${d}/lib"
> fi
> have_lmdb="yes"
> fi
> done
> ;;
> *)
> if test -f "${use_lmdb}/include/lmdb.h"
> then
> LMDB_CFLAGS="-I${use_lmdb}/include"
> !!LMDB_LIBS="-L${use_lmdb}/lib"
> have_lmdb="yes"
> else
> AC_MSG_ERROR([$use_lmdb/include/lmdb.h not found.])
> fi
> ;;
> esac
>
>
> is naive. it ignores commonplace multiarch support.
>
>
>
> with =path enabled on config, generated Makefile is just wrong
>
> egrep "^LMDB" Makefile
> LMDB_CFLAGS = -I/usr/local/lmdb/include
> LMDB_LIBS = -L/usr/local/lmdb/lib none required
>
>
>
> bind advertises
>
> ./configure --help | grep -i LMDB
> --with-lmdb=PATHbuild with LMDB library [yes|no|path]
>
> it simply fails to work as advertised.
>
>> you can use and adjust the .pc file from any Linux distribution package
>
> of course you can.
>
> it's here
>
> pkg-config --libs --cflags lmdb
> -I/usr/local/lmdb/include -L/usr/local/lmdb/lib64 -llmdb
>
>> LMDB support in BIND 9 comes with pkg-config support too
>
> there's NO such option advertised by bind configure, as
>
> LMDB_CFLAGS
> C compiler flags for LMDB, overriding pkg-config
> LMDB_LIBS
> linker flags for LMDB, overriding pkg-config
>
> it's simply not used by this bind build
>
> grep PKG_CHECK `grep -rln PKG_CHECK .` | grep -i lmdb
> (empty)
>
> & no mention at all of it in source
>
> grep -i lmdb `grep -rlni lmdb .` | grep -i pkg
> (empty)
>
> this
>
> --with-openssl=/usr/local/openssl
>
> works.
> this,
>
> --with-lmdb=/usr/local/lmdb
>
> does not.
>
> That has _nothing_ to do with 'LMDB upstream'
>
>
>> Did you came to get help or to argue?
>
> neither.
>
>> It’s really not our fault the LMDB upstream decided to make it hard to use
>> the library.
>
> ::facepalm::
>
>
> this
>
> tree /usr/local/lmdb
> /usr/local/lmdb
> ...
> ├── include
> │ └── lmdb.h
> ...
> ├── lib64
> │ ├── liblmdb.a
> │ └── liblmdb.so
> ...
>
> is about as simple as it gets.
>
> fix it, remove it, or leave it as is -- your product, your choice.
>
> good luck.
> ___
> 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
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
Re: New BIND releases ... 9.16.4: build, 'fatal error: lmdb.h: No such file or directory'
this
configure.ac
AC_MSG_CHECKING(for lmdb library)
AC_ARG_WITH(lmdb,
AS_HELP_STRING([--with-lmdb[=PATH]],
[build with LMDB library [yes|no|path]]),
use_lmdb="$withval", use_lmdb="auto")
have_lmdb=""
case "$use_lmdb" in
no)
LMDB_LIBS=""
;;
auto|yes)
for d in /usr /usr/local /opt/local
do
if test -f "${d}/include/lmdb.h"
then
if test ${d} != /usr
then
LMDB_CFLAGS="-I ${d}/include"
!! LMDB_LIBS="-L${d}/lib"
fi
have_lmdb="yes"
fi
done
;;
*)
if test -f "${use_lmdb}/include/lmdb.h"
then
LMDB_CFLAGS="-I${use_lmdb}/include"
!! LMDB_LIBS="-L${use_lmdb}/lib"
have_lmdb="yes"
else
AC_MSG_ERROR([$use_lmdb/include/lmdb.h not found.])
fi
;;
esac
is naive. it ignores commonplace multiarch support.
with =path enabled on config, generated Makefile is just wrong
egrep "^LMDB" Makefile
LMDB_CFLAGS = -I/usr/local/lmdb/include
LMDB_LIBS = -L/usr/local/lmdb/lib none required
bind advertises
./configure --help | grep -i LMDB
--with-lmdb=PATHbuild with LMDB library [yes|no|path]
it simply fails to work as advertised.
> you can use and adjust the .pc file from any Linux distribution package
of course you can.
it's here
pkg-config --libs --cflags lmdb
-I/usr/local/lmdb/include -L/usr/local/lmdb/lib64 -llmdb
> LMDB support in BIND 9 comes with pkg-config support too
there's NO such option advertised by bind configure, as
LMDB_CFLAGS
C compiler flags for LMDB, overriding pkg-config
LMDB_LIBS
linker flags for LMDB, overriding pkg-config
it's simply not used by this bind build
grep PKG_CHECK `grep -rln PKG_CHECK .` | grep -i lmdb
(empty)
& no mention at all of it in source
grep -i lmdb `grep -rlni lmdb .` | grep -i pkg
(empty)
this
--with-openssl=/usr/local/openssl
works.
this,
--with-lmdb=/usr/local/lmdb
does not.
That has _nothing_ to do with 'LMDB upstream'
> Did you came to get help or to argue?
neither.
> It’s really not our fault the LMDB upstream decided to make it hard to use
> the library.
::facepalm::
this
tree /usr/local/lmdb
/usr/local/lmdb
...
├── include
│ └── lmdb.h
...
├── lib64
│ ├── liblmdb.a
│ └── liblmdb.so
...
is about as simple as it gets.
fix it, remove it, or leave it as is -- your product, your choice.
good luck.
___
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: New BIND releases ... 9.16.4: build, 'fatal error: lmdb.h: No such file or directory'
On 6/18/20 6:34 AM, Matt Pallissard wrote: > I'd imagine you want CPPFLAGS here. or you can export C_INCLUDE_PATH ... > Edit: `s/CPPFLAGS/CFLAGS` specifically adding '-I/usr/local/lmdb/include' to $CFLAGS makes the build unhappy, here. but, yep! ... there _is_ hoop-jumping that appears to workaround the WONTFIX silliness^^ ... with lmdb installed as tree /usr/local/lmdb /usr/local/lmdb ├── bin │ ├── mdb_copy │ ├── mdb_drop │ ├── mdb_dump │ ├── mdb_load │ └── mdb_stat ├── include │ └── lmdb.h ├── lib ├── lib64 │ ├── liblmdb.a │ └── liblmdb.so ├── man └── share └── man └── man1 ├── mdb_copy.1 ├── mdb_drop.1 ├── mdb_dump.1 ├── mdb_load.1 └── mdb_stat.1 setting @ bind configure --with-lmdb=/usr/local/lmdb to avoid checking for lmdb library... configure: error: include/lmdb.h not found. and to ensure the feature is (at least) _reported_ as enabled ... === Configuration summary: --- Optional features enabled: ... LMDB database to store configuration for 'addzone' zones (--with-lmdb) ... --- Features disabled or unavailable on this platform: ... then just this CPPFLAGS= ... -I/usr/local/lmdb/include ... LDFLAGS=... -L/usr/local/lmdb/lib64 -llmdb ... is sufficient add'n to general flags still to make add'l adjustments. namely, to just completely circumvent the src code mess that results in, LMDB_CFLAGS = -I/usr/local/lmdb/include LMDB_LIBS = -L/usr/local/lmdb/lib none required and build breakage, applying to clean source, patch << 'EOF' --- configure.ac.ORIG 2020-06-10 14:01:43.0 -0700 +++ configure.ac2020-06-18 09:45:42.142523855 -0700 @@ -1274,6 +1274,8 @@ else AC_MSG_RESULT(no) fi +LMDB_CFLAGS="-I/usr/local/lmdb/include" +LMDB_LIBS="-L/usr/local/lmdb/lib64 -llmdb" AC_SUBST([LMDB_CFLAGS]) AC_SUBST([LMDB_LIBS]) EOF then, of course, ./autogen.sh now, after config, correctly s|^LMDB_CFLAGS =.*|LMDB_CFLAGS = -I/usr/local/lmdb/include|g s|^LMDB_LIBS =.*|LMDB_LIBS = -L/usr/local/lmdb/lib64 -llmdb|g on subsequent build, there's no longer any 'fatal error', In file included from server.c:131: /usr/local/src/bind-9.16.4/lib/dns/include/dns/lmdb.h:12:10: fatal error: lmdb.h: No such file or directory 12 | #include | ^~~~ compilation terminated. and, on install, named runs/functions named -v BIND 9.16.4 (Stable Release) lmdb lib is linked, ldd `which named` | grep lmdb liblmdb.so => /usr/local/lmdb/lib64/liblmdb.so (0x7fedf088b000) but whether lmdb inclusion/usage now _functions_ correctly with that^ cleanup, i have yet to verify. checking now ... ___ 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: A And Cname-record
But if there is a possibly relevant spelling error, it would be helpful to point out exactly where the error is rather than just saying “check your spelling”. Our eyes frequently see what we expect to see and therefore don’t see the error, even when told there is an error. -- Larry Stone lston...@stonejongleux.com > On Jun 18, 2020, at 9:29 AM, Chuck Aurora wrote: > > On 2020-06-18 06:41, Ondřej Surý wrote: >> Jukka and others, >> I would prefer if we didn’t scold people for typos on the mailing list. The >> typo >> in the message had no impact on the question itself, and here, we are trying >> to build community that’s welcoming to newcomers to the wonderful world >> of DNS. > > Is it a wonderful world? :) > > Anyway, the vast majority of errors posted here DO boil down to things like > the typos and syntax niceties (trailing dot) that Jukka pointed out. Granted, > in this case that was obviously an email typo, not copied exactly from the > zone file, but I'd simply suggest that pointing out a typo is not "scolding." > It's often hard for ME to see MY typos, because I know what I meant to type; > but for fresh eyes they are much easier to spot. > ___ > 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: A And Cname-record
On 2020-06-18 06:41, Ondřej Surý wrote: Jukka and others, I would prefer if we didn’t scold people for typos on the mailing list. The typo in the message had no impact on the question itself, and here, we are trying to build community that’s welcoming to newcomers to the wonderful world of DNS. Is it a wonderful world? :) Anyway, the vast majority of errors posted here DO boil down to things like the typos and syntax niceties (trailing dot) that Jukka pointed out. Granted, in this case that was obviously an email typo, not copied exactly from the zone file, but I'd simply suggest that pointing out a typo is not "scolding." It's often hard for ME to see MY typos, because I know what I meant to type; but for fresh eyes they are much easier to spot. ___ 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: A And Cname-record
May I suggest the following?: If you are an individual that is so pedantic that seeing a spelling error causes you to lose sleep or have other soul searing consternation, send an email (gently worded) to the poster only. Please also be encouraging to that individual pointing out that these types of errors happen and will not cause loss of their immortal soul. As Ondrej points out, we are trying to build community that's welcoming to newcomers to the wonderful world of DNS. I remember when I first subscribed to this list being terrified of posting after reading several rather terse replies. I've since gotten a bit thicker skin. I've learned a lot from this list. However, it's not for the timid. Please be considerate in the wording of your replies. With my lack of typing skills, my lack of spelling skills, and my lack of grammar skills, it's a small wonder that anything I post on this list is understood. Couple that with most readers not having english as a first language and it quickly becomes a miracle! My somewhat simpler interpretation of that error: if during the named loading process a zone produces an error that says CNAME and other data, my experience has been that the zone being loaded contains an A record and one or more CNAME records with the same owner value (hostname). That's not allowed under the RFC documents for bind. e.g. remtest IN A 100.64.0.2 remtest IN CNAME temp.example.com. -OR- remtest IN CNAME temp.example.com. remtest IN CNAME temp001.example.com. Both examples are not allowed under the RFCs. Bob ___ 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: New BIND releases ... 9.16.4: build, 'fatal error: lmdb.h: No such file or directory'
On 2020-06-18T06:34:12 -0700, Matt Pallissard wrote: > Response in-line. > > > build now fails @ "fatal error: lmdb.h: No such file or directory" > > > > ... > > libtool: compile: /usr/bin/gcc-10 -include > > /usr/local/src/bind-9.16.4/config.h -I/usr/local/src/bind-9.16.4 -I../.. > > -I./include -I./unix/include -I. > > -I/usr/local/src/bind-9.16.4/lib/ns/include -I../../lib/ns/include > > -I/usr/local/src/bind-9.16.4/lib/dns/include -I../../lib/dns/include > > -I/usr/local/openssl11/include > > -I/usr/local/src/bind-9.16.4/lib/bind9/include -I../../lib/bind9/include > > -I/usr/local/src/bind-9.16.4/lib/isccfg/include -I../../lib/isccfg/include > > -I/usr/local/src/bind-9.16.4/lib/isccc/include -I../../lib/isccc/include > > -I/usr/local/src/bind-9.16.4/lib/isc/include -I../../lib/isc > > -I../../lib/isc/include -I../../lib/isc/unix/include > > -I../../lib/isc/pthreads/include -I/usr/local/openssl11/include > > -I/usr/include/json-c -I/usr/include/libxml2 -I/usr/local/include -O3 -Wall > > -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables > > -fmessage-length=0 -grecord-gcc-switches -march=native -mtune=native -fPIC > > -DPIC -D_GNU_SOURCE -fno-strict-aliasing -Wall -pthread -fPIC -W -Wall > > -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wformat -Wpointer-arith > > -Wno-missing-field-initializers -fno-strict-aliasing -DPRODUCT=\"BIND\" > > -DVERSION=\"9.16.4\" -c ./server.c -fPIC -DPIC -o .libs/server.o > > In file included from ./server.c:131: > > There is no `-I/usr/local/lmdb/include` here > > > echo $CPPFLAGS > > -I/usr/local/include -I/usr/local/openssl11/include > > -I/usr/local/lmdb/include -I/usr/include > > I'd imagine you want CPPFLAGS here. or you can export C_INCLUDE_PATH Edit: `s/CPPFLAGS/CFLAGS` Matt Pallissrd signature.asc Description: PGP signature ___ 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: New BIND releases ... 9.16.4: build, 'fatal error: lmdb.h: No such file or directory'
Response in-line. > build now fails @ "fatal error: lmdb.h: No such file or directory" > > ... > libtool: compile: /usr/bin/gcc-10 -include > /usr/local/src/bind-9.16.4/config.h -I/usr/local/src/bind-9.16.4 -I../.. > -I./include -I./unix/include -I. -I/usr/local/src/bind-9.16.4/lib/ns/include > -I../../lib/ns/include -I/usr/local/src/bind-9.16.4/lib/dns/include > -I../../lib/dns/include -I/usr/local/openssl11/include > -I/usr/local/src/bind-9.16.4/lib/bind9/include -I../../lib/bind9/include > -I/usr/local/src/bind-9.16.4/lib/isccfg/include -I../../lib/isccfg/include > -I/usr/local/src/bind-9.16.4/lib/isccc/include -I../../lib/isccc/include > -I/usr/local/src/bind-9.16.4/lib/isc/include -I../../lib/isc > -I../../lib/isc/include -I../../lib/isc/unix/include > -I../../lib/isc/pthreads/include -I/usr/local/openssl11/include > -I/usr/include/json-c -I/usr/include/libxml2 -I/usr/local/include -O3 -Wall > -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables > -fmessage-length=0 -grecord-gcc-switches -march=native -mtune=native -fPIC > -DPIC -D_GNU_SOURCE -fno-strict-aliasing -Wall -pthread -fPIC -W -Wall > -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wformat -Wpointer-arith > -Wno-missing-field-initializers -fno-strict-aliasing -DPRODUCT=\"BIND\" > -DVERSION=\"9.16.4\" -c ./server.c -fPIC -DPIC -o .libs/server.o > In file included from ./server.c:131: There is no `-I/usr/local/lmdb/include` here > echo $CPPFLAGS > -I/usr/local/include -I/usr/local/openssl11/include > -I/usr/local/lmdb/include -I/usr/include I'd imagine you want CPPFLAGS here. or you can export C_INCLUDE_PATH Matt Pallissard signature.asc Description: PGP signature ___ 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: A And Cname-record
Jukka and others, I would prefer if we didn’t scold people for typos on the mailing list. The typo in the message had no impact on the question itself, and here, we are trying to build community that’s welcoming to newcomers to the wonderful world of DNS. Ondrej -- Ondřej Surý ond...@isc.org > On 18 Jun 2020, at 00:31, Jukka Pakkanen wrote: > > Yes but before going to RFC details one should check the basic spelling and > syntax first... > > -Alkuperäinen viesti- > Lähettäjä: bind-users Puolesta Mark Andrews > Lähetetty: 18. kesäkuuta 2020 0:27 > Vastaanottaja: Bogdan-Stefan Rotariu > Kopio: bind-users@lists.isc.org > Aihe: Re: A And Cname-record > > > >> On 18 Jun 2020, at 07:56, Bogdan-Stefan Rotariu wrote: >> >> Hi, >> >>> On 18 Jun 2020, at 00:44, Ejaz Ahmed wrote: >>> >>> when i am trying to add A and CNAME record together for the same >>> subdomain, getting an error as below, you all kind assistance would >>> be highly appreciated thanks in advance >>> >>> my records are as follows in zone >>> >>> auotdiscover IN A 1.1.1.1 >>> autodiscover IN CNAME autodiscover.acig.com.sa >>> >>> == >>> dns_master_load: acig.com.sa.hosts:102: autodiscover.acig.com.sa: >>> CNAME and other data >>> >>> zone acig.com.sa/IN: loading from master file acig.com.sa.hosts >>> failed: CNAME and other data >>> >>> zone acig.com.sa/IN: not loaded due to errors >> >> CNAME records cannot coexist with any other records last time I’ve >> checked. See section 2.4 from RFC1912[1] >> >> [1] https://tools.ietf.org/html/rfc1912 > > Well it actually goes back to RFC 1034. Unfortunately it wasn’t enforced in > nameservers at the beginning and is still not enforced by some servers. > > 3.6.2. Aliases and canonical names > > ... > > The domain system provides such a feature using the canonical name > (CNAME) RR. A CNAME RR identifies its owner name as an alias, and specifies > the corresponding canonical name in the RDATA section of the RR. If a CNAME > RR is present at a node, no other data should be present; this ensures that > the data for a canonical name and its aliases cannot be different. This rule > also insures that a cached CNAME can be used without checking with an > authoritative server for other RR types. > > Mark > >> — >> Bogdan-Stefan Rotariu >> >> ___ >> 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 > > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org > > ___ > 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 signature.asc Description: Message signed with OpenPGP ___ 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: VS: A And Cname-record
On 17.06.20 22:31, Jukka Pakkanen wrote: Yes but before going to RFC details one should check the basic spelling and syntax first... if there was a spelling mistake, the error would not be "CNAME and other data" when the error is "CNAME and other data", spelling mistakes don't matter... Lähettäjä: bind-users Puolesta Mark Andrews On 18 Jun 2020, at 07:56, Bogdan-Stefan Rotariu wrote: Hi, On 18 Jun 2020, at 00:44, Ejaz Ahmed wrote: when i am trying to add A and CNAME record together for the same subdomain, getting an error as below, you all kind assistance would be highly appreciated thanks in advance my records are as follows in zone auotdiscover IN A 1.1.1.1 autodiscover IN CNAME autodiscover.acig.com.sa == dns_master_load: acig.com.sa.hosts:102: autodiscover.acig.com.sa: CNAME and other data zone acig.com.sa/IN: loading from master file acig.com.sa.hosts failed: CNAME and other data zone acig.com.sa/IN: not loaded due to errors CNAME records cannot coexist with any other records last time I’ve checked. See section 2.4 from RFC1912[1] [1] https://tools.ietf.org/html/rfc1912 Well it actually goes back to RFC 1034. Unfortunately it wasn’t enforced in nameservers at the beginning and is still not enforced by some servers. 3.6.2. Aliases and canonical names ... The domain system provides such a feature using the canonical name (CNAME) RR. A CNAME RR identifies its owner name as an alias, and specifies the corresponding canonical name in the RDATA section of the RR. If a CNAME RR is present at a node, no other data should be present; this ensures that the data for a canonical name and its aliases cannot be different. This rule also insures that a cached CNAME can be used without checking with an authoritative server for other RR types. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Fighting for peace is like fucking for virginity... ___ 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: BIND 9.16 incoming TCP connection errors
On 16/06/2020 20:17, Tony Finch wrote: Hi Tony, 16-Jun-2020 15:21:58.815 general: Accepting TCP connection failed: socket is not connected What does this log message mean? I think this error comes from getpeername() and it can occur if the connection is closed between accept() and getpeername(), which I wouldn't expect to happen all that frequently... Thank you for this. I wasn't seeing these messages under 9.14. They only appear on servers upgraded to 9.16. I'd appreciate it if one of the developers of BIND could shed some light on where this message comes from, so I can investigate what's going on. Regards, Anand ___ 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
