Sharepoint 2013 DNS access from intranet
Hello, first of all thank you so much for reading this post. I have a Sharepoint 2013 setup with SQL and Win Server 2012.
I am able to access the web application I created intranet.mydomain.com on the local server only.
I created a Host (A) in DNS manager pointing to 127.0.0.1. In the forward lookup properties the FQDN are set to 192.168.0.131 (should I leave this address to 127.0.0.1 ??) and another name server at 127.0.0.1
If I ping intranet.mydomain.com on the local server machine I get a response with the IP 192.168.0.131.
However, I am not able to ping intranet.mydomain.com or access it through intranet from another PC, but I am able to ping the IP address of the server 192.168.0.131.
When I put 192.168.0.131 in a browser on another local PC I get the home page IIS 8 Windows Server.
How could I be able to access the server through the network using the DNS intranet.mydomain.com ?
Much appreciated,
Herb
- Edited by
Herb Ellis
3 hours 54 minutes ago
February 20th, 2014 3:21am
Hello,
You have to register a host name of intranet.mydomain.com with the unique and valid id and not with 127.0.0.1 (IP should be in the same subnet of your current domain configurations).
You also need to configure the Alternate Access Mappings in the Central Administration site.
BR.
- Edited by
AsimPervaz
3 hours 37 minutes ago
February 20th, 2014 3:44am
Thank you for your reply. I tried what you said.
I have 2 records there, one is my intranet.mydomain.com pointing to my web application the other one is point to central administration.
When I click on intranet.mydomain.com, I see that the zone is set to "Default" and whenever I try to change it to "Intranet" I get the following message: "Sorry, something went wrong. The public Default zone URL http://intranet.global-automation.in
cannot be deleted. Set another URL to be public default zone before performing this action.
Any ideas?
February 20th, 2014 3:56am
Hello BR,
"Hello,
You have to register a host name of intranet.mydomain.com with the unique and valid id and not with 127.0.0.1 (IP should be in the same subnet of your current domain configurations)."
Where do I configure that? The IP address of my local server is 192.168.0.131. Is that what you are talking about? Putting this IP address in the Zone Transfers of Mydomain.com properties of the DNS manager OR in the IIS Manager? If the later, where please?
If its in the Site Bindings its already been done. The IP address for intranet.mydomain.com have been added 192.168.0.131.
This is the IPv4 address I get when I prompt my local server with /ipconfig
Thank you
- Edited by
Herb Ellis
3 hours 1 minutes ago
February 20th, 2014 4:21am
Hello,
Do not change the default one, instead add one more entry for Internal URLS (intranet.mydomain.com).
Hope this helps.
Regards !
February 20th, 2014 4:22am
I tried adding another internal url and it doesn't work. My intranet.mydomain.com URL is set as Default Zone.
Regards.
February 20th, 2014 4:29am
Hello,
http://intranet.global-automation.in
If this is default URL then you cannot have additional URL with the same name.
Instead specify something different.(http://intra.global-automation.in) (External URL's)
BR.
- Edited by
AsimPervaz
2 hours 45 minutes ago
February 20th, 2014 4:39am
I already tried that. It doesn't work. Thanks
February 20th, 2014 4:46am
As a quick point; the name of the zone doesn't matter. SharePoint gives them nice friendly names like intranet, default etc. but they aren't used for anything nor does it matter if you use one for a different purpose than the names suggest.
Have a read of this blog, it will bring you up to speed:
http://guru-web.blogspot.co.uk/2008/01/sharepoint-site-by-any-other-name.html
February 20th, 2014 4:47am
I Forgot to mention that I can access SP Central Administration URL from another PC. I am prompt to enter credentials.
February 20th, 2014 4:48am
OK So that brings me back to my first question rephrased: Why can I not access my web collection from the internal URL intranet.mydomain.com. This URL ables me to access the web collection for the local server only while the other URL that leads to SP Central
Administration can be used on another PC.
Much appreciated.
February 20th, 2014 4:51am
Hello,
http://intranet.global-automation.in
If the above is the default URL then no need to make any changes either in DNS and AAM.
It will work from within your network.
BR.
February 20th, 2014 4:51am
I cannot ping this URL from another PC on the network. But the SP central administration can be access from another PC on the network.
Any ideas?
February 20th, 2014 4:55am
I've checked the DNS Manager /DNS Events log and I get the following warning:
"The DNS server encountered a packet addressed to itself on IP address 192.168.0.131. The packet is for the DNS name "mydomain.com". The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1.Forwarders list. (DNS servers should ot forward to themselves)
2.Msater lists of secondary zones.
3. Notify lists of primary zones
4. Delegations of subzones. Must not contain NS record for this DNS server unless a subzone is also on this server.
5. Root hints.
Example of self-delegations... etc. [...]"
February 20th, 2014 5:17am
Hello,
Ping the server name and browse the URL by http://servername:portnumber
This would definitely browse your URL.
BR.
February 20th, 2014 5:17am
Actually, the port for intranet.mydomain.com is 80 so I don't think it will have any impact, although I am not at work now to test it.
However, the SP central administration works on another PC in the network using the other url:port
February 20th, 2014 6:20am
Hi Herb,
Let me attempt to make this easy:
FQDN intranet.mydomain.com should be used to create an A Record in DNS Manager with IP Address
192.168.0.131
127.0.01 - Addresses starting with "127." are used when one program needs to talk to another program running on the same machine using the Internet Protocol. These addresses were assigned by the IETF,
the organization that develops Internet protocols, in the Standard document.
If necessary you can also add the FQDN intranet.mydomain.com with the LoopBack IP Address of 127.0.0.1 to your HOSTS File on the Server. (This is typically done if you are using a Load Balancer or have multiple WFEs
and you want to use just one of them from the Server.
C:\Windows\System32\drivers\etc\hosts
Note: if using 127.0.0.1 as the IP Address for the DNS A Record intranet.mydomain.com,
only the server where SharePoint is installed will be able to browse to the URL
HTTP://intranet.mydomain.com.
Reference
Hope this makes it a little easier...
February 20th, 2014 6:24am
127.0.0.1 isn't a real IP address, that's shorthand for your computer to talk to itself, also known as 'looping back'.
The DNS entry should be for the intranet.mydomain.com and the ip address should be 192.168.0.131. There should not be any reference to 127.0.0.1 in DNS.
Your first step must be to correct DNS so you are able to ping the name and get the server's IP address back when run on the client computer.
February 20th, 2014 6:26am