Discussion URL does not work if not FQDN

  • Tuesday, May 08, 2012 5:09 AM
     
     

    Hi all

    Apologies if this is not the correct forum. I will be more than willing to move my post if this is the wrong forum for the question. I have a strange issue with one Win XP SP3 client. The client go to a specific URL for a in house application eg <servername>/directory/index.php?dir=/name. If the user go to the URL as i typed it out she gets a DNS_Server_failure error. Your request could not be processed because an error occured contacting the DNS Server.

    If i edit the URL in the browser to say server.domain.lan instead of just servername than it works. I have tried with my domain admin account and it is giving the same issue. On my pc it works correct though. The URL with only the servername does work and on lots of othere pcs in the org. I have compared DNS setiings to those of my pc and it is the same. I can ping both the servername and the FQDN from the affected machine with no issues

    What could be the issue here?

All Replies

  • Tuesday, May 08, 2012 6:03 AM
     
     

    Hi,

    See if following discussion helps in your case

    SharePoint 2010 site not working unless I use FQDN

    http://social.technet.microsoft.com/Forums/en-ZA/sharepoint2010setup/thread/c7759cc2-53e9-43ad-86d3-7e3ae1794628

    If it doesn't then, you might wan't to check this is in IIS forum. 


    Thanks !

  • Wednesday, May 09, 2012 7:28 AM
    Moderator
     
     

    Hi CraMey,

    Thanks for posting here.

    Please check the DNS suffix list on this problematic Windows XP service pack 3 computer and insert the domain suffix entry “domain.lan” if it is not listed yet :

    Configuring Query Settings

    http://technet.microsoft.com/en-us/library/cc959339.aspx

    Thanks.

    Tiger Li


    Tiger Li

    TechNet Community Support

  • Wednesday, May 09, 2012 7:51 AM
     
     

    Hi

    Thanks for your post. That was the first or one of the first things which i have checked and it is there allready which makes the issue more bizarre

  • Wednesday, May 09, 2012 8:06 AM
    Moderator
     
     

    Hi CraMey,

    Thanks for posting here.

    Only one particular host was affected by this issue or all ?

    So after cleaning the DNS local cache and rebooting this host , we still got same result ?

    Which troubleshooting methods have we also tried ?

    Thanks.

    Tiger Li


    Tiger Li

    TechNet Community Support