Reading idn(International Domain Name)

quote:
<cfoutput>
#listFirst(cgi.server_name,'.')#
</cfoutput>
I have the code like the above in my webPage
"subDomain.cfm."
(1)
http://korea.dot.kr/test/subDomain.cfm
(2)
http://한국.dot.kr/test/subDomain.cfm
If you click the link (1) in the above, you will read
"korea."
If you clikc the link (2) in the above, you will read
"xn--3e0b707e."
"xn--3e0b707e" is the puny code for the IDN
"한국" which means "korea" in korean language.
I like to read the IDN "한국" instead of the puny
code "xn--3e0b707e."

As IE7 is on the road, most major browsers support
IDN(International Domain Name)
I think Server-scripting language should support IDN,
i.e. we should read IDN in server-scripting languages.
I've heard that there are some clues for reading IDN in PHP.
http://pear.speedpartner.de/apidoc/I18N_Punycode/I18N_Punycode/_Punycode_Punycode_php.html
http://phlymail.de/index.php?sid=79a...oads&what=idna
http://www.phpclasses.org/browse/file/5845.html
Then, why can't ColdFusion read IDN?
For example,
#cgi.HTTP_HOST in ColdFusion read EDN(English Domain Name).
We need a kind of cgi variables which is likely named
"cgi.HTTP_IDN" which can read IDN instead of PunyCode.
How can I read IDN in ColdFusion?
Any suggestion will be appreciated.

Similar Messages

Puny code and IDN(International Domain Name)

