Re: difference in responses between UDP and TCP

> > 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

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

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

difference in responses between UDP and TCP

Hello, Wondering why we are seeing different serial numbers from a bind authoritative server for requests over UDP and TCP. dig +tcp soa @ns.example.com example.com +short ns1.example.com. hostmaster.example.com. 2017061505 10800 3600 360 3600 dig +notcp soa @ns.example.com example.com +shor