Who was Dedan's father?

What follows is one scholar’s way of reading this disagreement — a critical-historical view that often concludes the texts genuinely disagree. It draws on the peer-reviewed sources listed below and stands as one position among the answers above, presented for transparency, not as GEBible’s position.

How critical scholarship weighs this: Genuinely disputed among scholars

This summarizes where critical scholarship tends to land on this tension — a report on the field’s center of gravity, not GEBible’s own ruling.

The contradiction is structurally identical to the Sheba problem: a single ethnonym, *Dedan*, is assigned two different fathers in two different lineages. Genesis 10:7 and its verbatim parallel in 1 Chronicles 1:9 place Dedan in the Hamite-Cushite line as a son of Raamah son of Cush; Genesis 25:3 and 1 Chronicles 1:32 place him in the Abrahamic line as a son of Jokshan, one of the sons of Keturah. The Chronicler simply transcribes both Genesis traditions without remark, which is itself diagnostic — he saw no need to choose, because in his genre the lists are not competing biological claims but competing ethnographic maps.

The strongest harmonization, defended by Kenneth Mathews and Derek Kidner, is that two distinct clans bore the name Dedan: one Cushite, one Keturite, both eventually settling in or trading through the same North Arabian corridor. This is not implausible on its face. Dedan is a securely attested place — the Dadan oasis in the al-ʿUlā region of northwest Arabia, a major caravan station on the incense road, associated with the Dadanite and later Lihyanite kingdoms and a substantial corpus of Dadanitic inscriptions. Ezekiel 27:20 and 38:13 treat Dedan as a trading people, and Jeremiah 25:23 and 49:8 locate it near Edom and Tema. So a name attached to a region rather than a person could plausibly recur across genealogical schemes.

The difficulty for the harmonization is the pairing. *Sheba and Dedan* appear together as a fixed dyad in both the Hamite list (Gen 10:7) and the Keturite list (Gen 25:3). It is one thing to posit a coincidental homonym; it is another to posit that the same *pair* of homonyms — Sheba and Dedan, side by side, both associated with the same Arabian incense trade — independently arose in two unrelated clans. The improbability compounds. The more economical explanation, advanced by Westermann and by John Day, is that Israelite tradition preserved more than one ethnographic catalog of the Arabian peoples, and that these catalogs disagreed on whether the Sheba-Dedan complex was reckoned Cushite (a southern, Hamite affiliation reflecting the Sabean kingdoms of South Arabia) or Abrahamic-Keturite (a northern affiliation tying the Arabian tribes into Israel's own kinship through Abraham's later wife). The two filiations encode two different political-geographic claims about the same trading peoples, and the Priestly compiler who shaped the canonical book set both down without harmonizing them.

This is genealogy functioning as what anthropologists call a "charter" — a map of contemporary alliances and trade relations projected backward into eponymous ancestors. Knoppers's Anchor Bible treatment of Chronicles 1 reads the segmented genealogy precisely this way: the Chronicler reproduces inherited material as a structured table of peoples, not a register of paternity. Sarna similarly notes that the Keturah list in Genesis 25 catalogs the Arabian and Transjordanian tribes with whom Israel had contact. The two-tribes defense survives only by treating a recurring matched pair as accidental, which strains parsimony past the breaking point.

Where the critical reading lands: genuine contradiction at the level of paternity, dissolving into a coherent picture only once the lists are recognized as competing ethnographic maps rather than biological records.