Re: Issue with case changing from master on BIND 9 to slave on BIND 8

2008-12-15 Thread Mark Andrews
Mark Andrews writes: > > > > In message <9fc47420fb263da9eda170166fd4d...@cornell.edu>, John Wobus writes: > > Some years ago, I had that issue. The problem was that the > > zone transfer compression mechanism could change the case > > of individual names. This was fixed in some release of bi

Re: Issue with case changing from master on BIND 9 to slave on BIND 8

2008-12-15 Thread Mark Andrews
In message <9fc47420fb263da9eda170166fd4d...@cornell.edu>, John Wobus writes: > Some years ago, I had that issue. The problem was that the > zone transfer compression mechanism could change the case > of individual names. This was fixed in some release of bind > (after 9.2.1, if I remember cor

Re: Issue with case changing from master on BIND 9 to slave on BIND 8

2008-12-15 Thread John Wobus
Some years ago, I had that issue. The problem was that the zone transfer compression mechanism could change the case of individual names. This was fixed in some release of bind (after 9.2.1, if I remember correctly), and bind release notes would pinpoint the exact version with the change. The p

Issue with case changing from master on BIND 9 to slave on BIND 8

2008-12-15 Thread Ben Croswell
I reaching out to the list on what appears to be a very odd issue that happened over the weekend. We had an issue where some internal domains had the TLD capitalized after the zone transfer. i.e. foo.bar.com on the master became foo.bar.COM on the slave. I know that DNS is case insensitive but it c