I have a couple of web sites and an hmailserver on my VPS. I recently noticed that comcast, and I guess others, are rejecting email where there is no PTR or rDNS. I can set up the PTR in DNS but not sure about the rDNS. I came across an old blog that shows how to do it in older versions of IIS but I'm not sure if this is the right way or how to do it in IIS-10
Say I have 3 domains
myDomain1.com and MyDomain2.com both use Ip x.x.x.y
and myMailServer.com uses Ip x.x.x.z
DNS for these are all set up on cloudflare. MX records for the MyDomain1 and MyDomain2 both point to mail.MyMailserver.com. I use hmailserver and all this works fine.
Comcast says I need a PTR record which I can set up on Cloudflare, and rDNS which is what I'm asking about.
This blog
http://www.expta.com/2010/01/how-to-enable-reverse-dns-lookup-in-iis.html
shows how to do it in earlier versions of IIS (I am on IIS-10) using IP Address and Domain Restrictions
So my questions are :
1 - if this is not the right way then please redirect me! else
2 - Do I use Allow Entry or Deny Entry?
3 - Do I use the mail domain x.x.x.z for all or the ip assigned in DNS - or both?
4 - do I do this for all domains?
Thanks
You need to go to your VPS provider to check their control panel for the PTR/rDNS setup. Usually all the VPS providers has this functionality in their control panels. If not, then ask them to add a proper PTR record for your IP address pointed to your hostname.
The hostname itself should be with proper A record pointed to the IP address of your VPS server.
Separate PTR record setup should be created for all your IPs.
Related
I am just wondering if this is possible/how I could go about doing this.
I work for a company that has their domain name registered on Site A while their hosting is on Site B. This is no issue as we just have the Registrar at Site A point the Name Servers to Site B. Easy.
Where I get a little confused, is say I would like to use a CDN such as CloudFlare (Site C), typically in a basic case, I would go to the registrar/host and just change my Name Servers to the ones given by CloudFlare. However if my Registrar and Domain Host are different, it appears someone could get lost in the mix, as if I go from Site A point to Site C .. how does host at Site B supply Site C with all the information to host and control the CDN for?
Thanks for the insight!
I reached out to CloudFlare and got this very simple, perfect answer.
Here's how it will work for you :
At your domain registrar, you will set your authoritative name servers to the ones that CloudFlare will assign to you when you sign up.
Within CloudFlare, using our dashboard, you will configure your DNS zone file to point your domain to the IP address of the server assigned to you by your hosting provider.
The CloudFlare reverse proxy does the rest!
Hope this helps!
Setup within the AWS ecosystem is multiple web sites across 2 domains using ELB, SSL, IIS & ASP.NET across 2 EC2 instances.
After a security audit, we discovered our cookies weren't set to secure, so I setup a URL rewrite to look for the appropriate header from ELB and set HTTPS to true. The problem is, users started getting emails stating https://www.test.com:80/ as the domain and unfortunately, we have too many references to Request.Url to make a change quickly.
Obviously IIS requires a different IP address (or port number) to host 2 SSL certificates. If we change the port number, we'll still have the same issue, so we were hoping to add a secondary IP address and point ELB to use it, but that doesn't appear to be supported. I'm fairly new to AWS, so I was hoping someone could give me some direction in terms of getting SSL to terminate within IIS on ELB.
So what I am asking is, is there a way to get ELB to use a specific IP Address instead of a generic EC2 instance which uses the primary IP Address?
Thank you in advance,
Andrew
If we change the port number, we'll still have the same issue,
No, you wouldn't.
Set up a second ELB using standard ports toward the Internet and custom ports toward the instance(s).
I'm running five wordpress sites (#EC2) all having it's own elastic IP tied to a proper domain name. I reached the max limit when wanted to launch another site (another domain).
Besides of the obvious; asking for more EIPs, can I use route 53 and pointing to the dynamic EC2 hostname?
As far as I understand this will destroy/mess-up all internal links of the wordpress instance, the moment I reboot or stop/start the instance, because it gets a new IP/hostname and all image-links of wordpress by default are absolute for SEO reasons.
Has anybody found a solution to this, or is my only option to ask for more EIPs?
In my opinion, requesting more EIP's is going to be the easier way to go.
You can set up your DNS to point the public ip of any instance, if its not an eip, it will change if the instance ever stop/started again. In which case you need to update DNS.
Wordpress doesn't really care what the hostname or ip address is of the instance. It cares what hostname you want it to respond to. Even if the underlying ip changes, as long as the hostname records are updated to the new IP, you wont have any issues.
I have installed WordPress on a subdomain that currently resides on an unpropogated domain. (It can only be accessed via IP address.) Is it possible for me to access any subdomains that have been created, eg: subdomain.mysite.com/wp-admin via IP, or do I have to wait till the domain has been propogated?
This is my first question, I apoligize if I have not explained my self thoroughly enough. Thanks in advance for any help.
you can use http://[IP]/~[username]/[domain.tld]/ to access your site by IP.
Where [IP] is the IP of your server and [username] is your username for the hosting site. [domain.tld] is the name of the folder on which you have mapped your subdomain.
You may be able to check it with an anonymous proxy?
I use http://anonymouse.org/anonwww.html to check sites as in Australia it normally takes a little longer to propagate over to here.
Please note: You will only be able to check it's existence, you would not use this to make site modifications through the back end. That would best be done once the domain propagates.
Hope this helps ;)
I would like to know if it is possible using IIS and ASP.NET (and ideally something that might be employed on a shared hosting account, but this isn't required) to mimic WordPress.com's ability to allow end users to use their own domain names.
WordPress has users who own their own domains change the domain's DNS settings to point to WordPress's own DNS. My guess is this is not something that would be able to be done on a shared hosting account since it would involve adding an entry to the DNS server's table for each custom user domain.
However, for future reference, is this something that might be automated programmatically on perhaps a VPS?
My guess is this is not something that would be able to be done on a shared hosting account
You're nearly correct. The default site in IIS listens to all connections on port 80 for the default IP address.
You can add more sites in 3 ways:
Add new sites listening on different ports. This is not entirely practical if you want "ordinary" sites litening on port 80.
Add more IP addresses to the box (not too eaisly done) and set up new IIS sites to listen to the new IP addresses independently.
Add new sites to the server listening to different "host headers" (domain names to you and I) but on the same (default) IP address .
So called "Shared hosting" usually uses options 3, because a hosting company can get away with only using a single IP address for possibly hundreds of sites.
Therefore you would have to go through the tedious process of adding each host header to the box, and while I'm almost certian this could be done with Wscript, I'm no expert in that area.
If you really wanted to get into it, you could write an ISAPI module to intercept the calls and set up some clever (ish) database/hash table of domain names and target folders to server as the different sites.
Bottom line is, there are various ways to achieve this on Windows. Probably none quite as easy as on a *nix platform where everything is super-scriptable.
What we do is have a wildcard DNS entry set up for our domain. That way, whatever domain the user types will resolve to our website as long as it ends with ".mydomain.com". Then our .Net code just looks at the "HOST" header coming in and serves up the content that matches that domain name.