Hi all,
Thought I'd try this again. Thanks so much for your help. I'm using
bind-9.9.4-12.P2 on fedora20.
$TTL 1d
@ INSOA ns.guardiandigital.com. admin.ns.guardiandigital.com. (
2014070701 ;serial (mmddxx)
3h ;refresh every 3 hours
> IN TXT "v=spf1 mx a ip4:192.168.1.11/32 ip4:192.168.2.11/32
> a:smtp.example.com a:smtp1.example.com -all"
go away with anonymized data if you want help
espcially in case of data which will made public anyways
signature.asc
Description: OpenPGP digital signature
Hi there,
On Tue, 8 Jul 2014, Alex wrote:
... Does this look correct? ...
No, it's terrible.
Drop a line over at the SPF-users mailing list, they'll sort you out.
Use real names and addresses, then it's more than just a conjecture.
This will all be published for the world to see anyway, so
http://www.kitterman.com/spf/validate.html
- Kevin
On 7/8/2014 12:43 PM, Alex wrote:
Hi,
I have a mail server that manages mail for about ten domains, using
bind-9.9.4-12.P2 on fedora20. I'd like to make sure my SPF record in
my SOA is set up correctly, a
Hi,
I have a mail server that manages mail for about ten domains, using
bind-9.9.4-12.P2 on fedora20. I'd like to make sure my SPF record in my SOA
is set up correctly, and hoped someone could help. Currently I have the
following:
$TTL 1d
@ INSOA ns.example.com. admin.ns.example.com. (
FWIW,
I ran into this issue with www.elevationsbanking.com as well. The setup was
very similar, the record resolved to a CNAME which in turn resolved to another
CNAME. When the TTL expired on the CNAME the record would revert to NXDOMAIN.
It wasn’t until the TTL expired for the SOA that things
In article ,
Mark Andrews wrote:
>
> The adobe servers are just plain broken.
>
> Request a CNAME -> NXDOMAIN (Should return CNAME record)
> Request a TXT -> NXDOMAIN (Should return CNAME record)
> Request a NS -> NXDOMAIN (Should return CNAME record)
> Add a EDNS optio
7 matches
Mail list logo
