Clear sendmail MX server cache or DNS cache issue? Announcing the arrival of Valued Associate...

Why is my conclusion inconsistent with the van't Hoff equation?

If a contract sometimes uses the wrong name, is it still valid?

What is a non-alternating simple group with big order, but relatively few conjugacy classes?

String `!23` is replaced with `docker` in command line

How to call a function with default parameter through a pointer to function that is the return of another function?

What does this icon in iOS Stardew Valley mean?

Using et al. for a last / senior author rather than for a first author

Identify plant with long narrow paired leaves and reddish stems

How to answer "Have you ever been terminated?"

Output the ŋarâþ crîþ alphabet song without using (m)any letters

Fundamental Solution of the Pell Equation

Is it fair for a professor to grade us on the possession of past papers?

English words in a non-english sci-fi novel

How to deal with a team lead who never gives me credit?

Error "illegal generic type for instanceof" when using local classes

List *all* the tuples!

Is it true that "carbohydrates are of no use for the basal metabolic need"?

Storing hydrofluoric acid before the invention of plastics

Is the Standard Deduction better than Itemized when both are the same amount?

Can an alien society believe that their star system is the universe?

Apollo command module space walk?

What would be the ideal power source for a cybernetic eye?

How can I make names more distinctive without making them longer?

Why do people hide their license plates in the EU?



Clear sendmail MX server cache or DNS cache issue?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!DNS - Any way to force a nameserver to update the record of a domain?Default DNS server as assigned by SonicWall 3500, how to change which DNS server is usedDNS cache issue or apache vhosts confusion?Workstations' records not updating in DNSSendmail on Ubuntu trying to use Google Apps servers as a relay, by default?Does SendMail cache DNS records? If so, how can this be flushed and what logic does it use?Sendmail server keeps relaying mail to wrong serverRouting mail from domain to external providerDo something with dns caching after transfering site to new hostingWindows DNS Server: Problems after DNS server cache clearing. What does Clear-DnsServerCache do?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I have recently switched our mail server to a new location by updating the appropriate DNS MX records in the domain. Everythings seems to work and I am getting the email on the new server already.



However, some applications on a web server that is using sendmail to send messages, are still sending messages to the old server. I assume there is either a cache meachanism in sendmail that "remembers" the old MX server or some sort of DNS cache in place (no dnsmasq or nscd installed).



How do I make the web server's sendmail use the new MX server?



Ubuntu 12.10










share|improve this question
















bumped to the homepage by Community 13 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 2





    what if you log into that webserver and run dig mx domain.com from there. Does that show the correct record?

    – Halfgaar
    Feb 4 '14 at 13:19











  • yes, the correct server is listed in the answers section when running dig

    – Roman Semko
    Feb 4 '14 at 14:44











  • What is the TTL of the MX record, BTW?

    – Halfgaar
    Feb 4 '14 at 14:53











  • What WAS the TTL of the MX records? Have you checked that new records are propagated to ALL secondary DNS servers of the DNS domain?

    – AnFi
    Feb 5 '14 at 13:29


















0















I have recently switched our mail server to a new location by updating the appropriate DNS MX records in the domain. Everythings seems to work and I am getting the email on the new server already.



However, some applications on a web server that is using sendmail to send messages, are still sending messages to the old server. I assume there is either a cache meachanism in sendmail that "remembers" the old MX server or some sort of DNS cache in place (no dnsmasq or nscd installed).



How do I make the web server's sendmail use the new MX server?



Ubuntu 12.10










share|improve this question
















bumped to the homepage by Community 13 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 2





    what if you log into that webserver and run dig mx domain.com from there. Does that show the correct record?

    – Halfgaar
    Feb 4 '14 at 13:19











  • yes, the correct server is listed in the answers section when running dig

    – Roman Semko
    Feb 4 '14 at 14:44











  • What is the TTL of the MX record, BTW?

    – Halfgaar
    Feb 4 '14 at 14:53











  • What WAS the TTL of the MX records? Have you checked that new records are propagated to ALL secondary DNS servers of the DNS domain?

    – AnFi
    Feb 5 '14 at 13:29














0












0








