Redirect public DNS record to url

I am looking for advise as to what to do. I want to take my mail.xxxx.com record and point it to a url such as http://something.some.thing/mail
Is this possible to do? It seems like I should be able to do this somehow.
cheers

Sounds like you're getting a little confused. There is no correlation between a DNS host entry and a URL - you can't have a DNS record that points to 'http://something.somewhere.net/mail'.
What you can do is point your DNS entry to an IP address of a server that's running a web server. Now when users enter your hostname in a web browser they'll connect to this server.
You then configure the web server to automatically redirect to /mail if that's where you want the user to end up. The process would be something like:
DNS: mail.somewhere.net -> x.x.x.x
Server x.x.x.x runs a web server.
Web server redirect / requests to /mail
Now a user can enter http://mail.somewhere.net/ and end up talking to http://mail.somewhere.net/mail/ thanks to the web server, not the DNS server.
To do this you'd add a line like:
Redirect / /mail/
to your web site configuration.

Similar Messages

Lync Edge and Proxy server public DNS records port forwarding rules

Hi All
I have question in regards to port forwarding rules for port 443 of simple url.
I have 4 public ip addresses.
1 edge server (4 nics , 3 running with different ip for sip, meet and dialin in DMZ network, 1 connected to internal local network).
1 proxy server (2 nics, 1 running with an ip which is in DMZ same as edge, and 1 connected to internal local network)
1 front end (lync 2013 standard installed.) connected to internal local network
1 office web apps . connected to internal local network
The question is that I am using 3 public ip addresses respectively on public DNS records for sip, meet and dialin(av) and using port 443 which has been set on edge server. So , I can use 3 DMZ network ip address on edge for sip, meet
and dialin (av) port forwarding from 3 public ip addresses as per in Microsoft document.
However, I also have a reverse proxy .Hence, my understanding is all public DNS records except SIP and port 443 should be pointed and port forwarded to reverse proxy ip address which is in DMZ network as it would redirect 443 and 80 to 4443 and 8080 to front
end.
Now the question has been clear, if simple URLs public DNS record and port forwarding rules for port 443 should be pointed to reverse proxy server, why they need to be set on each ip address and port number in Front end server topology to edge server?
If anyone knows, please give a help how to set it correct and what is supposed to be a correct configuration for a topology lync 2013

Hi George
Thanks for your reply. Attached is my topology which could make my it bit clear. You may see the public dns host record from the image. I set sip, meet, dialin , and owa 4 host records. The first 3 records are pointed to lync edge by doing a NAT with port
443 which is the same as per you said. However my understanding is they should be pointed to reverse proxy instead as for instance, I need meet.xxx.com with port 443 to be redirected to port 4443 through reverse proxy server to the front end. So when the external
customers who do not have lync client installed to their machine then we can shoot a lync meeting and send to them via outlook and they just need to click on join lync meeting link in the email to join in such a meeting based on IE. (Is my understanding correct?)
If lync web meeting works like so , then the question is why I need to set three SAME addresses in front end topology builder for edge and make them point to edge server instead?　
１. Access Edge service (SIP.XXX.COM) ---> I understand that it is used for external login lync front end.
2. Webconf edge server(Can I set to meet.xxx.com which is the same as simple URL that points to reverse proxy?) ----> If I can set this address to be the same as simple url address that points to reverse proxy, why should it need to be NATed to edge
instead? TO BE HONEST, if I HAVE tested, if I set this url as sip.xxx.com which means to use a single FQDN and ip address with port 444 and points simple url meet.xxx.com to reverse proxy, it will still work to join lync meeting sent by
outlook.I DO NOT REALLY UNDERSTAND WHAT this URL used for at this stage.
3. AV edge --- same as webconf
Regards
Wen Fei Cao

Exchange 2013 CAS DNS Round robin Public DNS Record

Dear All,
If I am going to use DNS round robin as CAS redundancy. How should I map the public DNS record? Do I need to map 2 public IP for 2 CAS server to the mail domain? THanks
Best Regards,
Elroy

