Blog: Domain

The ".bank" domain registration will open into general availability on June 24, 2015 at 00:00:00 UTC or June 23 at 8:00pm Eastern, 7:00pm Central, 6:00pm Mountain, & 5:00pm Pacific.  According to fTLD, during the initial sunrise regstration period, there were more than 700 applications made for ".bank" domains.  Domains will be awarded on a first-come, first-served basis in all registration periods.  To learn more, read the article Dot Bank by Leticia Saiid of CoNetrix published in the Spring 2015 issue of The Community Banker or visit


Registration for the new “.bank” domains is coming up soon. These domains could be prime Internet names in the future. A few quick notes: [more] 

  • Early “sunrise” registration will be May 18, 2015 with general availability on June 24th.
  • Registration will be limited to domain names with corresponding trademark, trade name, service mark, or bank name. 
  • There will be a verification procedure to ensure these domain names are only issued to valid financial institutions.
  • Banks should consider registering a trademark now to be able to register the associated domain during the sunrise registration period. 
  • Registration will be on a “first come, first serve” basis, so if a bank with similar names want the good domains, they need to register early.
  • More information is available at



According to, the default quota for adding computers by a user to a Domain is 10.  If you attempt to add more than 10, you will likely get the error message:

"Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased."

To resolve the problem, you can run adsiedit.msc on the domain controller and from there change the DOMAIN attribute "ms-DS-MachineAccountQuota" from 10 to something larger like 500.


A computer was getting the error message “the trust relationship between the workstation and the domain failed” when trying to log in.  Normally, the fix is to log on as the local admin and unjoin and rejoin the domain; however, in this case, the person did not know the local admin password. [more]

The solution was to disconnect from the network and then log in using cached domain admin credentials.  After logging in as the domain admin, we reset the local admin password, reconnect to the network, unjoined from the domain, logged on as the local administrators, and then rejoined the domain.