0








I have recently switched our mail server to a new location by updating the appropriate DNS MX records in the domain. Everythings seems to work and I am getting the email on the new server already.



However, some applications on a web server that is using sendmail to send messages, are still sending messages to the old server. I assume there is either a cache meachanism in sendmail that "remembers" the old MX server or some sort of DNS cache in place (no dnsmasq or nscd installed).



How do I make the web server's sendmail use the new MX server?



Ubuntu 12.10










share|improve this question
















I have recently switched our mail server to a new location by updating the appropriate DNS MX records in the domain. Everythings seems to work and I am getting the email on the new server already.



However, some applications on a web server that is using sendmail to send messages, are still sending messages to the old server. I assume there is either a cache meachanism in sendmail that "remembers" the old MX server or some sort of DNS cache in place (no dnsmasq or nscd installed).



How do I make the web server's sendmail use the new MX server?



Ubuntu 12.10







domain-name-system sendmail






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 4 '14 at 14:17









Gabriel Talavera

1,1971917




1,1971917










asked Feb 4 '14 at 12:30









Roman SemkoRoman Semko

1084




1084





bumped to the homepage by Community 13 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 13 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 2





    what if you log into that webserver and run dig mx domain.com from there. Does that show the correct record?

    – Halfgaar
    Feb 4 '14 at 13:19











  • yes, the correct server is listed in the answers section when running dig

    – Roman Semko
    Feb 4 '14 at 14:44











  • What is the TTL of the MX record, BTW?

    – Halfgaar
    Feb 4 '14 at 14:53











  • What WAS the TTL of the MX records? Have you checked that new records are propagated to ALL secondary DNS servers of the DNS domain?

    – AnFi
    Feb 5 '14 at 13:29














  • 2





    what if you log into that webserver and run dig mx domain.com from there. Does that show the correct record?

    – Halfgaar
    Feb 4 '14 at 13:19











  • yes, the correct server is listed in the answers section when running dig

    – Roman Semko
    Feb 4 '14 at 14:44











  • What is the TTL of the MX record, BTW?

    – Halfgaar
    Feb 4 '14 at 14:53











  • What WAS the TTL of the MX records? Have you checked that new records are propagated to ALL secondary DNS servers of the DNS domain?

    – AnFi
    Feb 5 '14 at 13:29








2




2





what if you log into that webserver and run dig mx domain.com from there. Does that show the correct record?

– Halfgaar
Feb 4 '14 at 13:19





what if you log into that webserver and run dig mx domain.com from there. Does that show the correct record?

– Halfgaar
Feb 4 '14 at 13:19













yes, the correct server is listed in the answers section when running dig

– Roman Semko
Feb 4 '14 at 14:44





yes, the correct server is listed in the answers section when running dig

– Roman Semko
Feb 4 '14 at 14:44













What is the TTL of the MX record, BTW?

– Halfgaar
Feb 4 '14 at 14:53





What is the TTL of the MX record, BTW?

– Halfgaar
Feb 4 '14 at 14:53













What WAS the TTL of the MX records? Have you checked that new records are propagated to ALL secondary DNS servers of the DNS domain?

– AnFi
Feb 5 '14 at 13:29





What WAS the TTL of the MX records? Have you checked that new records are propagated to ALL secondary DNS servers of the DNS domain?

– AnFi
Feb 5 '14 at 13:29










1 Answer
1






active

oldest

votes


















0














This requires more information. Sendmail doesn't cache DNS information, the DNS-client caches information, but not always. For example, Ubuntu doesn't cache DNS records by default (since 2011).



If your MX records are updated on your Name Server, then you need to flush the cache on your web server in order for it to query your Name Server for the new MX record; otherwise, the TTL value of your previous MX record will fix the issue on its own in 24-72 hours.




  1. Validate the MX record on the name server

  2. Clear cache from web server that has issue (dependent on your OS)


Confirm lookups on webserver by using dig (linux) or nslookup (winodws):




  • Using dig: http://www.madboa.com/geek/dig/

  • Using nslookup:
    http://support.microsoft.com/kb/200525






