Format

Send to:

Choose Destination
See comment in PubMed Commons below
J Biol Chem. 2005 Dec 16;280(50):41584-94. Epub 2005 Oct 11.

Mva1269I: a monomeric type IIS restriction endonuclease from Micrococcus varians with two EcoRI- and FokI-like catalytic domains.

Author information

  • 1Institute of Biotechnology, Graiciuno 8, Vilnius LT-02241, Lithuania.

Abstract

Type II restriction endonuclease Mva1269I recognizes an asymmetric DNA sequence 5'-GAATGCN / -3'/5'-NG / CATTC-3' and cuts top and bottom DNA strands at positions, indicated by the "/" symbol. Most restriction endonucleases require dimerization to cleave both strands of DNA. We found that Mva1269I is a monomer both in solution and upon binding of cognate DNA. Protein fold-recognition analysis revealed that Mva1269I comprises two "PD-(D/E)XK" domains. The N-terminal domain is related to the 5'-GAATTC-3'-specific restriction endonuclease EcoRI, whereas the C-terminal one resembles the nonspecific nuclease domain of restriction endonuclease FokI. Inactivation of the C-terminal catalytic site transformed Mva1269I into a very active bottom strand-nicking enzyme, whereas mutants in the N-terminal domain nicked the top strand, but only at elevated enzyme concentrations. We found that the cleavage of the bottom strand is a prerequisite for the cleavage of the top strand. We suggest that Mva1269I evolved the ability to recognize and to cleave its asymmetrical target by a fusion of an EcoRI-like domain, which incises the bottom strand within the target, and a FokI-like domain that completes the cleavage within the nonspecific region outside the target sequence. Our results have implications for the molecular evolution of restriction endonucleases, as well as for perspectives of engineering new restriction and nicking enzymes with asymmetric target sites.

PMID:
16223716
[PubMed - indexed for MEDLINE]
Free full text
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for HighWire
    Loading ...
    Write to the Help Desk