On 19/07/2019 16:15, bryantz-p...@zktech.com wrote:
Thank you again for your response, and also thank you for yesterday
pointing me to the support in open policy for the group.
Currently I don't have any evidence as I have not done the packet
captures.
Two of the three outside parties complain
Sincerely
Bryant
Bryant Zimmerman
Sr. Systems Architect
Grand Dial Communications, A ZK Tech Inc. Company
616-299-5607 (mobile)
616-855-1030 Ext. 2003 (office)
From: Brian Candler
Sent: 7/19/19 11:05 AM
To: bryantz-p...@zktech.com, pdns-users
Subject:
AM
To: bryantz-p...@zktech.com, pdns-users
Subject: Re: [Pdns-users] Reverse Lookup zone subnetted
On 19/07/2019 15:52, bryantz-p...@zktech.com wrote:
> Where we are getting into issues is that customers we host e-mail
> servers for are having issues as some email service providers appear
>
On Fri, 2019-07-19 at 14:52 +, bryantz-p...@zktech.com wrote:
> Alan
>
> Where we are getting into issues is that customers we host e-mail
> servers for are having issues as some email service providers appear
> to be forcing their reverse lookups directly against our powerdns
> servers.
>
>
On 19/07/2019 16:00, Brian Candler wrote:
On 19/07/2019 15:52, bryantz-p...@zktech.com wrote:
Where we are getting into issues is that customers we host e-mail
servers for are having issues as some email service providers appear
to be forcing their reverse lookups directly against our powerdns
On 19/07/2019 15:52, bryantz-p...@zktech.com wrote:
Where we are getting into issues is that customers we host e-mail
servers for are having issues as some email service providers appear
to be forcing their reverse lookups directly against our powerdns servers.
Can you provide your evidence fo
On 19/07/2019 13:55, bryantz-p...@zktech.com wrote:
If we do the following dig against our dns server we get a failure...
dig -x 65.183.176.179 @ns1.granddial.net
; <<>> DiG 9.9.4-rpz2.13269.14-P2 <<>> -x 65.183.176.179
@ns1.granddial.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<-
M
To: pdns-users
Subject: Re: [Pdns-users] Reverse Lookup zone subnetted
On Fri, 2019-07-19 at 12:55 +, bryantz-p...@zktech.com wrote:
If we do the following dig against our dns server we get a failure...
dig -x 65.183.176.179 @ns1.granddial.net
; <<>> DiG 9.9.4-rpz2.13269.14-P2
On Fri, 2019-07-19 at 12:55 +, bryantz-p...@zktech.com wrote:
> If we do the following dig against our dns server we get a
> failure...
>
> dig -x 65.183.176.179 @ns1.granddial.net
> ; <<>> DiG 9.9.4-rpz2.13269.14-P2 <<>> -x 65.183.176.179
> @ns1.granddial.net
> ;; global options: +cmd
> ;;
/27 IP
addresses in our block
I know I could put in a separate zone file for each IP address, but with 15 to
20 /27 blocks that is over 300 domains
Any ideas would be appreciated
Thanks
Bryant
From: Brian Candler
Sent: 7/19/19 4:20 AM
To: bryantz-p...@
On 19/07/2019 00:02, bryantz-p...@zktech.com wrote:
zone file - 60/27.1.1.1.in-addr.arpa
We then added PTR records for it would looks something like
62.60/27.1.1.1.in-addr.arpa. IN PTR mail.ourserver.net
63.60/27.1.1.1.in-addr.arpa. IN PTR mail.ourotherserver.net
For some reason PowerDNS wil
On Thu, 2019-07-18 at 23:02 +, bryantz-p...@zktech.com wrote:
> We have a /27 block of IP's from our datacenter
>
> Using binddns we listed them like this example
>
> zone file - 60/27.1.1.1.in-addr.arpa
> We then added PTR records for it would looks something like
>
> 62.60/27.1.1.1.in-ad
We have a /27 block of IP's from our datacenter
Using binddns we listed them like this example
zone file - 60/27.1.1.1.in-addr.arpa
We then added PTR records for it would looks something like
62.60/27.1.1.1.in-addr.arpa. IN PTR mail.ourserver.net
63.60/27.1.1.1.in-addr.arpa. IN PTR mail.ourother
13 matches
Mail list logo