share|improve this answer
























  • Thanks for your reply. Dig shows correct MX entry (I am on Ubuntu 12 as specified in the question). the problem persists for over a week now. :-/

    – Roman Semko
    Feb 6 '14 at 5:34











  • Are you running dig on the web server? If you are and the DNS lookups are correct. Then you have your sendmail server hard-coded and it has nothing to do with cache. Check your sendmail installation on the web server and see if you have a smarthost configuration pointing to the wrong mail server. Check your /etc/mail/sendmail.mc for a section like "define(`SMART_HOST', <WrongMailServer>)dnl". If so, remove it and restart sendmail. If that doesn't pan out, then check your email headers to determine what mail servers they're using.

    – David George
    Feb 7 '14 at 17:58














Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f573071%2fclear-sendmail-mx-server-cache-or-dns-cache-issue%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














This requires more information. Sendmail doesn't cache DNS information, the DNS-client caches information, but not always. For example, Ubuntu doesn't cache DNS records by default (since 2011).



If your MX records are updated on your Name Server, then you need to flush the cache on your web server in order for it to query your Name Server for the new MX record; otherwise, the TTL value of your previous MX record will fix the issue on its own in 24-72 hours.




  1. Validate the MX record on the name server

  2. Clear cache from web server that has issue (dependent on your OS)


Confirm lookups on webserver by using dig (linux) or nslookup (winodws):




  • Using dig: http://www.madboa.com/geek/dig/

  • Using nslookup:
    http://support.microsoft.com/kb/200525






share|improve this answer
























  • Thanks for your reply. Dig shows correct MX entry (I am on Ubuntu 12 as specified in the question). the problem persists for over a week now. :-/

    – Roman Semko
    Feb 6 '14 at 5:34











  • Are you running dig on the web server? If you are and the DNS lookups are correct. Then you have your sendmail server hard-coded and it has nothing to do with cache. Check your sendmail installation on the web server and see if you have a smarthost configuration pointing to the wrong mail server. Check your /etc/mail/sendmail.mc for a section like "define(`SMART_HOST', <WrongMailServer>)dnl". If so, remove it and restart sendmail. If that doesn't pan out, then check your email headers to determine what mail servers they're using.

    – David George
    Feb 7 '14 at 17:58


















0














This requires more information. Sendmail doesn't cache DNS information, the DNS-client caches information, but not always. For example, Ubuntu doesn't cache DNS records by default (since 2011).



If your MX records are updated on your Name Server, then you need to flush the cache on your web server in order for it to query your Name Server for the new MX record; otherwise, the TTL value of your previous MX record will fix the issue on its own in 24-72 hours.




  1. Validate the MX record on the name server

  2. Clear cache from web server that has issue (dependent on your OS)


Confirm lookups on webserver by using dig (linux) or nslookup (winodws):




  • Using dig: http://www.madboa.com/geek/dig/

  • Using nslookup:
    http://support.microsoft.com/kb/200525






share|improve this answer
























  • Thanks for your reply. Dig shows correct MX entry (I am on Ubuntu 12 as specified in the question). the problem persists for over a week now. :-/

    – Roman Semko
    Feb 6 '14 at 5:34











  • Are you running dig on the web server? If you are and the DNS lookups are correct. Then you have your sendmail server hard-coded and it has nothing to do with cache. Check your sendmail installation on the web server and see if you have a smarthost configuration pointing to the wrong mail server. Check your /etc/mail/sendmail.mc for a section like "define(`SMART_HOST', <WrongMailServer>)dnl". If so, remove it and restart sendmail. If that doesn't pan out, then check your email headers to determine what mail servers they're using.

    – David George
    Feb 7 '14 at 17:58
















0












0








0







This requires more information. Sendmail doesn't cache DNS information, the DNS-client caches information, but not always. For example, Ubuntu doesn't cache DNS records by default (since 2011).



If your MX records are updated on your Name Server, then you need to flush the cache on your web server in order for it to query your Name Server for the new MX record; otherwise, the TTL value of your previous MX record will fix the issue on its own in 24-72 hours.




  1. Validate the MX record on the name server

  2. Clear cache from web server that has issue (dependent on your OS)


