nt view. Maintaining
multiple versions will be a big overhead and, IMHO, this way madness lies.
If it were my network I'd advise the team who designed this application
to rethink their delivery mechanism. so that the requirement for
one_name == multiple IPs goes away.
/soapbox
If you
192.168.127.1
printer IN A 192.168.1.1
ldapIN A 172.16.1.16
; etc
;
On 4/15/25 8:43 AM, Marek Kozlowski wrote:
OK,
1. The sceniario:
For the clients: 192.168.1/24:
nfs.mydomain -> 192.168.12
ss lies.
If it were my network I'd advise the team who designed this application
to rethink their delivery mechanism. so that the requirement for
one_name == multiple IPs goes away.
/soapbox
If you absolutely *must* do this, some actual examples would help
please, rather than generalisat
t both ends so that the secondary
includes the key for a zone when making its transfer request and the
primary uses that to select the correct zone from the appropriate view.
End clients/stub resolvers don't typically use keys.
I hope this helps.
Cheers, Greg
On Mon, 14 Apr 2025 at 14:12
:-)
There are 4 name servers for my domain: two internal ones (my CIDR,
managed by me) and two external ones (foreign IP, I have no
administrative privileges).
I've been using two views: the private one (for my clients, served by my
servers) and a public one (for remote clients, served by al
:-)
On 1/18/21 9:59 AM, Reindl Harald wrote:
Am 18.01.21 um 09:49 schrieb Marek Kozlowski:
I believe that such a solution (read to install) should exist.
Unfortunately I don't know the magic keywords to find it:
I have a group of hosts with different IPs offering the same services.
I&#
:-)
I believe that such a solution (read to install) should exist.
Unfortunately I don't know the magic keywords to find it:
I have a group of hosts with different IPs offering the same services.
I'm able to install some agents on them for monitoring their
network/cpu/number of users/whateve
JECT Unacceptable HELO (Forged) /^yahoo\.es$/
> REJECT Unacceptable HELO (Forged) /^yahoo\.fr$/
> REJECT Unacceptable HELO (Forged) /^yahoo\.ie$/
> REJECT Unacceptable HELO (Forged) /^yahoo\.it$/
> REJECT Unacceptable HELO (Forged) /^yahoo\.jp$/
> REJECT Unacceptable HELO (Forged) /
:-)
I have defined several A and PTR records for my main server.
Unfortunately, recently I've noticed that some peer servers have
problems with rev-resolving my IP (verifying the name and address) if
there are too many As and PTRs. I'm wondering if it's possible to
specify one A and one PTR as a "
:-)
I have several domains for which I have two "internal" DNS servers (a
primary and one of the secondaries) and two "external" DNS servers (both
secondaries). There are six domains for each of them I have pairs of
zone description files: a private (for internal clients) and a public
(for all oth
:-)
As I can see BIND allows duplicate A:
pikusIN A 192.168.1.1
pikusIN A 192.168.1.2
and PTR:
192.168.1.1.IN PTR pikus.somedomain.com.
192.168.1.1.IN PTR filemon.somedomain.com.
and disallows duplicate CNAMEs in the same way. For A and PTR both
records are returned. My question
:-)
>> Or should I use separate secondary DNS servers for internal and
>> external zones?
>
> That depends a bit on your setup. Judicious use of views with ACLs
> could help you solve your problem regarding the zone transfers, but you
> may feel more comfortable with separate servers.
I understan
:-)
I have defined two views (let's call them an `internal' and an
`external') for my zones on the primary DNS server. Let's assume I'd
like the secondary DNS server to use the same two views synchronized to
the primary DNS. May I transfer *views* rather than zone description
files? May I transfer
:-)
One more question:
The documentation for `match-clients' isn't comprehensive enough... Can
I add all host from, for example 172.16/16 except a single host? Does:
match-clients { 172.16.0.0/16;!172.16.1.1; }
form an AND or an OR?
Best regards,
/m
_
:-)
Forgive me a stupid question but I can't find the answer...
Is it allowed to use a few `zone' clauses for a single domain? Is
something like this correct:
zone "mickey.mouse.com" in {
type master;
file "pri/mickey-public.zone";
allow-query { any; };
allow-trans
15 matches
Mail list logo
