DNS Help ...
-
We were contacted today by a former vendor who used to manage our website but who we have since replaced. They were asking us to make a change to our DNS records because they said one of our entries was pointing to an incorrect IP that was causing them some issues. I see what they are saying but I don't think it is being caused by our DNS records but can't explain the behavior either.
So the entry in question is mail.braswellfamilyfarms.com.
If I ping this server then I get the following result :
Which I think is correct. This matches what is in our DNS records.
However if I dig on the IP address that the vendor supplied then I get :
This also seems to be resolving to mail.braswellfamilyfarms.com as shown in the answer section. I'm guessing this is why they are having an issue but I don't know where the configuration error lies. I don't think it is in our DNS records. Where does dig get this information from that would resolve to the same hostname as a straight ping?
-
PTR records are handled by the ISP.
They are not something that should ever result in a domain name like this. but at some point in history, people always tried to contact their ISP to have PTR updated to thier mail server DNS name.
-
@JaredBusch said in DNS Help ...:
PTR records are handled by the ISP.
They are not something that should ever result in a domain name like this. but at some point in history, people always tried to contact their ISP to have PTR updated to thier mail server DNS name.
it's part of anti-spamming.
-
This is THEIR entry handled by THEIR ISP, in case that wasn't clear from the above. This should never cause them a problem, but they are free to ask their ISP to change it. It has nothing to do with you.
-
Sounds like that former vendor is desperately in need of some IT support.
-
@Dashrender said in DNS Help ...:
@JaredBusch said in DNS Help ...:
PTR records are handled by the ISP.
They are not something that should ever result in a domain name like this. but at some point in history, people always tried to contact their ISP to have PTR updated to thier mail server DNS name.
it's part of anti-spamming.
No, it is not.
-
@JaredBusch said in DNS Help ...:
@Dashrender said in DNS Help ...:
@JaredBusch said in DNS Help ...:
PTR records are handled by the ISP.
They are not something that should ever result in a domain name like this. but at some point in history, people always tried to contact their ISP to have PTR updated to thier mail server DNS name.
it's part of anti-spamming.
No, it is not.
This kind of thing might be what Dash is thinking of.
https://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults/?Number=KBA-01904While not explicitly a tool for anti-spam, I remember an MDaemon installation I inherited have reverse lookups enabled.
-
@EddieJennings said in DNS Help ...:
@JaredBusch said in DNS Help ...:
@Dashrender said in DNS Help ...:
@JaredBusch said in DNS Help ...:
PTR records are handled by the ISP.
They are not something that should ever result in a domain name like this. but at some point in history, people always tried to contact their ISP to have PTR updated to thier mail server DNS name.
it's part of anti-spamming.
No, it is not.
This kind of thing might be what Dash is thinking of.
https://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults/?Number=KBA-01904While not explicitly a tool for anti-spam, I remember an MDaemon installation I inherited have reverse lookups enabled.
NO, old guides used to claim that you needed to setup PTR for on site Exchange to make sure you had not SPAM issues. I know what he is talking about. Jus tthat it has never been fact, no matter what people used to say.
-
@JaredBusch said in DNS Help ...:
@EddieJennings said in DNS Help ...:
@JaredBusch said in DNS Help ...:
@Dashrender said in DNS Help ...:
@JaredBusch said in DNS Help ...:
PTR records are handled by the ISP.
They are not something that should ever result in a domain name like this. but at some point in history, people always tried to contact their ISP to have PTR updated to thier mail server DNS name.
it's part of anti-spamming.
No, it is not.
This kind of thing might be what Dash is thinking of.
https://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults/?Number=KBA-01904While not explicitly a tool for anti-spam, I remember an MDaemon installation I inherited have reverse lookups enabled.
NO, old guides used to claim that you needed to setup PTR for on site Exchange to make sure you had not SPAM issues. I know what he is talking about. Jus tthat it has never been fact, no matter what people used to say.
I'm with Jared on this. Yes, historically it was common to do this thing but it was a myth. It's just one of those things that people repeated a lot but had no technical reasoning behind it. People generally don't understand DNS and so DNS becomes one of those magic black boxes and once someone made up that PTR could have something to do with SPAM people ran with it. But it was never part of a spam blocking or reduction mechanism, it was just a random, foolish technical mistake that people made thinking that it might have something to do with something else that they didn't understand.
