LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 06-08-2018, 03:58 AM   #16
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 15,717

Rep: Reputation: 2222Reputation: 2222Reputation: 2222Reputation: 2222Reputation: 2222Reputation: 2222Reputation: 2222Reputation: 2222Reputation: 2222Reputation: 2222Reputation: 2222

A registered DNS entry resolves on the internet. We seem to be having an internal network issue. I imagine 192.168.x.x has a private use entry internet wide (e.g. on Cox Communications). Your question of how this started happening in a stable system is a good one. A backup restoration should solve it. Perhaps an external file was changed. Updates also have odd results, although not usually in critical network files. This usually becomes apparent after a solution is found.

The OP hasn't supplied hostnames. If the domain is hostname.ohprs.org, and hosts are resolved in the server, it should work. I don't see a way to resolve 192.168.0.x addresses at the moment. That's why I suggested the hosts file.
 
Old 06-09-2018, 10:58 AM   #17
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 2,395

Original Poster
Rep: Reputation: 172Reputation: 172
It's now working. I added 192.168.0.5 (sending) to 192.168.0.3's (receiving) /etc/hosts file, then restarted sendmail on both 192.1680.3 and 192.168.0.5. All of the pending undelivered email then got delivered with no "does not resolve" log messages thereafter. I then removed the hosts entry from 192.168.0.3 and restarted sendmail on 192.168.0.3 to see if that made any difference. So far (a day later) mail continues to be delivered sent from 192.168.0.5.

I'm not entirely sure what made the difference. Perhaps restarting sendmail on one or both hosts. Host 192.168.0.5 was rebooted a few days before the OP in this thread, so I would think that would constitute a fresh restart of sendmail on that host. 192.168.0.3 was rebooted only 9 days ago. A mystery, but it's now working. Perhaps one or both sendmail restarts did the trick.

I still can't do 'dig @192.168.0.3 hostname', but that's another problem I'll deal with later in a different thread.

Thanks for all the feedback!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Sendmail doubling sender domain- ex. hostname.domain.net.domain.net halborr Slackware 7 08-23-2010 09:37 AM
DNS http:domain.com resolve to www.domain.com keysorsoze Linux - Networking 3 02-12-2007 04:03 AM
what would make ever virtual domain name resolve to one domain name on my system kuplo Linux - Newbie 1 11-14-2005 07:57 PM
fetchmail-sender domain doesn't resolve tincat2 Linux - Software 5 05-03-2005 09:29 AM
Sender domain must exist? J_Szucs Linux - Software 5 09-11-2003 12:38 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 04:10 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration