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 problem was that the compression mechanism would compress
a.example.COM and b.example.com by using a pointer to a single string,
in one specific instance, "example.COM". When uncompressed
at at the secondary end, the names came out as a.example.COM and
b.example.COM.
John Wobus
Cornell University CIT
On Dec 15, 2008, at 10:51 AM, Ben Croswell wrote:
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 caused an issue with apps
that were misbehaving.
The master is BIND 9.2.1 and the slaves in question are 8.2.3.
The master zone has everything lower case, and BIND 9 slaves show them
as lower case as well.
A manual zone xfer on the 8.2.3 boxes to a different local directory
than the actual named directory shows .COM.
I was wondering if anyone had experienced an issue like this.
And I understand both of those version are ancient and need to be
removed from the environment.
--
-Ben Croswell
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