Confirm lookups on webserver by using dig (linux) or nslookup (winodws):




  • Using dig: http://www.madboa.com/geek/dig/

  • Using nslookup:
    http://support.microsoft.com/kb/200525






share|improve this answer













This requires more information. Sendmail doesn't cache DNS information, the DNS-client caches information, but not always. For example, Ubuntu doesn't cache DNS records by default (since 2011).



If your MX records are updated on your Name Server, then you need to flush the cache on your web server in order for it to query your Name Server for the new MX record; otherwise, the TTL value of your previous MX record will fix the issue on its own in 24-72 hours.




  1. Validate the MX record on the name server

  2. Clear cache from web server that has issue (dependent on your OS)


Confirm lookups on webserver by using dig (linux) or nslookup (winodws):




  • Using dig: http://www.madboa.com/geek/dig/

  • Using nslookup:
    http://support.microsoft.com/kb/200525







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 4 '14 at 14:45









David GeorgeDavid George

6541720




6541720













  • Thanks for your reply. Dig shows correct MX entry (I am on Ubuntu 12 as specified in the question). the problem persists for over a week now. :-/

    – Roman Semko
    Feb 6 '14 at 5:34











  • Are you running dig on the web server? If you are and the DNS lookups are correct. Then you have your sendmail server hard-coded and it has nothing to do with cache. Check your sendmail installation on the web server and see if you have a smarthost configuration pointing to the wrong mail server. Check your /etc/mail/sendmail.mc for a section like "define(`SMART_HOST', <WrongMailServer>)dnl". If so, remove it and restart sendmail. If that doesn't pan out, then check your email headers to determine what mail servers they're using.

    – David George
    Feb 7 '14 at 17:58





















  • Thanks for your reply. Dig shows correct MX entry (I am on Ubuntu 12 as specified in the question). the problem persists for over a week now. :-/

    – Roman Semko
    Feb 6 '14 at 5:34











  • Are you running dig on the web server? If you are and the DNS lookups are correct. Then you have your sendmail server hard-coded and it has nothing to do with cache. Check your sendmail installation on the web server and see if you have a smarthost configuration pointing to the wrong mail server. Check your /etc/mail/sendmail.mc for a section like "define(`SMART_HOST', <WrongMailServer>)dnl". If so, remove it and restart sendmail. If that doesn't pan out, then check your email headers to determine what mail servers they're using.

    – David George
    Feb 7 '14 at 17:58



















Thanks for your reply. Dig shows correct MX entry (I am on Ubuntu 12 as specified in the question). the problem persists for over a week now. :-/

– Roman Semko
Feb 6 '14 at 5:34





Thanks for your reply. Dig shows correct MX entry (I am on Ubuntu 12 as specified in the question). the problem persists for over a week now. :-/

– Roman Semko
Feb 6 '14 at 5:34













Are you running dig on the web server? If you are and the DNS lookups are correct. Then you have your sendmail server hard-coded and it has nothing to do with cache. Check your sendmail installation on the web server and see if you have a smarthost configuration pointing to the wrong mail server. Check your /etc/mail/sendmail.mc for a section like "define(`SMART_HOST', <WrongMailServer>)dnl". If so, remove it and restart sendmail. If that doesn't pan out, then check your email headers to determine what mail servers they're using.

– David George
Feb 7 '14 at 17:58







Are you running dig on the web server? If you are and the DNS lookups are correct. Then you have your sendmail server hard-coded and it has nothing to do with cache. Check your sendmail installation on the web server and see if you have a smarthost configuration pointing to the wrong mail server. Check your /etc/mail/sendmail.mc for a section like "define(`SMART_HOST', <WrongMailServer>)dnl". If so, remove it and restart sendmail. If that doesn't pan out, then check your email headers to determine what mail servers they're using.

– David George
Feb 7 '14 at 17:58




















draft saved

draft discarded




















































Thanks for contributing an answer to Server Fault!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f573071%2fclear-sendmail-mx-server-cache-or-dns-cache-issue%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

Список ссавців Італії Природоохоронні статуси | Список |...

Українські прізвища Зміст Історичні відомості |...