quote:
code in google.cfm
<cflocation url='
http://www.google.co.kr/search?q=#listFirst(cgi.server_name,'.')#'
addToken='no'>
The code above is in
http://www.dot.kr/test/google.cfm.
if you click the above link it will go to google search page
with the keyword "
www."
if you change the sub-domain "www" to another word, it will
go to google search page with the keyword "
another word."
You can test it with the links below.
http://book.dot.kr/test/google.cfm
book
http://note.dot.kr/test/google.cfm[
note
http://adobe.dot.kr/test/google.cfm
adobe
http://movie.dot.kr/test/google.cfm
movie
http://coldfusion.dot.kr/test/google.cfm
coldfusion
http://e.dot.kr/test/google.cfm
the alphabet
e
The links above works fine as I expected.
when the sub-domain is English, it works fine like the links
above.
But the sub-domain is non-English, it goes to google search
page with the keyword in PUNY Code (xn-code).
For example,
The following link doesn't work correctly because the
sub-domain is non-English.
http://é.dot.kr/test/google.cfm
the alphabet
é
If you click the link above, it will go to google search page
with the keyword "
xn--9ca" instead of "
é"
xn--9ca" is the PUNY Code (xn code) of the IDN(international
domain name) "
é."
I like to make it go to google search page with the IDN
keyword instead of
the puny code keyword when a user enters IDN sub-domain.
(I like to make it go to google search page with the IDN
keyword "
é" instead of the puny code keyword "
xn--9ca')
Any suggestion will be appreciated.

As IE7 is on the road, most major browsers support
IDN(International Domain Name)
I think Server-scripting language should support IDN,
i.e. we should read IDN in server-scripting languages.
I've heard that there are some clues for reading IDN in PHP.
http://pear.speedpartner.de/apidoc/I18N_Punycode/I18N_Punycode/_Punycode_Punycode_php.html
http://phlymail.de/index.php?sid=79a...oads&what=idna
http://www.phpclasses.org/browse/file/5845.html
Then, why can't ColdFusion read IDN?
For example,
#cgi.HTTP_HOST in ColdFusion read EDN(English Domain Name).
We need a kind of cgi variables which is likely named
"cgi.HTTP_IDN" which can read IDN instead of PunyCode.
How can I read IDN in ColdFusion?
Any suggestion will be appreciated.

Cant Launch Firefox from Mac with UTF8 International Domain name

From a Mac running OSX 10.7, I Launch Firefox with a UTF-8 string containing an international domain name:
I try to launch http://www.vihtilä.fi and Firefox responds: Can’t connect to http://www.vihtil\xc3\xa4.fi but the address bar string is correct. If I copy the address bar string, and paste it back into the address bar, then hit enter, the site opens. Safari and Chrome launch the correct site.
\xc3\xc4 is the UTF8 representation of 'ä'
Firefox on Windows works correctly, but I pass it a WCHAR (UTF16) name.

That is weird. 
The forum makes a correct and working link (www.vihtilä.fi) via preview, but changes the URL to the escaped encodeURI version when it is posted.
I can't replicate what you are doing, but the page opens via a desktop shortcut with "-url http://www.vihtilä.fi" command line parameter.

CA stops Internal domain names for certificates

I have got this information from digicert http://www.digicert.com/internal-names.htm is there any way to ensure all clients works properly.
Should we have to change our internal domain names to external ones, this will be a problem and visible. It gives us insecured feeling.
Experts please throw your views.
Thanks!
Regards, Ganesh, MCTS, MCP, ITILV2 This posting is provided with no warranties and confers no rights. Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

Hi,
Thanks for the great information from Andy.
Following is some detailed information on Split DNS, just for your reference:
Split-brain DNS is known by a number of names, for example, split DNS or split-horizon DNS. Simply, it describes a DNS configuration where there are two DNS zones with the same namespace – but one DNS zone services internal-only requests, and the other
DNS zone services external-only requests. However, many of the DNS SRV and A records contained in the internal DNS will not be contained in the external DNS, and the reverse is also true. In cases where the same DNS record exists in both the internal and external
DNS (for example, www.contoso.com), the IP address returned will be different based on where (internal or external) the query was initiated.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Internal Domain names

I know what a domain name is for the external web, but what forms of words are acceptable to OS X Server for an intranet? I don't want to have to pay to register a domain name acceptable to the rest of the web, I just want something meaningful for my intranet such as "diary" or "wiki" - or even an IP address alone.
Do they all have to end in .local or will a single word be OK? Should they all start with http://www. or something else? OS X Server help just assumes any website being set up is for world use, and there are no instructions if you just want to set up a private intranet visible only to people on the internal network but invisible to the outside world.
Where can I go for guidance/what formats are acceptable, please?
Many thanks.

Internal domains can be whatever you want. It doesn't have to be a .com, .net or even .local
If you want you can have your own domain .bar then you can have foo.bar as a hostname in that domain.
Since it's only used internally it won't have any impact on anyone outside of your network.
Similarly, if you really wanted to, you could call your own domain 'apple.com' and then have a hostname of basilisk.apple.com pointing to your machine. Of course, this would impact your ability to get to any other .apple.com hostname, so you might not want to do that, but it is possible.
As for the 'single word' question, by definition a hostname is a component of your domain which would mean that 'foo' isn't strictly valid, however, you can configure your machine (System Preferences -> Network -> TCP/IP -> Search Domains) to automatically append specific domain names to any lookup. If you set this to 'bar' then a lookup for 'foo' would automatically look up 'foo.bar' and you'd get the result you're looking for.
Finally, for now, there is no requirement to have 'www' as pointing to your web server. That's just a common convention used around the internet. It's just as valid to have fred.bar as your web server and barney.bar as your mail server if that's what you want.

DNS not querying/ recognizing/ resolving internal domain name using nslookup

I've setup a virtual lab for practice purpose on VMware 8 workstation.
I have already asked this question in vm community but still got no answers hence asking it here.
In my vmware workstation 8, for practice lab purpose my setup is as follows:-
1] Win 2k8R2 Enetrprise edi.vm as my DC with DNS & DHCP configured and working perfect. DNS is getting resolved internally via NSLOOKUP. Server has manual ip assigned...192.168.1.xx series.
2] Win xp vm as my Client and getting dhcp lease address from the above DC and also the DNS is getting resolved internally via NSLOOKUP.
Now that these two vms are communicating perfectly with each other, I thought about connecting them to my physical internet.
So, in the Virtual network editor, I added a Host-only type network named
VMnet 04 with Use local dhcp service checkbook Disabled and on each of these vms, in network adapter settings, selected specific virtual network and pointed it to
VMnet 04 in both vms.
Now, in both the vms, an additional network connection got added and hence was successfully able to browse internet from both vms.
Now the REAL problem:--
After the above configuration, when I do NSLOOKUP on the DC, the DNS doesnt resolves external sites on the internet.
I havent specified any kind of conditional forwarding etc.., its a simple DNS setup.
I want it to resolve to the internal domain and also be connected to the internet .
What setting do I need to do in DNS or in VM network?
I tried almost all types of settings in vm virtual network editor by specifying dns manually and so on but none worked.

