Of course... Error code 18!!! Damn!
On Thu, Jan 28, 2016 at 9:14 AM, Matus UHLAR - fantomas
wrote:
> On 28.01.16 08:58, Bernard Fay wrote:
>
>> When checking my reverse zone, I have the following error:
>>
>> named-checkzone cts.org 192.168.99.zone
>> zone cts.org/IN: NS 'ns1.cts.org' has no ad
Suffix searching is a client function, there is no explicit support for it in
BIND or any nameserver implementation.
The only incredibly ugly thing you could do in DNS to support shortname
resolution is set up a "fake" root zone containing the names you need to
resolve. But, you really don't wa
Howdy Mark,
Can you please clarify the best practice for this?
> Recursive servers (honouring RD=1) however can be authoritative for zones.
In this context of "authoritative", do you mean that they can be fully
functional slaves and have a complete copy of the zone information?
I would imagine
Why not? Data obtained from the recursive function will never outrank
authoritative data of a master or a slave. See the "Data Ranking" section of
RFC 2181. AFAICT, it's been a *very* long time since BIND, or any other DNS
implementation, has accidentally got those ranking rules wrong and given
On 01/21/2016 09:27 AM, gnafou wrote:
I have a zone myzone.com where dynamic dns is active ( dhcp updates
continuously the dns )
I need to respond differently for MX requests such as :
MX for "internal" queries ismxinternal.myzone.com
MX for "internet" queries is mxexternal.myzone.
On 01/22/2016 01:03 AM, gnafou wrote:
but, indeed i do need some of the dynamic dns data in the external view
and yes, the mx is it the apex ..
How dynamic? Are we talking DHCP for a LAN w/ AD joined clients? Or
are we talking occasional updates for an external IP of a cable modem?
Your a
On 01/23/2016 01:47 PM, Olliver Schinagl wrote:
recently I updated to bind-9.10 and noticed that an illegal setup was
finally disallowed. Good things, but I (and others I'm sure) kind of
miss-used this ability. With the change however, I am now looking for
help on restoring similar behavior. Let
On 01/26/2016 04:46 PM, Reindl Harald wrote:
violating what?
Chaining CNAMEs is a violation according to RFCs.
It works, but it is unsupported, and you can only blame yourself when it
doesn't.
--
Grant. . . .
unix || die
___
Please visit https:/
Thanks for the followup.
>
> NXDOMAIN is not a "failure" response. Are you *sure* you're getting NXDOMAIN?
Yes. Pretty sure. With hindsight I should have run the tests inside a 'script'
session.
> If you're using nslookup to test, be aware that it will do suffix searching
> by default, so if
On 2016-01-21 08:27, gnafou wrote:
Hello
I have a zone myzone.com where dynamic dns is active ( dhcp updates
continuously the dns )
I need to respond differently for MX requests such as :
MX for "internal" queries ismxinternal.myzone.com
MX for "internet" queries is mxexternal.m
On 2016-01-29 18:45, Grant Taylor wrote:
On 01/26/2016 04:46 PM, Reindl Harald wrote:
violating what?
Chaining CNAMEs is a violation according to RFCs.
It works, but it is unsupported, and you can only blame yourself when
it doesn't.
Maybe I'm misremembering RFC 1034, but a CNAME chain onl
11 matches
Mail list logo