Verizon Users Can't See Site
cyberseal at comcast.net
cyberseal at comcast.net
Tue Sep 14 22:05:47 UTC 2010
----- "Hauke Lampe" <lampe at hauke-lampe.de> wrote:
> On 14.09.2010 19:32, cyberseal at comcast.net wrote:
>
> > Today I was given access to a Linux box on the Verizon network that
> is using their DNS server 71.252.0.12, which is affected by this
> problem.
>
> Your nameserver software is case-sensitive where it should not be:
>
> dig +norec www-mbclive.mbc.irides.com. @216.250.250.136
> - -> correct answer
>
> dig +norec www-mbclive.mbc.irides.COM. @216.250.250.136
> - -> NODATA answer
>
> If Verizon's DNS resolvers use 0x20[1] or modify the character case
> in
> any way, they cannot find the right answer.
>
> You should complain to your DNS LB vendor. Their implementation
> appears
> to be too minimalistic.
>
> dig +norec version.bind txt ch @216.250.250.136
> ;; Question section mismatch: got version.bind/TXT/IN
> ;; connection timed out; no servers could be reached
Hauke, my hat's off to you...I think you nailed it...many, many thanks. I will buy you a beer and a trip around Nurburgring the next time I'm in Germany!
:^ )
More information about the bind-users
mailing list