If is possible to find out which nameservers a domain was previously pointing too? I need to try and find where a domain was previously hosted so that I can try and gain access to an old hosted email account.
Any ideas?
If is possible to find out which nameservers a domain was previously pointing too? I need to try and find where a domain was previously hosted so that I can try and gain access to an old hosted email account.
Any ideas?
I've seen articles about "different subdomains for different MX records".
But I want two records for the same domain, @abc.example
for example.
Originally, I used Live Mail(MSN) to host my emails, and already have MX setup for it. Now I want to use some of the Google App features, so I need to setup MX for Google Mail.
Can both of the two work together and well?
Say you own a abcd.com
and you only want to use it to send and receive email via [email protected]
. You don't want to provide any kind of website.
Can you set up the DNS records to include an "MX" record and no "A" record?
Is this enough for sending and receiving email to work?
Is this valid in terms of whatever standard defines these things?
Edit: To clarify, the mail server (terminology?) would not be hosted on abcd.com or *.abcd.com
I'd like to feel more confident setting up mail for my clients with regards to false positives. Here's what I know:
SPF records are good, but not every spam filter service/software (SFSS) uses them.
reverse DNS (PTR) records are pretty much a necessity.
Open relays are bad.
(Here's "other tips" I've read):
the reverse lookup of the IP address of your mail server should resolve to the domain that you're sending mail out from.
your server should say HELO FQDN.of.your.mail.server.com when speaking to other mail servers.
the A host records in MX records should be (or resolve to to the IP address) your FQDN.of.your.mail.server.com
Feel pretty good about 1 and 3. Here's where I'd like some clarification/suggestions:
2 and 4: I did alot of digging and this seems to be incorrect as most spam-filters are looking for a PTR in general and one that's not generically-assigned by the ISP; it doesn't appear that the domain you send mail out as has anything to do with this (i.e. if you owned two domains you used for mail, you'd need to send out from two IP addresses with PTRs for each?)
This makes sense, but does it care what that FQDN resolves to? Should it resolve to the IP address that's currently sending said HELO?
Again, another one from various Google searches; don't see how this would work if you used Postini as your gateway service (or any other smarthost for that matter).
And what about sending on behalf of another domain that you're not authoritative for? I have some clients (some.branchdomain.tld) that are required to send mail out as @some.corporatedomain.tld, even though said corporate HQ won't setup a relay/smarthost for them to use. corporatedomain.tld can create SPF records to show that some.branchdomain.tld is allowed to send mail, but would that still be considering "spoofing", especially if said SFSS doesn't check SPF records? Should I be concerned about this?
Let us say we own the zone mywebservice.com.
I would like each of my customers to get their own subdomain, such as customer.mywebservice.com.
customer.mywebservice.com needs to be a CNAME to a given server offsite. Since that site manages its own equipment and can change addresses at any point in time, the CNAME is a requirement.
People also need to be able to send email to [email protected], which would require a simple MX record.
However, and this is where I'd like some guidance:
According to RFC 1034:
If a CNAME RR is present at a node, no other data should be
present; this ensures that the data for a canonical name and its aliases
cannot be different.
I have also verified that my DNS server will refuse to serve up anything but a CNAME for hosts that use them.
So, it seems that I may have a losing situation. If I want to use the MX record, I need to use an A instead of a CNAME.
Can anyone think of any workarounds? Thanks!