postfix can't find DNS server after upgrade to ubuntu 17.04
I upgraded to Ubuntu 17.04 and discovered that postfix is not able to find the DNS server and is unable to send mail as a result.
Code:
May 19 05:49:47 alpaca postfix/smtp[4151]: 5E923BC0C2D: to=<root@alpaca.cox.net>, orig_to=<root>, relay=none, delay=0.03, delays=0.03/0.01/0/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=smtp.east.cox.net type=MX: Host not found, try again) What is the right answer? |
I can't stand the silence... :)
I don't know squat about postfix, or ubuntu, for that matter. I don't know why an upgrade of your OS would break postfix. I do know that "finding the DNS server" requires having nameserver entries in /etc/resolv.conf Please post Code:
more /etc/resolv.conf |
The contents of /etc/resolv.conf are
Code:
nameserver 68.100.16.25 |
Quote:
|
Quote:
Try the solutions proposed there and choose the one that fit your needs Regards |
Hmmm. Based on that report, this problem has been around since 2015, and it's evidently still not fixed. I wonder why it only started for me upon my recent update. Note that my machine is a desktop, always wired, though I am using DHCP.
I'm left thinking that the real solution is to switch from postfix to some other MTA if they can't get postfix working reliably. |
Quote:
Or you can run it not-chrooted, so it uses the main /etc/resolv.conf |
By "change the starting order" do you mean to follow the instructions in the linked bug report, where people talk about editing "/lib/systemd/system/postfix@.service" and adding an "After" line? It sounds like this mod might get clobbered every time postfix is updated, so it would be a bit of a maintenance nuisance. Is there some other mechanism that affects starting order?
|
Quote:
|
Quote:
Code:
[Unit] You can also try the solution at post #34 that apparently works (see post #35) |
All times are GMT -5. The time now is 12:20 AM. |