Sorry my bad.... slight mistake in my question...Here is my corercted query--
After successfully connecting to the internet, when I do NSLOOKUP on the DC, the DNS doesnt resolve my internal domain/site but instead resolves external sites on the internet.
My computer FQDN is nri.wwe.com
Domain dns name is wwe.com
The above should get resolve internally but it searches on the internet.
This is how it should work
& it works perfect when I disable the other NAT network adapter (i.e. disable internet connectivity on my virtual DC)
C:\>nslookup nri.wwe.com
Server: nri.wwe.com
Address: 192.168.1.11
Name:    nri.wwe.com
Address: 192.168.1.11
But when I again enable internet connectivity, this it what happens.
C:\nslookup www.wwe.com
DNS request timed out.
    timeout was 2 seconds.
Server: UnKnown
Address: 192.168.12.2
DNS request timed out.
    timeout was 2 seconds.
Non-authoritative answer:
DNS request timed out.
    timeout was 2 seconds.
Name:    www.wwe.com.nsatc.net
Address: 64.152.0.124
Aliases: www.wwe.com
And when I again nslookup, this is what I get,
C:\>nslookup www.wwe.com
DNS request timed out.
    timeout was 2 seconds.
Server: UnKnown
Address: 192.168.12.2
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out
Now this 192.168.12.2 is VM assigned DNS via VM Natting with its own DHCP. If we do it manually, none of the virtual machines can connect to the internet. So I cannot fiddle with it anymore as I have already that as well.

Internal Domain Names (good or bad?)

I'm just trying to establish what's good or bad about internal domain naming. I've currently got server.office (when viewed internally) but server.externaldomain.co.uk when viewed externally. But now the time has come to upgrade the servers and it seems a good time to reevaluate the naming and ip status of stuff. My question is that should a network's server and computers have internal dns (ala .office) or external naming linked to internal ip's (computer01.external.co.uk - 10.0.0.2)? What's the advantages of both.
Thanks.

Personally I'd stick with the same name from a user's perspective, independent of whether you're using separate DNS zones internally.
Using mail as an example, you might configure 'mail.domain.co.uk' as the hostname for your mail server.
By publishing that name in both the internal and external DNS you only need to tell users to configure their mail client to talk to mail.domain.co.uk and they'll always get connected. The magic of DNS means they'll resolve the public IP address if they're outside the network, and the private IP address if they're in the office (or on VPN, etc.). Now users don't need to maintain separate mail profiles for internal and external accounts.
Now, whether or not mail.domain.co.uk is the actual hostname of the machine on the internal network is a different matter altogether. This could easily be CNAME'd to mailserver.office on the internal zone, allowing you to maintain the .office zone on the inside network which has advantages in that you know you should never serve .office to external clients.
Personally, in my network, there are no externally-visible hostnames that match the actual machine names.

Internal Domain Name

Hello,
I am about to setup a new domain and was wondering what the new Microsoft standard is for a local domain name?
is using .local, or .lan still the standard or should we be using the companies main domain? company.com?
I've also seen some recommendations on using internal.company.com.
Any advise or recommendations would be appreciated.

