I do confirm that NS21.DOMAINCONTROL.COM and NS22.DOMAINCONTROL.COM are also unreacheable from ISP Free.fr in France.<br />
Like pQd traceroute, mine also end after 208.109.115.201 for both ns21 and ns22.

    traceroute to NS22.DOMAINCONTROL.COM (208.109.255.11), 64 hops max, 40 byte packets
     1  x.x.x.x (x.x.x.x)  2.526 ms  0.799 ms  0.798 ms
     2  78.224.126.254 (78.224.126.254)  6.313 ms  6.063 ms  6.589 ms
     3  213.228.5.254 (213.228.5.254)  6.099 ms  6.776 ms *
     4  212.27.50.170 (212.27.50.170)  6.943 ms  6.866 ms  6.842 ms
     5  212.27.50.190 (212.27.50.190)  8.308 ms  6.641 ms  6.866 ms
     6  212.27.38.226 (212.27.38.226)  68.660 ms  185.527 ms  14.123 ms
     7  204.245.39.50 (204.245.39.50)  48.544 ms  19.391 ms  19.753 ms
     8  208.109.115.201 (208.109.115.201)  19.315 ms  19.668 ms  34.110 ms
     9  * * *
    10  * * *
    11  * * *
    12  * * *

But ns52.domaincontrol.com (208.109.255.26) do works and is in the same subnet as ns22.domaincontrol.com (208.109.255.11)

    traceroute to ns52.domaincontrol.com (208.109.255.26), 64 hops max, 40 byte packets
     1  x.x.x.x (x.x.x.x)  1.229 ms  0.816 ms  0.808 ms
     2  78.224.126.254 (78.224.126.254)  12.127 ms  5.623 ms  6.068 ms
     3  * * *
     4  212.27.50.170 (212.27.50.170)  13.824 ms  6.683 ms  6.828 ms
     5  212.27.50.190 (212.27.50.190)  6.962 ms *  7.085 ms
     6  212.27.38.226 (212.27.38.226)  35.379 ms  7.105 ms  7.830 ms
     7  204.245.39.50 (204.245.39.50)  19.896 ms  19.426 ms  19.355 ms
     8  208.109.115.121 (208.109.115.121)  37.931 ms  19.665 ms  19.814 ms
     9  208.109.115.162 (208.109.115.162)  19.663 ms  19.395 ms  29.670 ms
    10  208.109.113.62 (208.109.113.62)  19.398 ms  19.220 ms  19.158 ms
    11  * * *
    12  * * *
    13  * * *

As you can see, this time after 204.245.39.50 we go to 208.109.115.121 instead of 208.109.115.201.
And pQd has the same traceroute. From a working place I did not cross this 204.245.39.50 router (Global Crossing).

More traceroute from working and non working place would help, but it's highly probable that  Global Crossing has a bogus routing entry for 208.109.255.11/32 and 216.69.185.11/32 as 208.109.255.10, 208.109.255.12, 216.69.185.10, 216.69.185.12 are working well.

Why it has a boged routing entry is hard to know. Probably 208.109.115.201 (Go Daddy) is advertising a non working route for 208.109.255.11/32 and 216.69.185.11/32.

EDIT: You can telnet route-server.eu.gblx.net to connect to the Global Crossing route server and do traceroute from within Global Crossing network