Re: Unable to completely transfer root zone

On Sun, Feb 16, 2020 at 6:48 AM Ed Daniel wrote: > > Thank you for replying and sharing, Warren. I apologise for my > misunderstanding of the intent of your words. Nah, no worries - tone gets lost in email, and my response definitely could have been read as really sarcastic. I'd also like to

Re: Unable to completely transfer root zone

Thank you for replying and sharing, Warren. I apologise for my misunderstanding of the intent of your words. On 16/02/2020 03:08, Warren Kumari wrote: > > > On Fri, Feb 14, 2020 at 10:49 PM Ed Daniel > wrote: > > On 11/02/2020 15:28, Warren Kumari wrote: >

Re: Unable to completely transfer root zone

On Fri, Feb 14, 2020 at 10:49 PM Ed Daniel wrote: > On 11/02/2020 15:28, Warren Kumari wrote: > > On Tue, Feb 11, 2020 at 3:12 AM Stephane Bortzmeyer > wrote: > >> > >> On Mon, Feb 10, 2020 at 02:32:55PM -0500, > >> Warren Kumari wrote > >> a message of 70 lines which said: > >> > >>> Also,

Re: Unable to completely transfer root zone

Matus UHLAR - fantomas wrote: If you use cisco routers, ask network admins to disable any DNS "fixup" functionality, because that usually causes problems. On 14.02.20 12:47, Tony Finch wrote: In my experience all Cisco PIX/ASA fuxup options are horribly broken and should be turned off. I

Re: Unable to completely transfer root zone

Matus UHLAR - fantomas wrote: > > unfortunately this happens when you decide to mirror root zone and it fails. > > you should use more primary servers when possible and change root zone > type from secondary to hint if it fails. In this particular case, adding more primaries would not have

Re: Unable to completely transfer root zone

On 14.02.20 09:32, von Dein, Thomas wrote: As reported we were unable to transfer the root zone for 1 week, then the expire time was over and we had an outage. unfortunately this happens when you decide to mirror root zone and it fails. you should use more primary servers when possible and

Re: Unable to completely transfer root zone

On 11/02/2020 15:28, Warren Kumari wrote: > On Tue, Feb 11, 2020 at 3:12 AM Stephane Bortzmeyer wrote: >> >> On Mon, Feb 10, 2020 at 02:32:55PM -0500, >> Warren Kumari wrote >> a message of 70 lines which said: >> >>> Also, can you try: >>> dig +tcp . axfr @192.0.32.132 >>> dig +tcp . axfr

Re: Unable to completely transfer root zone

On Tue, Feb 11, 2020 at 3:12 AM Stephane Bortzmeyer wrote: > > On Mon, Feb 10, 2020 at 02:32:55PM -0500, > Warren Kumari wrote > a message of 70 lines which said: > > > Also, can you try: > > dig +tcp . axfr @192.0.32.132 > > dig +tcp . axfr @192.0.47.132 > > dig +tcp . axfr

Re: Unable to completely transfer root zone

Warren Kumari wrote: > von Dein, Thomas wrote: > > > > Does anyone have an idea, what's wrong here and how I could possibly fix > > this? > > This sounds very much like a path MTU issue -- it starts the transfer, > gets part of the way and then a big packet doesn't make it through... I

Re: Unable to completely transfer root zone

On Mon, Feb 10, 2020 at 02:32:55PM -0500, Warren Kumari wrote a message of 70 lines which said: > Also, can you try: > dig +tcp . axfr @192.0.32.132 > dig +tcp . axfr @192.0.47.132 > dig +tcp . axfr @b.root-servers.net > > (no, I'm not really sure why trying with the first 2 IPs instead of >

Re: Unable to completely transfer root zone

Hi usually it is a common problem. If u'r succesful via u'r root access, it mean is not a network or BIND related but FULL PATH and File Permission issue. Daemons does not run with root privilege for priviledge escalation and specially bind and others are jailed. Check if all paths are not

Re: Unable to completely transfer root zone

On Mon, Feb 10, 2020 at 12:53 PM von Dein, Thomas wrote: > > Hi everyone, > > we are unable to complete root zone transfer from our nameservers. This is > the error we're getting: > > Feb 10 18:33:32 bedns2 named[61444]: transfer of './IN' from 192.0.47.132#53: > connected using