I don't know where should I post this...
So the issue is cannot add target in External endpoint if there is "one word only" between "."
Example:
example.com - working
abc.example.com - working
a.abc.example.com - working
abc.a.example.com - is not working
guest.v.example.com - is not working
The error message is "This value is neither an IP address nor a fully qualified domain name (FQDN)."
If Microsoft staff see this, please fix this. I didn't pay for open case...
I also face the same error and such FQDN abc.a.example.com can not be added in External endpoint.
From this Azure feedback, you could add IP address there in this case.
Traffic Manager support for external endpoints that are IP addresses
instead of FQDN is available.
Related
I have purchased a server through GoDaddy and when I access WHM or the CPanel, it uses the IP address of the server rather than the host name. How to I change this to use the host name and put SSL on that host name?
You could access WHM both on IP and hostname. Please check if your server actually has a valid hostname. If not, then you can't use WHM via hostname, so you'll have to configure a domain on that server and create a hostname for your WHM server.
Upon provision I was given a hostname of the form:
s192.168.2.###.secureserver.net This will not resolve in a browser. Nor will a ping -a to an IP address. It is a temporary hostname. It will work for creating resellers and putting up websites but you will not be able to secure it with an SSL cert as far as I know. You need a hostname that is also a domain that resolves to your server's primary IP address to allow login to WHM.
And the server has a requirement for hostnames as being an FQDN. The requirements for an FQDN are:
- Do not select a hostname that begins with www or a number, or a hostname that ends with a hyphen (-).
- You must use a fully-qualified domain name (FQDN) that contains two periods (for example, hostname.example.com).
- Do not choose a hostname that a cPanel account on your server will use.
- Do not choose a potential proxy subdomain as a hostname (for example, cpanel.example.com or whm.example.com).
- Do not select a socially-unacceptable hostname. The hostname will appear in mail headers.
- Only use lowercase, Latin-script letters in hostnames.
On the part that requires that you install an SSL for connecting to a URL and port number I cannot address yet but I purchased a cheam domain name from Godaddy, it was then auto parked.
Went into the DNS records for the domain and pointed the A record to the primary IP address of the server.
Record: A # 192.168.2.#### TTL: 18000
You will want to delete all the other records listed there as an FQDN cannot have any subdomain or potential proxy. So no CNAMEs allowed.
Leave Godaddy's name servers NS as they are.
Give the domain settings time to propagate. (i.e. 15min - 24hours)
Connect back to your WHM via ip (https://192.168.2.###:2087)
Navigate to Basic Setup or enter Basic Setup into the search and click on the link.
Change the NS servers at the bottom of the page to GoDaddy's name servers.
Save Settings change.
Enter the new hostname in the Set Up Networking section of WHM's Initial Setup Assistant interface.
Save your settings.
Navigate to your new domain name preceded by "https://" and followed by ":2087" (i.e https://mynewhostname.com:2087 ).
I believe this will get you at least that far for your process.
I keep getting this error: "ConflictError : The specified DNS name is already taken." though i am pretty sure that i gave different cloud services name and VM name. How to avoid this error? Please give me some suggestion.
How to avoid the error? Use a different DNS name :)
Remember that all services in Azure share the same .cloudapp.net (or .websites.net) domain so it could be some other user who is using that DNS name. But ultimately the .cloudapp.net DNS name is largely irrelevant since you should be setting up your own custom domain and using CNAME to point to the Azure domain.
I have a server that I have assigned an external IP address to it and NAT'd through in my firewall. Then I have assigned with my domain host provider and made a DNS name to point to that external. All is great from the outside, and inside if I point to the local IP address of that server.
My problem is that the software that is on the server I cannot access certain Java features outside of the network because the local IP address is hardcoded into the software and Java wont read both internal and external IP address. So tech support on the software said we can put in a DNS name into the software.
So I went into the DNS of my domain controller and put in an Host (A) entry of subdomain.domain.com and the local IP address. Well it doesnt resolve right because DNS made the entry I put in as subdomain.domain.com.local so again Java doesn't read it right. How do I make DNS read this entry right as subdomain.domain.com?
Is this a windows DNS solution and domain controller? if so, the A record should just be "subdomain" (windows will add on domain.com since that is the domain for the domain controller). If this is the case, try that A record, and it should work.
UPDATE
Based on comments below, it sounds like you need to do this:
Create a new zone using your external domain name.
Open DNS console.
Click on Forward Lookup Zones.
Right-click, choose new Zone, type in the name of the external
domain name (srb1.com).
Once created, right-click the zone you just created, choose New Host
Record.
Type in 'software' (without the quotes), and provide the internal Private
IP address of your internal webserver.
These instructions were pulled from here: Scenario 2
Background/objective here is to get clients that VPN in to have access to the LAN they are VPN-ing into. Everything is on EC2.
To get this working, I'm trying to set up direct-access on the Win2k12 box where Remote Access is set-up. Once of the perquisite checks when you launch the "Enabled Direct Access Wizard" is verifying one of the network adapters is configured to have a static IP address (I do not, nor am I aware of a way to make that a reality on EC2!) I can choose to suppress that warning and continue...to a point...eventually I am prompted to "Type the public name of IPv4 used by clients..." prompt pictured below. No value I have tried (host name, fully qualified host name, IP) seems to
work failing with the below errors
host name : "The public name of IPv4 address is invalid. Modify the settings"
fully qualified host name : "An internal adapter with a valid IP address, IPv6 enabled, DNS settings, and a domain profile cannot be located"
IP: "The public name of IPv4 address is invalid. Modify the settings"
I'm thinking this could all be due to the failed pre-requisite, though I'm not 100% sure. Ultimately, I'm beginning to be become unsure if this is possible [by using direct access] or if it is possible to accomplish my goal by using a different approach. Thanks in advance.
I was setting this up on my 2012 server as well and came across the same error. I had to restart the server after verifying I had a static IP, with it's own IP ad the main DNS and the loopback address as the secondary. This was probably because I said that DNS could only respond on that certain IP.
Is there any difference between the following when a intranet URL in accessed in IE
Add an entry in drivers/etc/host file for a name and IP
vs
Use IP directly
e.g. it works with the following link if I have a host entry as (XYZ 10.0.10.200)
http://XYZ/SiteDirectory/ABC/Default.aspx
but when I tried to use IP instead of name
http://10.0.10.200/SiteDirectory/ABC/Default.aspx
It gives me 404 not found error
Yes, there's a difference.
The web server is using HTTP/1.1 and "shared virtual hosting". When the client connects it sends an additional Host: header which contains the hostname part of the URL that the user supplied.
The web server looks at the header to find out which virtual host's data to serve.
In this case, the web server is configured to recognise and serve content from the "XYZ" domain, but doesn't know about any domain called 10.0.10.200
Smells like the webserver is using virtual hosts, so that it serves different pages if the client went to "www.foo.com" or "www.bar.com", even though they have the same IP-address.
As far as I can see there should be no difference. With a host name the order is hosts file before DNS so it should be used.
Is there another line in the host file with the same hostname?
What happens when you do a tacert? (trace route)