Re: reverse dns configuration for IPV4, IPV6+ dns+ mail ?

2017-06-18 Thread Matus UHLAR - fantomas
On 19.06.17 08:03, Pierre Couderc wrote: Ok, thank you all, now I need to understand your answers... long story short: in the "125.124.123.in-addr.arpa" zone: 126 IN PTR mail.xxx.com. quoting your original message: What should I put for IPV4 reverse address : if I put mail.xxx.com,

Re: reverse dns configuration for IPV4, IPV6+ dns+ mail ?

2017-06-18 Thread Matus UHLAR - fantomas
On 18.06.17 16:26, Mark Elkins wrote: Put two reverse records in both the IPv4 and IPv6 reverse zones in the "125.124.123.in-addr.arpa" zone: 126 IN PTR mail.xxx.com. 126 IN PTR ns.xxx.com. Am 18.06.2017 um 17:38 schrieb Matus UHLAR - fantomas: there are cases when having t

Re: reverse dns configuration for IPV4, IPV6+ dns+ mail ?

2017-06-18 Thread Pierre Couderc
On 06/19/2017 01:05 AM, Reindl Harald wrote: Am 18.06.2017 um 17:38 schrieb Matus UHLAR - fantomas: On 18.06.17 16:26, Mark Elkins wrote: Put two reverse records in both the IPv4 and IPv6 reverse zones in the "125.124.123.in-addr.arpa" zone: 126 IN PTR mail.xxx.com. 126 IN

Re: reverse dns configuration for IPV4, IPV6+ dns+ mail ?

2017-06-18 Thread Reindl Harald
Am 18.06.2017 um 17:38 schrieb Matus UHLAR - fantomas: On 18.06.17 16:26, Mark Elkins wrote: Put two reverse records in both the IPv4 and IPv6 reverse zones in the "125.124.123.in-addr.arpa" zone: 126 IN PTR mail.xxx.com. 126 IN PTR ns.xxx.com. while this is possible, it's

Re: reverse dns configuration for IPV4, IPV6+ dns+ mail ?

2017-06-18 Thread Matus UHLAR - fantomas
On 18.06.17 16:26, Mark Elkins wrote: Put two reverse records in both the IPv4 and IPv6 reverse zones in the "125.124.123.in-addr.arpa" zone: 126 IN PTR mail.xxx.com. 126 IN PTR ns.xxx.com. while this is possible, it's not always a good idea. One reverse record is enough in m

Re: reverse dns configuration for IPV4, IPV6+ dns+ mail ?

2017-06-18 Thread Matus UHLAR - fantomas
On 18.06.17 15:40, Pierre Couderc wrote: Well, we have 2 computers in xxx.com subnet provided by ISP on 123.124.125.126 ipV4 address and corresponding IPV6 segment mail.xxx.com :2a01:e34:::::1122:3344 for mail server ns.xxx.com : 2a01:e34:::::aabb:ccdd for

Re: reverse dns configuration for IPV4, IPV6+ dns+ mail ?

2017-06-18 Thread Mark Elkins
Put two reverse records in both the IPv4 and IPv6 reverse zones in the "125.124.123.in-addr.arpa" zone: 126 IN PTR mail.xxx.com. 126 IN PTR ns.xxx.com. and the same sort of thing in the reverse IPv6 zone. To calculate run:- 2a01:e34:::::1122:3344 and see what que

reverse dns configuration for IPV4, IPV6+ dns+ mail ?

2017-06-18 Thread Pierre Couderc
Well, we have 2 computers in xxx.com subnet provided by ISP on 123.124.125.126 ipV4 address and corresponding IPV6 segment mail.xxx.com :2a01:e34:::::1122:3344 for mail server ns.xxx.com : 2a01:e34:::::aabb:ccdd for dns server In xxx.com bind : mail A 123.

Re: difference in responses between UDP and TCP

2017-06-18 Thread Arun Natarajan
> > If it is happening consistently, then it's possible that you have *two* >> DNS servers listening on the server, one on the UDP socket, and another >> on the TCP socket, and they're loaded with different zones. >> > > You are right, seems there are two DNS process listening TCP and UDP. :) >

Re: difference in responses between UDP and TCP

2017-06-18 Thread Reindl Harald
Am 18.06.2017 um 12:12 schrieb Arun Natarajan: Hello Tony, Without knowing the server host name and zone name there could be lots of different reasons, so there isn't really any way to answer. True, dig +tcp @212.26.18.3 pub.sa serial: 2017061

Re: difference in responses between UDP and TCP

2017-06-18 Thread Arun Natarajan
Hello Tony, > > Without knowing the server host name and zone name there could be lots of > different reasons, so there isn't really any way to answer. > > True, dig +tcp @212.26.18.3 pub.sa serial: 2017061804 dig +notcp @212.26.18.3 pub.sa serial: 2017061805 -- arun ___

Re: difference in responses between UDP and TCP

2017-06-18 Thread Arun Natarajan
Hello Anand, Thanks for the response. > > Perhaps the zone got updated between your queries. > > Have you (as one should in a proper experiment) repeated these queries > to demonstrate that this is happening consistently? > Yes, it is a consistent behaviour. It happens with some of our secondar