[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1242
  • Last Modified:

Server 2008 R2 SPF record, where is it?

Where should I be looking for the SPF record existence?  I have GFI mail essentials on site, and I'm aware they provide a free SPF service with their software, but it's currently shut off.

I'm asking because the spam that is coming from internal sources (spoofing I think this is called?) is increasing for some users.  Coming from old email addresses that are rarely used (old contacts that haven't updated their contacts list; people who remember the company as their old name, etc.).
0
mgedlaman
Asked:
mgedlaman
  • 3
  • 3
  • 3
  • +1
1 Solution
 
GovvyCommented:
0
 
PapertripCommented:
SPF records are TXT records for the parent domain.

You can look yours up at http://www.kitterman.com/spf/validate.html
0
 
PapertripCommented:
Apologies I was distracted and misspoke.   I meant an SPF record is a TXT record for the sending domain.
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
robw24Commented:
SPF records are always located on public zone records for the domain. So start with whoever is hosting your domain. Check the zone file for a "TXT" record, which would contain the SPF string. The zone file is also where you will find your mail MX records and domain host records.
0
 
GovvyCommented:
Sample to compare:

Type Domain Name TTL Record
TXT google.com 60 min v=spf1 include:_netblocks.google.com ip4:216.73.93.70/31 ip4:216.73.93.72/31 ~all
0
 
mgedlamanAuthor Commented:
Sorry guys, I wasn't clear.  I'm the new server administrator for the domain.  The DC has DNS, on it, and I thought it was in there somewhere, just didn't know where to look.  Thank you for reading inbetween the lines robw.  

I tried the tools from the above suggestions, seems the one from papertrip showed I don't have one, however, the mxtoolbox site showed a result...hard to tell from that result if there is one in place.
0
 
PapertripCommented:
What is your domain?  I can tell you if the SPF record is correct, as well as give advice for best practices.

Check out this thread I worked on from yesterday for some overall SPF info.
0
 
robw24Commented:
I run a domain with DNS servers as well, however our SPF record is not for the internal domain. It is for the public DNS server. Publishing an SPF record does not protect your own domain, it is intended to protect other domains from people pretending to be from your domain. It tells them to not accept mail from your domain unless it is coming from specific designated hosts that you define in the SPF record. For this purpose it needs to be on a public DNS server, not an internal private one. You could go to DNSSTUFF.com and put in your domain name and it will display the public records for that domain, including the SPF record if you have one.
0
 
mgedlamanAuthor Commented:
Papertrip, I appreciate your enthusiasm, I don't feel comfortable posting that here.  I will check out your other thread for further advice.  Thank you so much!

Yes Rob, it would be embarassing for our company to be sending "spam" to other companies for sure.  It would also be helpful to shield the internal domain as well though.
0
 
robw24Commented:
In order to protect your internal domain, you will utilize the SPF records of other domains. Example, if someone emails your domain from somedomain.com, you do an SPF lookup for that domain to see if that email is coming from an approved server.

As far as your internal emails being spoofed, I think you have a different problem. I really don't know anything about your setup, but your mail server should not be accepting email from internal sources, whether spoofed or not, unless it is a server or device that needs to relay off it. Email generated within your internal email server should not ever be spoofed. If it is, then it is because your email server software is allowing clients to change the sender info, which it should not so. If clients are just relaying off the server with spoofed addresses, then you need to only allow designated clients to relay off the server, not just anyone.

I could be wrong with my advice but i'm just trying to help with the limited knowledge that I have. I don't usually answer questions here, I am mostly an "asker".
0
 
mgedlamanAuthor Commented:
Thank you for sticking with this to the end Rob!  

Found out it was a single infected terminal!?  We are in the process of cleaning it :)
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now