In article ,
PAVLOV Misha wrote:
> Folks,
>
> Wonder if someone can kindly confirm that there is nothing wrong with having
> a PTR record in one of the subnet zone file (we are authorative for) with PTR
> to the name owned by another office (domain). A server
> exchange.north.our.company (ow
On Apr 17, 2013, at 8:58 AM, Matus UHLAR - fantomas wrote:
> On 17.04.13 06:39, Ben-Eliezer, Tal (ITS) wrote:
>> default.log:12-Apr-2013 00:45:37.447 general: warning: zone
>> /IN: gc._msdcs./A: bad owner name (check-names)
>> default.log:12-Apr-2013 00:45:37.447 gene
On 17.04.13 06:39, Ben-Eliezer, Tal (ITS) wrote:
Subject: BIND 9.4.x and check-names
Isn't it time to upgrade?
I recently implemented a change in our DNS environment with the intention
of suppressing the log events related to AD-integrated zones, and their
Non-RFC compliant nature.
check-nam
You can point PTR records anywhere you want. In fact, there's nothing
that even says that PTR records are limited to representing reverse
mappings, or that they can only appear in the in-addr.arpa hierarchy.
Strictly speaking, they're just name-to-name mappings, _sans_ the
special "aliasing" fu
Folks,
Wonder if someone can kindly confirm that there is nothing wrong with having a
PTR record in one of the subnet zone file (we are authorative for) with PTR to
the name owned by another office (domain). A server exchange.north.our.company
(owned and registered in north.our.company domain)
Chu,
I also use gcc on Solaris instead of SunStudio (or whatever they're calling it
these days).
Here's the history from my last build:
export
PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/sbin:/usr/sfw/bin:/usr/ucb:/usr/openwin/bin:/usr/ccs/bin:/opt/sf
"Ben-Eliezer, Tal (ITS)" wrote:
Good Morning,
I recently implemented a change in our DNS environment with the intention of
suppressing the log events related to AD-integrated zones, and their Non-RFC
compliant nature.
In the global configuration I added the following statements:
check-names
Good Morning,
I recently implemented a change in our DNS environment with the intention of
suppressing the log events related to AD-integrated zones, and their Non-RFC
compliant nature.
In the global configuration I added the following statements:
check-names slave ignore;
check-names master i
Chu
My version of BIND is compiled 64-bit and running:
>~: file bin/named/named
bin/named/named:ELF 64-bit MSB executable SPARCV9 Version 1,
dynamically linked, not stripped
Compiled with Studio I passed the following variables in configure:
CC="/bin/cc"
CXX="/bin/CC"
F77="/bin/f77"
CF
9 matches
Mail list logo