Simon
asked on
DNS Entry for an Internal URL
We recently set up a new time management system on a dedicated virtual machine.
OS: Windows Server 2016 Standard
In order to access its main internal website I need to use http://servername-server or server's IP address.
How do I change this name to be http://timemanagement.mydomain.com?
What type of a DNS entry do I need to add (under my mydomain.com forward lookup zone?) to make it work?
Thanks, your help is much appreciated.
OS: Windows Server 2016 Standard
In order to access its main internal website I need to use http://servername-server or server's IP address.
How do I change this name to be http://timemanagement.mydomain.com?
What type of a DNS entry do I need to add (under my mydomain.com forward lookup zone?) to make it work?
Thanks, your help is much appreciated.
Do you have a DNS zone for mydomain.com? If so then just create a Pointer record under the forward lookup zone\mydomain.com.
In your dns console
Right Click on Mydomain.com --> Create New A Record
Enter the Name and IP address for the server and Make sure create pointer record is checked.
Right Click on Mydomain.com --> Create New A Record
Enter the Name and IP address for the server and Make sure create pointer record is checked.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, I do mydomain.com with a few pointers there now like www and ftp;
However, these all point to external IPs.
If I simply create another host record with "timemanagement" name and point to my internal IP then what happens to the pointer myservername-server that points to the same IP?
However, these all point to external IPs.
If I simply create another host record with "timemanagement" name and point to my internal IP then what happens to the pointer myservername-server that points to the same IP?
@cP6uH
Create the record with the local IP
such as
name = mysevername
IP = 192.168.254.1 as an example..
Create the record with the local IP
such as
name = mysevername
IP = 192.168.254.1 as an example..
Pointer (or specifically PTR) records don't play a part here. Those are fore reverse lookups which is not what you are doing. Don't mess with them. Creating a CNAME record won't have the checkbox to create a PTR record and so it won't mess with your existing legitimate server records. It just adds an alternate name.
@cliff
Explain what you are talking about, I have always used an A record to map a server Name to IP after you do that you can go to http://servername.domain.com from a browser and you can resolve the site "AS LONG" as the server is listening on port 80..
a cname would only be used if you were trying to redirect http://servername.mydomain to http://servername.mydomain.com
Explain what you are talking about, I have always used an A record to map a server Name to IP after you do that you can go to http://servername.domain.com from a browser and you can resolve the site "AS LONG" as the server is listening on port 80..
a cname would only be used if you were trying to redirect http://servername.mydomain to http://servername.mydomain.com
@cP6uH
Please use the method I presented above and add an A record to your mydomain.com DNS forward lookup zone. It will work for you.. Alternately you could use a
CNAME as suggested by @Cliff "IF" you wanted to just redirect http://servername-server to http://timemanagement.mydomain.com but it is up to you what you feel works best.
I usually use A records as I feel they are cleaner.
Please use the method I presented above and add an A record to your mydomain.com DNS forward lookup zone. It will work for you.. Alternately you could use a
CNAME as suggested by @Cliff "IF" you wanted to just redirect http://servername-server to http://timemanagement.mydomain.com but it is up to you what you feel works best.
I usually use A records as I feel they are cleaner.
ASKER
I created a CNAME under "Forward Lookup Zones" and mydomain.com
Name: timemanagement
Type: CNAME
Data: servername-server.mylocald omain.loca l.
It seems to be working. I chose this solution because I was concerned about my existing pointer servername-server to local IP.
Name: timemanagement
Type: CNAME
Data: servername-server.mylocald
It seems to be working. I chose this solution because I was concerned about my existing pointer servername-server to local IP.
Sounds good.
Two A records can however share the same Local IP just for future reference.
You usually find this implemented with Web servers
https://social.technet.microsoft.com/Forums/Lync/en-US/ddd164cc-faa0-43b2-aca8-6d810938a31b/multiple-a-record-for-single-ip-address-in-dns?forum=winserverDS.
You usually find this implemented with Web servers
https://social.technet.microsoft.com/Forums/Lync/en-US/ddd164cc-faa0-43b2-aca8-6d810938a31b/multiple-a-record-for-single-ip-address-in-dns?forum=winserverDS.
a cname would only be used if you were trying to redirect http://servername.mydomain to http://servername.mydomain.com
DNS *does not* redirect. CNAME records are alternate names, not redirects. Terminology matters.
Enter the Name and IP address for the server and Make sure create pointer record is checked.
You actively gave advice to create a pointer record. Again, terminology matters. Additional PTR records are not needed for the OPS goal.
@cliff
Explain what you are talking about
Since you called me out, yes, I am quoting your previous comments to illustrate why I decided to respond and am explaining what I am talking about.
"I usually use A records as I feel they are cleaner. "
I disagree. The original intent of DNS was that an A record should match the actual hostname (a real property on Unix machines, and analogous to the machine name on windows.) CNAME records should be used for additional names that services may use on the same server. That is the intent of CNAME records...otherwise why even have them? Why not use A records all the time. The RFC spec matters, and if the DNS manager wins the lottery, retires, or moves on, proper CNAME records makes it *much* easier for a new DNS manager to step in and know what is going on from the zone file alone. That's my definition of "cleaner."
CNAME as suggested by @Cliff "IF" you wanted to just redirect http://servername-server to http://timemanagement.mydomain.com
That's *PRECISELY* what the OP first asked for.
In order to access its main internal website I need to use http://servername-server or server's IP address.
How do I change this name to be http://timemanagement.mydomain.com?
What type of a DNS entry do I need to add (under my mydomain.com forward lookup zone?) to make it work?
There was no "if" necessary. Solution matched the OPs ask, full on. Thus I stand by and defend my suggestion. I'll allow my profile to speak for the quality of my work.
@Cliff
Thanks for your detailed explanation I at least understand where you are coming from and your point of view :P
Thanks for your detailed explanation I at least understand where you are coming from and your point of view :P