goodie069
asked on
CNAME resource reocrds for Site is incorrect
After running SBS BPA I received two identical alerts, as follows:
CNAME resource records for Site is incorrect
The CNAME resource record for the Sites alias should point to the fully qualified domain name of the computer that is running Windows SBS 2008.
In the DNS Manager, looking under SERVER -> Forward Lookup Zones -> SERVER.local i see a "Sites" entry that is currently pointing to SERVER.DOMAIN.local
I would like to know what this Sites entry is and what it's used for. It may have been changed for a reason (for internal sharepoint access, etc), so I'm hesitant to change it before I fully understand what it is.
Unfortunately I can't find much in the way of information doing a google search on the topic. Thanks in advance for any information or insight you can provide!
CNAME resource records for Site is incorrect
The CNAME resource record for the Sites alias should point to the fully qualified domain name of the computer that is running Windows SBS 2008.
In the DNS Manager, looking under SERVER -> Forward Lookup Zones -> SERVER.local i see a "Sites" entry that is currently pointing to SERVER.DOMAIN.local
I would like to know what this Sites entry is and what it's used for. It may have been changed for a reason (for internal sharepoint access, etc), so I'm hesitant to change it before I fully understand what it is.
Unfortunately I can't find much in the way of information doing a google search on the topic. Thanks in advance for any information or insight you can provide!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@HyperCat:
Yes, all of my IIS sites (RWW, OWA, Web, etc) are all functional from both inside & outside the network. This is the reason I am so hesitant to just change it - if it's not broke, don't fix it.
@MPECSInc:
I'm a bit confused. Yes, that is the external URL we use to access SharePoint sites from outside of our network. That works with the current configuration (CNAME is server.domain.local). Should this be changed to remote.domain.com?
I do have a Forward Lookup Zone for remote.domain.com that contains the SOA (server.domain.local), NS (server.domain.local), and Host (A) 1.2.3.4 (internal server IP).
There is no similar record in the domain.local Forward Lookup Zone, however. All of the various CNAME references there point to server.domain.local (among the various A records for internal machines).
So I'm inclined to go with the bogus error and ain't broke don't fix approach. Just wanted to clarify in case there's something I'm not understanding.
Thanks!
Yes, all of my IIS sites (RWW, OWA, Web, etc) are all functional from both inside & outside the network. This is the reason I am so hesitant to just change it - if it's not broke, don't fix it.
@MPECSInc:
I'm a bit confused. Yes, that is the external URL we use to access SharePoint sites from outside of our network. That works with the current configuration (CNAME is server.domain.local). Should this be changed to remote.domain.com?
I do have a Forward Lookup Zone for remote.domain.com that contains the SOA (server.domain.local), NS (server.domain.local), and Host (A) 1.2.3.4 (internal server IP).
There is no similar record in the domain.local Forward Lookup Zone, however. All of the various CNAME references there point to server.domain.local (among the various A records for internal machines).
So I'm inclined to go with the bogus error and ain't broke don't fix approach. Just wanted to clarify in case there's something I'm not understanding.
Thanks!
Run the Fix My Network wizard from the network tab and see if it fixes it.
Philip
Philip
What is the purpose of the forward looking zone for remote.domain.com?
LOL - I mean "forward LOOKUP zone"! I'm sure you're forward looking enough without a zone to prove it...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I've seen that error too.
It's probably bogus. You'll get this error if there's a CNAME record in the DNS server cache that has "site" as the host name (before the first dot). In SBS BPA scan results, click on the tree view and drill down to the CNAME error. You will probably see that it's a record for a remote domain (like site.google.com or something)
Clear the cache on the DNS server and rerun SBSBPA2008 and see if the error's still there.
It's probably bogus. You'll get this error if there's a CNAME record in the DNS server cache that has "site" as the host name (before the first dot). In SBS BPA scan results, click on the tree view and drill down to the CNAME error. You will probably see that it's a record for a remote domain (like site.google.com or something)
Clear the cache on the DNS server and rerun SBSBPA2008 and see if the error's still there.
ASKER
Never really resolved this, but since everything is working as-is, I've ignored the message in the BPA.
I had that error as well. Clearing the DNS cache did the trick. Thanks for the help.
I found a solution for this !. Clear the DNS cache !. Then re-run BPA
I think this error message is a BUG with SBS 2008 BPA !!!!!
I think this error message is a BUG with SBS 2008 BPA !!!!!
+ https://remote.yoursbsdomain.com:987/sites/MyNewCollection
The sites CName is a part of the split DNS setup. If you look, you will also see that you have a Forward Lookup Zone for your remote.yoursbsdomain.com zone too.
Philip