dns confusion on forward zone

phoeneousphoeneous Go ping yourself...Member Posts: 2,333 ■■■■■■■□□□
in Off-Topic
Ive created a sharepoint portal at http://sharepointserver. I also created an A record for 'portal' to point to that site since the server name is not user friendly. My boss would like the portal address to be http://portal.gocompany instead of just http://portal, is this possible? I created the portal.gocompany record in dns but of course it created a new domain called gocompany and then an A record called portal. Is this something that needs to be done in iis?
· Share on FacebookShare on Twitter

Comments

  • jibbajabbajibbajabba Google Ninja Member Posts: 4,317 ■■■■■■■■□□
    Well there are two things to consider .. First is the host header of the website. I don't know anything about sharepoint, but if Sharepoint runs from IIS then yes, you need to change the hostheader to "answer" at http://portal.gocompany

    Second thing to consider is DNS. If the portal needs to be accessible via http://portal.gocompany, the gocompany acts as TLD (Top Level Domain) and portal would be an A-Record ...

    Two options

    1. Nasty one - adding the domain into the hostfile of each workstation ... well .. horrible idea - so forget that one.

    2. Adding the domain 'gocompany' into DNS (which is used by the workstations) and add an A-Record with the IP of the sharepoint server.

    For this, you need to create a new forward zone called 'gocompany' and underneath that an A-Record portal

    vht4jl.jpg
    My own knowledge base made public: http://open902.com :p
    · Share on FacebookShare on Twitter
  • phoeneousphoeneous Go ping yourself... Member Posts: 2,333 ■■■■■■■□□□
    Gomjaba wrote: »
    Well there are two things to consider .. First is the host header of the website. I don't know anything about sharepoint, but if Sharepoint runs from IIS then yes, you need to change the hostheader to "answer" at http://portal.gocompany

    Second thing to consider is DNS. If the portal needs to be accessible via http://portal.gocompany, the gocompany acts as TLD (Top Level Domain) and portal would be an A-Record ...

    Two options

    1. Nasty one - adding the domain into the hostfile of each workstation ... well .. horrible idea - so forget that one.

    2. Adding the domain 'gocompany' into DNS (which is used by the workstations) and add an A-Record with the IP of the sharepoint server.

    For this, you need to create a new forward zone called 'gocompany' and underneath that an A-Record portal


    Whats the difference between creating a forward zone called gocompany, and just creating a domain called gocompany within the existing forward zone?
    · Share on FacebookShare on Twitter
  • jibbajabbajibbajabba Google Ninja Member Posts: 4,317 ■■■■■■■■□□
    To be honest, I have never seen this option before. How weird.
    Cannot even find an exaplanation in my MCTS / MCITP books.

    I'll ask around ..

    Maybe someone else here can enlighten us ? This is the option he is refering to :

    798_Capture.png

    Unfortunately I don't have access to my test server at the moment and I don't really want to touch customer live server to test that ..

    Could check it tomorrow ...
    My own knowledge base made public: http://open902.com :p
    · Share on FacebookShare on Twitter
  • cnfuzzdcnfuzzd Senior Member Member Posts: 208
    I think that option creates a new child domain. so in the company.com zone, the new domain option (after entering child) would create a domain of child.company.com.

    I think.

    John
    __________________________________________

    Work In Progress: BSCI, Sharepoint
    · Share on FacebookShare on Twitter
  • jibbajabbajibbajabba Google Ninja Member Posts: 4,317 ■■■■■■■■□□
    So if you would out in a record called wibbled.com underneath domain.com, it would actually be like

    wibble.com.domain.com

    If that is the case he indeed needs to create a new forward lookup zone.

    Wait .. for subdomain I would actually just add an A-Record .. now I am confused ..

    Edit2: Ah wait a second, a CHILD DOMAIN , not SUB DOMAIN .... I Seeeeeee
    My own knowledge base made public: http://open902.com :p
    · Share on FacebookShare on Twitter
  • jibbajabbajibbajabba Google Ninja Member Posts: 4,317 ■■■■■■■■□□
    Right, checked some more. So creating a "Domain Record" creates a child domain in DNS and not a sub domain. For example. If you create a domain record called wibble.com inside of domain.com, it would create a child zone called com with an A-Record of wibble.

    This is clearly not what you need. So create a new forward zone called gocompany, create an A-Record 'portal' etc., like I said in my first post.

    The A-Record specifies obviously an IP which the IIS website is configured with. If you run multiple websites using the same IP don't forget to specify host header.
    My own knowledge base made public: http://open902.com :p
    · Share on FacebookShare on Twitter
  • phoeneousphoeneous Go ping yourself... Member Posts: 2,333 ■■■■■■■□□□
    Gomjaba wrote: »
    Right, checked some more. So creating a "Domain Record" creates a child domain in DNS and not a sub domain. For example. If you create a domain record called wibble.com inside of domain.com, it would create a child zone called com with an A-Record of wibble.

    This is clearly not what you need. So create a new forward zone called gocompany, create an A-Record 'portal' etc., like I said in my first post.

    The A-Record specifies obviously an IP which the IIS website is configured with. If you run multiple websites using the same IP don't forget to specify host header.

    Good to know. I'll try it after hours so I dont break anything. Thanks!
    · Share on FacebookShare on Twitter
  • jibbajabbajibbajabba Google Ninja Member Posts: 4,317 ■■■■■■■■□□
    ipconfig /flushdns will be your best friend :)
    My own knowledge base made public: http://open902.com :p
    · Share on FacebookShare on Twitter
Sign In or Register to comment.