[Murtaza Piyersoap] I would suggest that while discussion understand what is applicable for all items in the backlog and that goes in DoD and what is specific to the user story or specific to the feature you are developing goes as acceptance criteria.

[Kristen Varona] My response would be that the DoD contains criteria that apply to all stories that flow through the team. These are the contract between the PO and the Sprint Team to know when a story is deemed, 'done'. example: 'All acceptance criteria have been met', 'All code has been merged to {x}', etc

The acceptance criteria are criteria specific to the story to describe how to validate that the requirement has been met. example: Given I have an account, When I login, Then I expect to be on the dashboard, And I expect to see my avatar and first name.

[Ayushi Garg] Acceptance criteria mentions the set of conditions, features and functionality that must be completed for that particular user story to be considered as complete.

While DOD is kind of checklist which includes code completion, unit testing, integration testing, documentation, security, accessibility. In short, DOD sets the overall standards for completion including various aspects of development process while acceptance criteria focus on requirements that need to be fulfilled for a feature to be approved by PO.

[Debarati Roy Gupta] As per my understanding, Acceptance criteria to be written by Product Owner as he is the value maximizer for the Product and voice of customer.
But if a scenario arise where PO is relatively new and developers are much mature where they are working on the Product for a long time.In that case Dev may be in the position to suggest a better way to create Acceptance Criteria .But finally customer's voice should be reflected in Acceptance Criteria.
As a SM one should help team to understand
that instead of arguing let understand customer's requirement tranparantly such that customer voice gets reflected in Acceptance Criteria.
As far as DOD is concerned Dod to ensure that increment in created as per Customer requirement. There also PO as value maximizer can suggest better way of creating DOD or a mature team can give their perspective but finally customer should be happy with the increment.
1st agile principle says
"Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software."