Hello,
Yes. We recommend you use internal.company.com instead of .local.
Cara Chen
TechNet Community Support

MSExchangeTransport 12014 3rd Party SSL Certificate does not match internal domain name.

I have a co-existance of Exchange 2003 and Exchange 2010 and after installing a new 3rd party cert I'm getting The following error. All mail is flowing and OWA is working.
Microsoft Exchange could not find a certificate that contains the domain name Exchange.domain.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Default EXCHANGE with a FQDN parameter
of Exchange.domain.local. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate
exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
Our GoDaddy UC SAN cert is not allowed to have .local SAN names, so I have no way of adding it to the cert. Is it possible for me to install a local CA and generate a self signed cert for the personal store or would it be better to disable
TLS for the receive connector?

Change the name on the Receive Connector (2010) or on the SMTP Virtual Server (2003) to match the name in the new certificate. One of them is sending the "exchange.domain.local" in the 220 banner when it accepts a connection.
--- Rich Matheisen MCSE&I, Exchange MVP

Problem with IDN (internationalized domain name)

i want load images from a domain which contain non-latin character (ex: www.bücher.com) but Flash only display a secury message.
how to resolve this issue , please help me .Thanks.
I use as3.

Firefox only shows the IDN name if the TLD is white-listed. 
The .net domain isn't in that list and thus shows as puny code.
*http://www.mozilla.org/projects/security/tld-idn-policy-list.html
See also:
* [http://kb.mozillazine.org/network.IDN.whitelist.*]
Use the Google cache in case of problems accessing the MozillaZine KB (prefix links with cache:)
*[http://www.google.com/search?hl=en&ie=UTF-8&q=cache:http://kb.mozillazine.org/network.IDN.whitelist.*]

Server 2012 - Can't access external website from internal domain with same name. Tried everything.

Hello All.
I have read loads of forums and tried numerous fixes and configurations, but nothing seems to work and I am extremely frustrated at this point.
I have a client where I setup Server 2012 Standard with Exchange 2013. After reading best practice documentation for DNS naming and reasons not to use ".LOCAL" I opted to use ".com.na" in which case the Internal Domain Name and Internet
Website now has the same name.
When attempting to open the extarnal website eg. "www.company.com.na" from a client PC within the internal "company.com.na" Domain, I keep getting error "403 - Forbidden: Access is denied. You do not have permission to view this
directory or page using the credentials that you supplied."
I should also mention, the website is hosted by an ISP and not locally.
I added a "www" Host record in the Forward Lookup Zone, I have added the url and ip address to the Hosts file on a client pc (Windows 7) and even tried setting up Split-Brains DNS. Nothing seems to work.
Running a Tracert takes me to the correct public ip address of the website, but I keep getting this 403 error.
I am so sick and tired of this issue that iI am at the point of backing up the Exchange and re-rolling the entire server with the ".local" DNS domain name. I have a mirror setup in a VMWare environment and simply using "rendom" to rename
the domain seems to cause new issues with Exchange connectivity.
Any pointers and help will be greatly appreciated.
Thanks in advance.
Hentie Loots

I opted to use ".com.na" in which case the Internal Domain Name and Internet Website
now has the same name.
This ends up with a split-DNS stup for internal and external resolution which requires extra administration tasks and attention from the administrators.
When attempting to open the extarnal website eg. "www.company.com.na" from a client PC within the internal "company.com.na" Domain, I keep getting error "403 - Forbidden: Access is denied. You do not have permission to view
this directory or page using the credentials that you supplied."
I should also mention, the website is hosted by an ISP and not locally.
I added a "www" Host record in the Forward Lookup Zone, I have added the url and ip address to the Hosts file on a client pc (Windows 7) and even tried setting up Split-Brains DNS. Nothing seems to work.
Running a Tracert takes me to the correct public ip address of the website, but I keep getting this 403 error.
This means that you are able to reach the Website but it is responding with the access denied error message. That should be checked on the middleware level so if this is IIS running then I would recommend asking them in IIS forum: http://forums.iis.net/
If this is a Website that is completely managed by your ISP then I would recommend checking with them.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

DNS (internal domain has same name as external website)

Our internal domain name is called "abc.com" and our company website is called "abc.com". I have created an "A" record that points to
www.abc.com so staff can browse the website from within the office. The problem is that if people enter "abc.com" from a web browser with the office it does not resolve in an efficient manner. Can someone please
help?
Interflex

Hi Interflex,
I agree with Ace’s option 2 and 3 just like what I thought.
I still consider the idea which Jorge provided about prevent register DC’s A record . This probably cause some un-expected issues,
because this record is used for DFS and GPOs. So I don’t recommend this method.
Meanwhile , I have thought as same as Ace’s second suggestion, if the environment or policy of your company allow deploy IIS on your
DC server , I thought this could be a possible resolution.
And I have a tips for your reference. If client’s browser is IE, by default, when you type web address in address bar,
and press “ Ctrl + Shift +Enter “,IE will auto add Prefix WWW to the beginning of typed web address. In your case , users just type “abc” in address bar, and press “ Ctrl + Shift +Enter “
You can set this at “Prefix and Suffix option” which located at “Internet Options”/ “General”
Tab / ”language” button.
Thank.
Tiger Li
Hi Tiger,
I've actually found by default, just hitting Ctrl + Enter (without the shift key) puts in the 'www' and 'com.' but it only works for the 'com' TLD' by deffault. I guess you could add 'net' in the General tab, Language, suffix option to use ctrl-shift-enter,
or whatever the actual internal TLD name is.
Cheers!
Ace
Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003, Microsoft Certified Trainer, Microsoft MVP - Directory Services. This posting is provided AS-IS with no warranties or guarantees and confers no
rights.

How to Setup RDS custom property when internal and external domain name space is different

Hi All
I am setting up RDS for customer
My internal domain name is domain.local and my external domain is domain.com
I came across below PowerShell cmdlets on some blogs because my internal and external name space are different
Set-RDSessionCollectionConfiguration –CollectionName QuickSessionCollection -CustomRdpProperty “use redirection server name:i:1 `n alternate full address:s:remote.domain.com”
In above command, remote.domain.com points to which host?
Is it pointing to RD Session Broker
OR
Pointing to RD Session Host servers
I am not sure what above command will do exactly ?
Any help will be highly appreciated
Thanks Best Regards Mahesh

Hi,
It all depends who is accessing the RDS Solution.
If you have a large BYOD or large number of external users, it would be better to use a public certificate.
Have a look at the following script which will simplyfy the configuration of the RDSH hosts with certificates.
http://ryanmangansitblog.com/2014/05/20/rds-2012-rdsh-certificate-deployment-script/
You can use a custom RDP property to hide the Session host names.
Have a look at the following article on configuring certificates:
http://ryanmangansitblog.com/2013/03/10/configuring-rds-2012-certificates-and-sso/
Ryan Mangan | Ryanmangansitblog.wordpress.com | Help keep the forums tidy, if this has helped please mark it as an answer

Changing the internal domain to a subdomain -- Help!

Hello, so I have a huge project coming up and i was wondering if someone had some experience on this that could give me some advice.
So, started working on this company that has an internal domain called.. lets say abc.com and external alphabetaghama.org .. the problem we have is that we cannot get certs for our internal domain for public access like our exchange
server fqdn for example is exchange.abc.com ... Someone else owns abc.com which prompted my new boss to fix this and now i have a project to change our internal domain to match our external but I know that the best practice is to have a
subdomain as the internal domain and I think that's the route my boss wants to go with.. which brings me to my question.
What will I have to do to get this accomplished... our external domain name is really just a forward zone and i dont have a forest so does that mean that i will have to build a alphabetaghama.org forest and add a subdomain like corp.alphabetaghama.org
for our internal and then migrate everything over?
We currently have exchange 2007 with 2008R2 DC's.. our new domain would be on 2012R2 DCs with the same exchange server..
Sorry if something doesn't make sense, I'm a little new to a major project like this...

Hi,
This really depends on the requirements. As the Domain restructure is a huge project, we'd better have some experts with good experenses at hand. And if the problem (to get public access) is solved, it is recommended to have a good consideration
if the rebuilding is needed.
Regarding the internal domain name, maybe you want to have a look into the below MS article:
How Domain Rename Works
http://technet.microsoft.com/en-us/library/cc738208(v=WS.10).aspx
For your reference:
ADMT Guide: Migrating and Restructuring Active Directory Domains
http://technet.microsoft.com/en-us/library/cc974332(v=WS.10).aspx
One thing to mind is ADMT tool may cannot
be installed on a Windows Server 2012 DC, so please make sure in the target domain we have a Windows Server 2008 DC to be the ADMT server.
ADMT 3.2 and PES 3.1 installation errors on Windows Server 2012
http://support.microsoft.com/kb/2753560
Hope this may help
Best regards
Michael
If you have any feedback on our support, please click
here.
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. This can be beneficial to other community members reading the thread.

Best practices of having a different external/internal domain

In the midst of migrating from a joint Windows/Mac server environment to a completely Apple one. Previously, DNS was hosted on the Windows machine using the companyname.local internal domain. When we set up the Apple server, our Apple contact created a new internal domain, called companyname.ltd. (Supposedly there was some conflict in having a 10.5 server be part of a .local domain - either way it was no worries either way.) Companyname.net is our website.
The goal now is to have the Leopard server run everything - DNS, Kerio mailserver, website, the works. In setting up the DNS on the Mac server this go around, we were advised to just use companyname.net as the internal domain name instead of .ltd or .local or something like that. I happen to like having a separate local domain just for clarity's sake - users know if they are internal/external, but supposedly the Kerio setup would respond much better to just the one companyname.net.
So after all that - what's the best practice of what I should do? Is it ok to have companyname.net be the local domain, even when companyname.net is also the address to our external website? Or should the local domain be something different from that public URL? Or does it really not matter one way or the other? I've been running companyname.net as the local domain for a week or so now with pretty much no issues, I'd just hate to hit a point where something breaks long term because of an initial setup mixup.
Thanks in advance for any advice you all can offer!

Part of this is personal preference, but there are some technical elements to it, too.
You may find that your decision is swayed by the number of mobile users in your network. If your internal machines are all stationary then it doesn't matter if they're configured for companyname.local (or any other internal-only domain), but if you're a mobile user (e.g. on a laptop that you take to/from work/home/clients/starbucks, etc.) then you'll find it a huge PITA to have to reconfigure things like your mail client to get mail from mail.companyname.local when you're in the office but mail.companyname.net when you're outside.
For this reason we opted to use the same domain name internally as well as externally. Everyone can set their mail client (and other apps) to use one hostname and DNS controls where they go - e.g. if they're in the office or on VPN, the office DNS server hands out the internal address of the mail server, but if they're remote they get the public address.
For the most part, users don't know the difference - most of them wouldn't know how to tell anyway - and using one domain name puts the onus on the network administrator to make sure it's correct which IMHO certainly raises the chance of it working correctly when compared to hoping/expecting/praying that all company employees understand your network and know which server name to use when.
Now one of the downsides of this is that you need to maintain two copies of your companyname.net domain zone data - one for the internal view and one for external (but that's not much more effort than maintaining companyname.net and companyname.local) and make sure you edit the right one.
It also means you cannot use Apple's Server Admin to manage your DNS on a single machine - Server Admin only understands one view (either internal or external, but not both at the same time). If you have two DNS servers (one for public use and one for internal-only use) then that's not so much of an issue.
Of course, you can always drive DNS manually by editing the zone files directly.

Reading idn(International Domain Name)

Similar Messages

Maybe you are looking for