PHOTOSKailyn Lowry’s Baby Daddy Calls Son Lux ‘A Lopez Regardless’ Of What She Named Him
Oct. 12 2017, Updated 5:09 p.m. ET
Kailyn Lowry may have given her son Lux Russell her last name, but her baby daddy Chris Lopez isn’t about to let the two-month-old forget where he comes from. The Teen Mom 2 star’s ex took to Instagram to call out Kail’s decision to give Lux her last name and remind her that their son will always be “a Lopez regardless!”
Chris posted this photo of Lux with the caption, “You watch Floyd one time now you think you can fight. Love you boy #youngking #YouALopezRegardless.”
Kail recently revealed that she went ahead with naming Lux without Chris’ input. “I finally decided on a name because it felt like I was going nowhere with Chris trying to decide,” she told TheAshleysRealityRoundUp.com.
While Kail said Chris had already agreed to Lux’s first name, she had yet to find out how he felt about his middle name, Russell, and his last name, Lowry!
- Jenelle Evans' Son Jace Hints Reality Star Kicked Him Out After She Called 911 on Him: ‘I Didn’t Do S---'
- Kailyn Lowry Says It's a 'Difficult Time for Me' in Alleged Vulnerable Message as Cheating Rumors About Her Fiancé Elijah Scott Swirl
- Kailyn Lowry and Elijah Scott Blast Breakup Rumors as They Put on a United Front: 'Fake News'
Want OK! each day? Sign up here!
Judging by his post and hashtag, it seems Chris wishes his son had gotten his last name! Chris also revealed that he’s missing Lux amid his court case with Kail. “Missing you something serious right now,” he captioned this pic.
As OK! readers know, Kail is currently taking Chris to court to force him to acknowledge paternity of Lux. “My guess is he won’t acknowledge paternity so she can’t file for child support,” a source close to Kail told RadarOnline.com exclusively.
“Her lawyer drew something up and they are going through the court because he doesn't have any rights to Lux without signing,” the insider explained. “He's not seeing the baby right now for those reasons.”
What do you think of Chris’ post? Sound off in the comments below!
