On 11/08/2019 18:12, Tom Ivar Helbekkmo wrote:
Hmm. Might it also work to do something really simple involving more
than one recursor? If the primary recursor had something like this:
forward-zones-recurse=e164.arpa=10.0.0.11;1.1.1.1
...and the one at 10.0.0.11 then had:
forward-zones=e164.a
Juha Heinanen via Pdns-users writes:
> Some of the e164.arpa domains used in my SIP Proxy environment are
> private and thus (on purpose), are not registered under e164.arpa.
Depending on what software you're using, it may be possible to work
around this by using another DNS domain. With Asteri
Is there some good reason why backwards compatibility was not provided
by a recursor.conf setting that would make it to send all requests to
the authoritative server and if server responds to a request with not
found, recursor would send the request to the Internet?
-- Juha
___
Brian Candler writes:
> * You can forward e164.arpa to your own authoritative nameserver(s) with
> a single static entry, and all subdomains will be forwarded. Of course,
> no other domains under e164.arpa will resolve, since you've made
> yourself authoritative for the whole domain.
>
> * Yo
On 10/08/2019 07:24, Juha Heinanen via Pdns-users wrote:
I have been using 4.0.x pdns/recursor setup to serve DNS records of
phone numbers. For example, a domain name in records table could be
1.7.6.5.4.3.2.3.8.5.3.e164.arpa. Phone numbers can be random, i.e.,
they don't necessarily share a com
I have been using 4.0.x pdns/recursor setup to serve DNS records of
phone numbers. For example, a domain name in records table could be
1.7.6.5.4.3.2.3.8.5.3.e164.arpa. Phone numbers can be random, i.e.,
they don't necessarily share a common prefix. The records are
added/removed dynamically when