Dear Elroy
I am not sure about the success rate of your implementations but yes if it is round robin what you require you need add 2 ip addresses.
Suggestion:
Why don't you implement a CAS with a load balancer and then you can map the Public IP to the one IP on the Load Balancer.
Good Luck.

DNS records to be created for Lync deployment (Internal and External)

Hi There,
If I want the Lync server environment to work Internal as well from External in all the aspects. (auto-discover, meetings, AV conferencing,web conferencing, voice integration, mobility etc), please answer to the below questions and also their purpose please.
I'm not sure whether the answer varies for 2010 and 2013 version.
1. What are the Internal and External(public) DNS records to be created for the reverse proxy(assume i'm using TMG servers), and their purpose?
2. What are the Internal and External(public) DNS records to be created for Lync Edge server, and their purpose?

I'll try to answer as well.
1) For the reverse proxy, you'll need to publish the following:
External:
lyncdiscover.sipdomain.com (You'll need this record for every sip domain you have). This is for client autodiscover.
external web services FQDN (You'll need one of these per pool, you get to choose the name). This is for address book downloads, web conferencing, etc.
Meet.sipdomain.com (You can choose the name here, and have one per sip domain or one for the whole org). This is for web conferencing.
Dialin.sipdomain.com (You'll just need one here, it doesn't have to be dialin). This is for changing your conferencing/phone pin, resetting conference info, and general conferencing info.
For Lync 2013 only, you may want the Office Web Application server pool name as well for PowerPoint sharing. Lync 2010 doesn't use this.
Internal:
The external web services FQDN. You'll need this available internally through the reverse proxy so you can redirect requests on port 443 to port 4443. This will be used for mobile devices on WiFi.
2) For the Edge server:
Externally:
sip.sipdomain.com (you'll need one per sip domain) this is an autodiscover/multi use FQDN and should point to your access edge IP.
webedge.sipdomain.com (edge web conferencing, you can pick any name you like).
avedge.sipdomain.com (av edge, you can pick any name you like).
accessedge.sipdomain.com (you'll need a name for the access edge role, however you can just use sip.sipdomain.com and save a name in your certificate request).
Internally:
edgepool.sipdomain.com (you can pick any name you want, it's just the name assigned to the internal edge interface.
If you choose to have a single ip for the external edge, you can get away with just an access edge name and/or sip.sipdomain.com
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Internal and Public DNS conflict breaks mail

History:
We set up a new Mac Mini Server to replace our existing Server. The Mac Mini Server is setup behind a Time Capsule, which acts as our router and DHCP server. It also acts as our firewall on the public IP address and forwards mail to our internal server. Our situation is almost identical to the example situation on page 18 to 19 in the 'Getting Started' guide.
Our ISP acts as our DNS server and they host our public website. They also used to host our mail, but we have now moved the mail to our new in-house server. We asked our ISP to update their MX records to point to our static public IP address. Public DNS records for server.mydomain.com also resolve to this IP address.
When we originally set up the new mac mini server, the ISP had not yet updated the MX records. I am wondering if this affects how the Server sets up DNS on the local server machine?
Issue:
The local server machine on the local LAN is called server.mydomain.com, which resolves via local DNS (hosted by our server) to the server's internal IP address. (The local DNS server was setup automatically by the Server during initial installation / setup.) This conflicts with with public DNS records which identify server.mydomain.com with our public IP address at 205.200.19.225. This somehow causes confusion for the server which consequently seemingly randomly resets our domain (mydomain.com) and host name (server.mydomain.com) settings under Mail settings - which breaks our mail service. (We then edit these to the correct settings and all works again.)
I spoke to an Apple tech and they advised that we reinstall the Server operating system, using a local server name that differs from the public name. e.g. server.mydomain.lan (local) vs. server.mydomain.com (public).
*This may seem like a dumb question*: Would it be easier to keep our local host and DNS set up to server.mydomain.com and then rather have our ISP change the records for our public address / IP to mail.mydomain.com or public.mydomain.com? If we could make the change via the ISP's records versus our own, then it would save us a lot of work.
*A second potentially dumb question:* Since we rely on our ISP for DNS name servers, could we delete / stop the local DNS server for the local network and just use straight IP addresses instead?
*Plan of Action:*
Assuming that there is not an easy fix via the ISP's DNS records, then I'll reinstall the operating system and use server.mydomain.lan as the local machine and domain name. If I do this, then what should I be using as the domain and host name settings in mail? .com or .lan?
Should there be any need to manually configure DNS settings to make Mail work?

Mr Hoffman and Corbywan - thanks for the interesting and educational discussion. I must admit that I am still a bit confused and would appreciate any further help in understanding this issue!
*My situation:*
- Server on a LAN, which sits behind a Time Capsule router.
- The Time Capsule router serves DHCP and Internet to the LAN and sits on our public static IP Address.
- Our ISP has set up MX and domain records to forward public requests for our domain to our static IP address.
- Time Capsule acts as our firewall and forwards Mail and other incoming services to our internal server via port forwarding.
- Local DNS service is provided by the local server so that it can provide services to the local network. Non local requests are forwarded to the ISP DNS service.
*The problem*
We seem to have established that Snow Leopard Server breaks when the internal domain name matches the public domain name, because of conflict between the internal and public DNS which resolve to different IP addresses for the same domain.
*The solution*
I am looking for the easiest and most basic way to fix this problem. My understanding is that the simplest would be to reinstall our Snow Leopard Server to a new and different local domain name.
I am thinking of using server.example.lan for our local LAN domain name - which would be resolved to our private IP address via local DNS on the local server. I would be keeping server.example.com for our public domain name - which would be resolved to our public IP address, which would be forwarded from the Time Capsule to the internal server.
Now where I start getting confused is this: If Snow Leopard Server requires a Fully Qualified Domain Name to do things like send mail, then do I need to register my internal domain name? And how would this resolve from a public DNS server to the internal private IP address? Or is it more an issue where as long as the internal (albeit 'fake') domain name does not conflict with an existing public domain name?
*Other items:*
After setup, I will verify that Snow Leopard Server has setup our local DNS correctly for local DNS service.
If I understand correctly, I would set up Mail Settings - 'Domain Name' as the local domain name: i.e. example.lan and I would set up the Host Name as server.example.lan - is this correct? Would this work if these are not FQDN?
How does the mail server reconcile these local domain names with the public domain names? I assume that I need to check the box at Mail - Settings - Advanced - Hosting: "Include server's domain as local host alias" ? Or would I manually add an alias to the Local Host Aliases under the same tab?
Thanks!

When do I have to update my DNS records for my URLs, such as mail and autodiscover?

We currently have EX2010, with autodiscover.domain, owa.domain, and outlook.domain records in DNS. The outlook.domain is used for the CAS array and would not be modified during this.
We are going to install new EX2013 servers soon. When we do that, we plan to set all the URLs to be the same as EX2010 (like above).
From what I can tell, I do not have to change the DNS records until we actually start to migrate mailboxes. Would that be correct? I would rather do some additional testing, and get our load balancers configured correctly, before pointing autodiscover
and owa at EX2013.
Most of the documentation I have seen says change the DNS records at the end of your installation, but that would be if I was ready to migrate mailboxes I would think.
Thanks for any help or assistance on this. I have read all of the articles on the Exchange Blog site, but nothing really says make this change immediately.

Hi DarlonJeel,
Based on your description, I know you want to upgrade Exchange 2010 to Exchange 2013.
After you've completed the installation of Exchange 2013, you could update the MX record and the Autodiscover record to the Exchange 2013 CAS Server.
Don’t worry about that the users whose mailboxes are located in Exchange 2010 server. When a user uses OWA or OutlookAnywhere, Exchange 2013 CAS server will redirect to the Exchange 2010
CAS server automatically.
Hope it helps,
Best regards,
Eric

How to configure Exchange 2010 to use a certain MX record that is unavailable with public DNS

Dear all,
as for TLS encryption I'm required to send emails destined for a certain domain via a dedicated send connector that has TLS encryption enabled/enforced. Thing is that the recipient's corresponding domain MX records cannot be resolved using public DNS. As soon
as I verify MX records for the recipient's domain using nslookup I only receive MX records that do not accept TLS. In order for TLS to work I'm required to send all outgoing emails to that specific domain via a certain predefined host, i.e. MX record, that
is known to me and Exchange needs to know as well. But how can I configure Exchange to use a certain MX record (that resolves to mxtls.<domain>.com instead of mx.<domain>.com without being available in public DNS?
Editing the hosts file directly on the Exchange server? Not an option, right?
Messing with my ADS integrated DNS not an option, too, as I then have to add all sorts of entries for that zone, e.g. www and stuff like that, to make it work?
I'm lost here, any help would be greatly appreciated.
Alex
Alexander Ollischer Diplom-Wirtschaftsinformatiker (FH) Citrix & Microsoft Certified Engineer (CCEA, CCEE, MCSA, MCSE, MCDBA, MCTS) Afontis IT+Services GmbH Baierbrunner Straße 15 81379 München Deutschland Telefon (089) 74 34 55-0 Fax (089) 74 34 55-55
mailto:[email protected] http://www.afontis.de http://www.itganzeinfach.de Amtsgericht München, HRB 109 005 Geschäftsführer: Thomas Klimmer

Well, I figured it out by myself. I just had to add the corresponding server, i.e. mxtls.<domain>.com, to the Smarthost configuration for the corresponding Send Connector and set its RequireTLS setting to $True.
Alex
Alexander Ollischer Diplom-Wirtschaftsinformatiker (FH) Citrix & Microsoft Certified Engineer (CCEA, CCEE, MCSA, MCSE, MCDBA, MCTS) Afontis IT+Services GmbH Baierbrunner Straße 15 81379 München Deutschland Telefon (089) 74 34 55-0 Fax (089) 74 34 55-55
mailto:[email protected] http://www.afontis.de http://www.itganzeinfach.de Amtsgericht München, HRB 109 005 Geschäftsführer: Thomas Klimmer

How do I setup a DNS record to point to an internal IP with a port.

I am trying to setup a DNS entry on my AD server to point to a web sever that I have setup to run certain services. All of these services run through IIS on port 82 for example service A is internally 192.168.0.1:82/info/login and service B is 192.168.0.1:82/tech/login.
I am trying to give these services easy to use names like for example info.mycompany.com and tech.mycompany.com so that it is easy to access for the employees but I am obviously missing something because I have had no luck setting up anything. My
company is still using SBS 2003 as it's AD and DNS server so I am working with flint and bear skin here.
I am also trying to do the same thing for the external access to these services but where as I have the internal address for these services I have the external static IP. When using the external IP with the port from outside the network everything
works fine but I would like for it to to have a simple name identical to the internal names but accessible from the outside. I frankly feel out of my depth on both of these issues and I would really appreciate any help that can be lent. Thank you.

You cant set a dns record (that would be used by a browser) to point to an ip and port, srv records can but that requires the application to look them up.
To have info.mycompany.com point to 192.168.0.1:82/info/login you
would add a cname or A record to the dns pointing to that IP, then in IIS you would assign that dns name to the host headers. Also in IIS you would need to use
URL rewrite plugin with this you would setup a redirect for that host header {HTTP_HOST} to point to that link.

DNS Records Confused

Hi everyone,
I have did the transtion from Exchange 2007 to Exchange 2013.
My Exchange 2007 URLS were with mail.mydomain.com and hostname of the exchange 2007 server was mail.
I came up with Exchange 2013 with hostname mail1
mail : 192.168.1.10 (Exchange 2007)
mail1 : 192.168.1.15 (Exchange 2013)(all virtual directories i set to mail.mydomain.com)
After decommisioning Exchange 2007 i changed exchange 2013 server to the old ip of Exchange 2007
mail1 192.168.1.10
I created
A record mail pointing to 192.168.1.10(mail.mydomain.com)? is it right
Now i have two records mail and mail1 pointing to same ip 192.168.1.10
Autodiscover record pointing to 192.168.1.10(autodiscover.mydomain.com)? is it right
should my MX record be pointing to mail or mail1
Should i create an SRV recoard?
Please do guide me ,i am able to open Exchang admin center and owa web pages but i am not able to login.
For outlook or active sync, what should be the incoming and outgoing mail server(mail.mydomain.com or mail1.mydomain.com)
I want to use mail as used earlier with exchange 2007

The mail part of mail.mydomain.com for purposes of finding your mail server is not referring to the name of the server as in server1.mydomain.com so the name of your server is not important.
But your certificate should match whatever that is. So for example my mailserver uses webmail.mydomain.org on the certificate so this is what the internal and external DNS records are pointed to even though the server has a name completely
unrelated to that. Also, my internal domain is mydomain.local so I created a separate DNS zone internally for webmail.mydomain.org and put the A record (with the internal IP) for my exchange server in there.
So from internally when you look for webmail.mydomain.org you find the internal IP address of the exchange server and when externally looking for the same thing, webmail.mydomain.org you find the external IP address of the exchange server.
Since you have put the new server at the old server IP you should not have to change DNS records externally and if you have DNS configured internally you should not have to change those either.
You do not need srv or mx records internally. An mx record would be an external record to help people find your mail server on the internet but as I said, since you put the new server at the same IP, presumably you already have external
DNS and firewall settings to allow access.
What you need to do is set the virtual directory addresses and the Service Connection Point for the new server.
First verify your DNS by pinging mail.mydomain.com both internally and externally.
Internally it should resolve to 192.168.1.10. Externally it should resolve to whatever public IP provides external access through your firewall to the server sitting at that internal IP.
Set the SCP for the new server using EMS (this assumes that your internal ping results above worked correctly):
Set-ClientAccessServer -Identity mail1 -AutoDiscoverServiceInternalURI https://mail.yourdomain.com/autodiscover/autodiscover.xml
You said you already did this part below but you can verify or do it again.
Configure virtual directories for mail1.
Go to ECP and navigate to Servers >> Virtual Directories
Select mail1 then click the wrench
Add mail1 at the top and then enter mail.yourdomain.com
Back in the Servers >> Virtual Directories section of ECP click on the virtual directories one at a time and then click the edit pencil and copy and paste to make the internal URL match the external one.
Do this for OWA, ECP, ActiveSync, EWS and OAB. Skip autodiscover and powershell!
Once all of this is done your OWA would be accessed at
https://mail.mydomain.com/owa and your ecp would be accessed at
https://mail.mydomain.com/ecp from both inside and outside your organization.

Redirect Mobile Browsers to Alternate URL.

I have weblogic 10.3 in place currently and I would like to redirect mobile browsers to an alternate URL. What is the best way to accomplish this?
Thanks
George
Edited by: user6039076 on Mar 30, 2012 12:03 PM

Hi,Johnathan,
Are the other phones Windows Phone?If not please make sure you have input the correct format of user information when connect.
Did you connect the Lync mobile using automatic connection or manual connection?
When you use automatic discovery, mobile devices use DNS to locate resources. During the DNS lookup, a connection is first attempted to the fully qualified domain name (FQDN) that is associated with the internal DNS record (lyncdiscoverinternal.<internal
domain name>). If a connection cannot be made by using the internal DNS record, a connection is attempted by using the external DNS record (lyncdiscover.<sipdomain>). However, both the internal Mobility Service URL and the external Mobility
Service URL are associated with the external Web Services FQDN. So the Lync mobile will connect to the external web service regardless it connect internally or externally which is just on the oppsite of your scenario.
I doubt there should be something wrong with your DNS record or the publishing rule ,would you pleae double check them?
Besides,please enable diagnose log on your phone and the other phone then send the log file to your email and compare them to find out the difference for troubleshooting.
Regards,
Sharon
Sharon Shen
TechNet Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

Smart Hosts & DNS records

Hi All.
I hope someone could assist me as I have been struggling with mail flow issues for a long time.
We have our own in house exchange server and internal mail as well as incoming mail is 100 %.
We have always used our ISP smart host to send email and started getting email flow issues a couple of months ago.
I then switched over to sending email via DNS. I setup the correct DNS records eg Reverse Lookup record and SPF records as i thought this might be an issue. I have also cleared our domain off one or 2 blacklists. (We had a user account compramised and spammers
were using that account to send email)
This is now all cleared up and general outbound email flow is going great, but once again we are now experiencing issues with all clients filtering with Mail Marshall.. Message as below:
Your message did not reach some or all of the intended recipients.
Subject: Email
Sent: 2014/09/16 09:02 AM
The following recipient(s) cannot be reached:
[email protected] on 2014/09/16 09:02 AM
There was a SMTP communication problem with the recipient's email server.
Please contact your system administrator.
<example.example.org.za #5.5.0 smtp;550 Message refused by MailMarshal SpamProfiler>
Has anyone got any advice on what I can do. The failed report doesnt give much help. I have also sent an email with just text to see if maybe its the email signature but still
no luck.
I'm thinking of switching back to the ISP as a smart host but I'm not sure if the SPF and reverse DNS records would cause an issue now.
Would our clients not look at the reverse and SPF record and see that the IP (ISP Smarthost) doesn't match our IP lised in the public DNS ?
Much Appreciated.
Shaun

Hi.
I contacted the support for Mail Marshal and they got back to me and sorted out the issue. It seems fine for now.. They were really helpful I must say.
The response from them for anyone else with the same issue perhaps.
Regards,
Shaun
Hi Shaun,
It is not a blacklist exactly. SpamProfiler is run on a fingerprint (or pattern) basis. It scans the content of the email message and then acts accordingly to the fingerprints it finds. Due to emails containing your
email domain being submitted as spam and/or mails you sent hitting honey pots, the fingerprint of your domain was flagged as a spam URL. Hence the recommendation to audit your mailing lists. So it was the pattern of the domain that was in the system. Unfortunately
that is not something you can check on MX Toolbox, as Cloudmark (the company that provides the fingerprints for SpamProfiler) does not make their fingerprints publically available

Use of Public DNS Server

I have an iMac, Mac Mini and a Macbook Pro connected to a Airport Extreme Base Station. I normally use a Public DNS Server and I am not sure where to put the DNS URLs. Do I put them on the individual computers or is there somewhere in the Airport Extreme Base Station that they go? where ever they belong please provide location and instructions. Thanks.

Configuring the AirPort Extreme with the DNS makes it so that you do not have to configure each individual computer on the WLAN, the DNS settings will be handed down to the devices when they are given their internal IPs, but as long as the base station does not have a competing/conflicting DNS setup, configuring each individual device, as suggested by Carolyn, works also.
However, something strange can happen sometimes when you use a public DNS setup. I use the one Carolyn suggests, OpenDNS, but I cannot access any of the webpages of my ISP with this configuration. I have Todo en Uno (All in One), a service that provides cable, telephone and internet service from my local cable company, CableVisión. So with the OpenDNS setup I cannot configure the digital options for my telephone service, such as blocking and unblocking Int'l long Distance calls. I have to remove the OpenDNS setting to do so. But I created a work around using Locations in the Network settings. I have one Location with my ISP's DNS settings and another Location with OpenDNS settings. I can quickly switch between the two when I need to access my ISP's website.
Dah•veed

Exchange Server 2013 internal and external DNS records

I recently installed Exchange Server 2013 and I've register a pubic ip too for exchange server. How can I create internal DNS as well MX record for my Exchange server to send and receive internet mails. It's my first time configuring exchange for a organization.
registered domain name=====np.bbcmediaaction.org
public ip=====202.166.212.221

Hi,
For external mail flow, we need the following DNS records: MX records for the domain part of the external recipient, A records for the destination messaging servers. For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/bb676467(v=exchg.150).aspx
Additionally, to ensure external mail flow works well, we also need to configure send connector.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

DNS Records Questions - TXT Files

Hello everyone, I would like to preface this post with, this is my first time dealing with DNS records. However, the instructions seem a little confusing, so i would like your professional feedback.
Currently using Godaddy for hosting. Ill start with the instructions, then my set up, my result and my questions.
Instructions:
You will be adding two separate TXT entries to your DNS record - note - be sure that you do not add any carriage returns when copying the key, below:
First Entry (This is called the DKIM policy record):
Name: _domainkeyTXT: "t=y; o=~;"If your domain is 'foo.com', then the 'name' entry will look like this when it is displayed as: "_domainkey.foo.com"
Second Entry: (This is called the 'selector record' and includes a public crypto key):
Name: key1._domainkeyTXT: "k=rsa\; p=MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAKQrQeUnNX/CQBIXWqeHc8lKl+EwhGKzPuDRbDjnN2Xzl8N4Fc2oQ6R+opnEM6U4x4p
3NggEyNg8Mp2W6oUYpAECAwEAAQ=="
If your domain is 'foo.com', then the 'name' entry for this will look like this when it is displayed: "key1._domainkey.foo.com"
That's it!
You can send a test message to a yahoo email address, then select Actions->View Full Headers in Yahoo
when you view the email. If you have configured DKIM correctly, the header information for the email will include a line similar to:
Authentication-Results: mta1084.mail.mud.yahoo.com from=mypinpointe.com; domainkeys=pass (ok)
Fisrt Entrey
Hostname: @
TXT Value: _domainkey.mydomain.com: t=y; o=~;
TTL: 1/2 hour
Second Entry:
Hostname: @
TXT Value: key1._domainkey.mydomain.com: k=rsa; p=MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAKQrQeUnNX/CQBIXWqeHc8lKl+EwhGKzPuDRbDjnN2Xzl8N4Fc2oQ6R+opnEM6U4x4p3NggEyNg8Mp2W6oUYpAECAwEAAQ==
TTL: 1/2 hour
Results
1. a really long string of code, but when you search for it here is the result Doesnt say domainkeys=pass (ok):
Authentication-Results: mta1466.mail.gq1.yahoo.com from=giglinxusa.com; domainkeys=neutral (no sig); from=crapemyrtle.mypinpointe.com; dkim=pass (ok)
Questions
1. Should the TXT value include "", like they have it in the instructions?
2. In the first entry, should there be so many spaces after the .com: t=y
3. What are carriage returns? (assuming spaces)

Hello,
but I don't understand anything else then you will use Godaddy.
What is the aim of this? Connecting an email domain to your internal network or about web services? Please be more specific in your description what you are trying to achieve.
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

My domain add WWW will redirect to DNS server's Domain, IE works ok,What's the reason

I have a website, and I had added both @ and WWW A record on host. I set the domain as the home page, They all work ok in IE, WWW failed work in Firefox. What are the reasons?
//My domian is http://www.hey-deals.com, hey-deals.com works fine, but http://www.hey-deals.com cannot work in Firefox! It redirect to DNS server's domain, how to set?
Thanks!

I have Windows capability but have never used it. I can't imagine anyone using anything other than Pages for Word Processing, etc. I use Safari and Firefox for Browsing. I use Safari primarily and Firefox occassionally. I have not used Internet Explorer for years and years. In fact, I was sort of surprised when I learned that some people do still use Internet Explorer.
I wasn't sure whether or not there was an Ultra-Safe way to go about checking to discover whether or not Apple Users had to worry about a problem with this particular bug.
Although there IS a link provided in the Denver Post's on-line version of this particular news article, I hated to click on a strange link - even if it was provided by the local newspaper. It is just as easy for the local newspaper to be fooled by bogus links as it is for anyone else to be fooled.
My understanding from friends is that there are a whole lot of local newspapers - all across the country - who are currently running this news article - or an article very similar to it.
So it would seem to me that a whole lot of Apple users all across the country might suddenly be wondering whether or not they have anything to worry about - and whether or not there was an Ultra-Safe way for Apple users to check all of this out.
I contacted my service provider about this issue but, so far, have not heard anything back from them.
Thanks for the response.
Sincerely,
Hannah

Redirect public DNS record to url

Similar Messages

Maybe you are looking for