I've my domain hosted on Google Cloud DNS however my email provider is a 3rd party i.e iPage. After adding fields as recommended by iPage i.e adding '#' and '' as host and mx.ipage.com as pointer but it still isn't working. My email starts from info# but in the dns name, I'm actually adding '#' and ''. Am I doing the right way?
Here is a screenshot of GC DNS:
https://i.ibb.co/71GfBK7/Capture.png
Here is a link to the ipage reqs for registering MX record:
https://www.ipage.com/help/article/dns-management-how-to-update-mx-records
Thanks but I got it now. Actually, you don't have to add * or # infront of the dns name. Just leave it blank and it works instantly.
Related
I want to transfer my e-mail accounts to Yandex. I use Cpanel at hosting server.
I get an error when adding Yandex mx addresses, "mx.yandex.net." I can't add address with dot. Error says: "It must have a valid TLD tag." I stuck here.
I had the same problem.
I could manage to fix it by deleting all old MX records and adding a new one
Priority: 10
Destination: mx.yandex.net
enter image description here
You also need to add the TXT record
v=spf1 redirect=_spf.yandex.net
enter image description here
I'm a newbie in domain names, DNS etc.
I'm using surge.sh for deploying my app. Now I want to add a custom domain, that I registered using transIP, and I can't get it working. I set the IP address to 45.55.110.124, as they explain here. All together, I entered the following settings:
Name: *
TTL: 1 min
Type: A
Address: 45.55.110.124
And another one, exactly the same but then using name #:
Name: #
TTL: 1 min
Type: A
Address: 45.55.110.124
I created a test page that contains hello domain, inside a simple html file. Now, I deployed the page by moving to the folder that contains the html file and doing: surge ./ mydomain.io.
I waited over 5 minutes and nothing is changing.
Now, my questions are:
What am I doing wrong?
My domain provider suggests that I also use an IPv6 address, but which one should I use for Surge?
Why is there an option of setting TTL longer than 1 minute, who wants to wait longer before their deploy comes online?
For starters, you want to use the CNAME instead of A record if possible. The reason for this is that their IP address can possibly change out from under you when infrastructure changes / updates / re-deploys. If possible, remove the A records and create CNAME records pointing to na-west1.surge.sh. instead.
Next, assuming that they want you to point to the same IP as na-west1.surge.sh resolves to, that IP is different from the documentation (possible even due to my previous explanation). You can ping the domain or use the host utility to get the current IP address:
$ host na-west1.surge.sh
na-west1.surge.sh has address 138.197.235.123
Armed with this information, try changing to CNAME records first. If this isn't possible, then use the updated IP address that you get from resolving the their CNAME.
How can I set up DKIM with the DNS record for the domain we use for mails being sent from Parse.com, like registration emails?
Parse has only this one line of instructions:
"Run the following in your terminal: dig +short k1._domainkey.parse.com txt for the most up-to-date DKIM value."
But what next? The output is something like this: "k=rsa\; p=MIGfMA0GCSqGSIb3...44Dyfnzp7zmQIDAQAB".
How does the DNS entry has to look like?
Like this?
k1._domainkey.parse.com IN TXT "k=rsa\; p=MIGfMA0GCSqGSIb3...44Dyfnzp7zmQIDAQAB"
You need to put this on your own DNS. If your domain is company.com, a record like this in your company.com zone file should do it:
k1._domainkey.company.com In TXT "k=rsa\; p=MIGfMA0GCSqGSIb3...44Dyfnzp7zmQIDAQAB"
Just make sure that parse.com will DKIM sign the message with your company.com domain and set d=k1!
According to http://dkimcore.org/c/keycheck, I needed to delete the \ after k=rsa for the key type to be valid.
In WSO2 Enterprise Store 1.0.0 there is a mix about the hostname used to make connections.
You can set HostName and MgtHostName in carbon.xml. But there are files with fixed names, like
sso-idp-config.xml: (AssertionConsumerService) https://localhost:9443/store/acs
jaggeryapps\store\controllers\ login.jag: (postUrl) "https://" + process.getProperty('carbon.local.ip') + ":" ...
localhost breaks every remote connection. IP address breaks SAML authentication and is not consistent with 3rd party certificates.
Is there an easy way to set the hostname all over the ES?
I tried this scenario only by updating AssertionConsumerService within sso-idp-config.xml and it works for me.
So you have to only update AssertionConsumerService within sso-idp-config.xml.
To work properly, the full list of files I had to modify is:
repository\conf\sso-idp-config.xml
repository\deployment\server\jaggeryapps\publisher\controllers\login.jag
repository\deployment\server\jaggeryapps\publisher\controllers\logout.jag
repository\deployment\server\jaggeryapps\social\controllers\login.jag
repository\deployment\server\jaggeryapps\social\controllers\logout.jag
repository\deployment\server\jaggeryapps\store\controllers\login.jag
repository\deployment\server\jaggeryapps\store\controllers\logout.jag
repository\deployment\server\jaggeryapps\store\themes\store\js\asset.js
login/logout files use the IP address (a bad choice when working with third-party certificates. It also breaks SAML authentication).
I lost a lot of time locating files with IP and localhost references. I think it should be reviewed and documented in future versions of the product.
I have setup a catchall router on exim (used as last router):
catchall:
driver = redirect
domains = +local_domains
data = ${lookup{*#$domain}lsearch{/etc/aliases}}
retry_use_local_part
This works perfectly when sending emails locally. However, if I login to my GMail account and send an email to whatever#mydomain.com, then I get an "Unrouteable Address".
Thank you for any hints to solve this issue.
In the system_aliases: section of the config file you already have a section which does the lookup in /etc/aliases.
Replace
data = ${lookup{$local_part}lsearch{/etc/aliases}}
with
data = ${lookup{$local_part}lsearch*#{/etc/aliases}}
and make sure you have *:catchall_username* in /etc/aliases
This works great for a single domain mail server which is already using /etc/aliases
For this router to work, make sure that
mydomain.com is in local_domains
there is an entry for *#mydomain.com in /etc/aliases
MX record for mydomain.com is pointing to the server, where you've
configured this
This is old as heck, but I didn't see a good answer posted and someone else might want to know the answer.
This post is geared towards Debian with in single configuration file mode. It should work on any Linux Exim4 install though. For the purpose of explaining things we’ll use test#example.com which is configured with the hostname mail.example.com. The system will have a real user called test and we want to create an alias for test called alias. So the end result will all email sent to alias#example.com forwarded to test#example.com without having to create the user alias on the system.
First we need to create a place to store all of the alias files:
mkdir /etc/exim/aliases.d
vim /etc/exim/aliases.d/mail.example.com
contents of the alias file for mail.example.com alias:test
vim /etc/exim/exim4.conf.template
Now look for the section system_aliases. Here you’ll see data = ${lookup{$local_part}lsearch{/etc/aliases}} or something similar. Change that to
data = ${lookup{$local_part}lsearch{/etc/exim4/aliases.d/$domain}}
Save the file and restart exim. The alias should now work. To add support for other domains just add more alias files in the aliases.d directory with the correct hostname.
I copied and pasted this from my blog:
0xeb.info