On 12/27/19 3:43 PM, Paul Kosinski via bind-users wrote:
P.S. Unfortunately our 2 current IPs, although adjacent, are not /31,
and thus would require 2 delegations
There's always going to be at least one record, be it an NS for
delegation or CNAME for 2317, for each IP that's not being delegat
I was pleased that I was able to get our two (successive) ISPs to set
up reverse DNS for our small number of IP addresses, and each twice to
change them when they moved us to moved us to new IP ranges (due to the
IPv4 crunch). It never even occurred to me that it might be possible to
have them dele
On 12/27/19 1:22 PM, Reindl Harald wrote:
nobody out there will delegate single /255 ip's
I've had multiple different ISP's delegate reverse DNS for single IPs
(/32 or /128) multiple times.
Some used RFC 2317 Classless IN-ADDR.ARPA Delegation, others used
standard delegation.
Some ~> many
Am 27.12.19 um 21:06 schrieb Grant Taylor via bind-users:
>> if the ISP is willing to do and if you really own a large enough range
>> that it makes sense is a different question, for just 3 random
>> addresses it is unlikely to happen
>
> Agreed.
>
> But I will still ask the ISP to delegate t
On 12/27/19 10:49 AM, Reindl Harald wrote:
in the real world they just delegate the reverse-zone to your nameserver
like it#s done for our /24 range for years
Please clarify what the "reverse-zone" is that you're talking about. Is
it "246.2.186.in-addr.arpa." or "17.246.2.186.in-addr.arpa."?
On 12/27/19 10:48 AM, Matus UHLAR - fantomas wrote:
I think that it should be either change local DNS or call ISP to change
it, not both at once. Having both usually creates/hides different kinds
of problems.
Yes, ideally the configuration lives in one place. Multi-master is
always problema
Am 27.12.19 um 18:58 schrieb Matus UHLAR - fantomas:
The only thing that I saw was a slip in that there is something
outside the local DNS server that needs to be configured for reverse
DNS.
>
>> Am 27.12.19 um 18:48 schrieb Matus UHLAR - fantomas:
>>> I think that it should be e
The only thing that I saw was a slip in that there is something
outside the local DNS server that needs to be configured for reverse DNS.
Am 27.12.19 um 18:48 schrieb Matus UHLAR - fantomas:
I think that it should be either change local DNS or call ISP to change it,
not both at once. Having b
Am 27.12.19 um 18:48 schrieb Matus UHLAR - fantomas:
>> The only thing that I saw was a slip in that there is something
>> outside the local DNS server that needs to be configured for reverse DNS.
>
> I think that it should be either change local DNS or call ISP to change it,
> not both at once.
Am 27.12.19 um 16:58 schrieb Grant Taylor via bind-users:
> On 12/27/19 7:04 AM, Matus UHLAR - fantomas wrote:
>> they configure it for fetching from your servers.
>
> I do object to this part of the statement.
>
> This seems to imply that the ISP is a secondary DNS server and doing
> zone tra
On 12/27/19 7:04 AM, Matus UHLAR - fantomas wrote:
there's obviously something broken in this setup. You don't have
to call the ISP if the reverse DNS changes.
On 27.12.19 08:58, Grant Taylor via bind-users wrote:
Why do you say that?
What do you see that's broken in the OP's configuration?
On 12/27/19 7:04 AM, Matus UHLAR - fantomas wrote:
there's obviously something broken in this setup. You don't have to
call the ISP if the reverse DNS changes.
Why do you say that?
What do you see that's broken in the OP's configuration?
I personally didn't see anything broken. Hence why r
On 27.12.19 00:27, Edouard Guigné wrote:
I have forgotten this point, rdns is done by ISP...
The same problem occured 2 years ago, and I have to call them to restart it.
there's obviously something broken in this setup. You don't have to call
the ISP if the reverse DNS changes.
Either they s
13 matches
Mail list logo
