Tree_Farmer
Level 1 (4 points)
Mac OS X

Q: One website does not come up-DNS problem?

There is one website that does not come up, on all our work computers, when they are connected to our internal network.

We also have a work wi-fi network, this website DOES come up on computers when they are connected wirelessly.

 

What would be troubleshooting steps to figure out what’s going on with ONE website?

I suspect an error/corruption in my local DNS.

 

I have changed the DNS on a local computer, to Google’s DNS and it doesn’t make a difference.

Our in-house DNS is running on a Windows 2008 server.

 

I tried a Traceroute in Nework Utility, but it doesn’t show anything (or maybe I don’t know how to read it)

There is one line that has 3 asterisks, but it’s in the middle, line item 6 out of 12.

 

Does anyone have any other ideas on what could be wrong, why one website will not come up, or ideas on troubleshooting?

 

I have a MacBook Pro, OS 10.9.4, but I don't think it's a problem with my Mac, since I get the same symptom on Windows computers.

 

Thank you,

Doug

MacBook Pro, OS X Mavericks (10.9.1)

Posted on Jun 6, 2016 3:05 PM

Close
Tree_Farmer

Q: One website does not come up-DNS problem?

  • All replies
  • Helpful answers

  • by leroydouglas,

    leroydouglas leroydouglas Jun 6, 2016 4:32 PM in response to Tree_Farmer
    Level 7 (22,920 points)
    Notebooks
    Jun 6, 2016 4:32 PM in response to Tree_Farmer

    If you are willing to share it might be beneficial the  website address?

     

    Surely you have tried the full address http://www.yourwebsite.com vs http://yourwebsite.com

  • by MrHoffman,

    MrHoffman MrHoffman Jun 6, 2016 6:58 PM in response to Tree_Farmer
    Level 6 (15,627 points)
    Mac OS X
    Jun 6, 2016 6:58 PM in response to Tree_Farmer

    How are your Wi-Fi devices configured?  As a router, or as an access point (AP)?   Same subnet as the wired network, or a different subnet?

     

    If you use the dig command to translate the name to an IP address, you'll also get the identity of the DNS server that returned the response.  You can access the dig command from the command line, or from within the Network Utility.app tool on OS X.   For example, the command line command is:

     

    dig www.example.com

     

    You'll get the IP address of the NS (name server) that provided the translation in the wad of text output that command produces.

     

    DNS corruptions can arise in the DNS server or in the local resolver cache, and DNS translations can also be explicitly blocked by various network hardware and add-on software that can be present in many networks; by firewalls, nanny filters and other such accoutrements.   These packages can be implemented at various locations in the internal network, as well.

     

    But if this misbehaviour is arising on both OS X and Windows clients, and if this is involving Windows Server and its DNS server, then I'd suggest taking the question over to the Windows or Windows Server forums over at Microsoft, and restricting your question there to just Windows clients and Windows Server software (to avoid getting "reflected" back over here), as the folks in the Microsoft forums are likely much more familiar with configuring and troubleshooting DNS services running on Windows Server configurations.   It's unlikely that the problem is a corruption in the local client software here, given that you're reporting misbehaviour on both OS X and Windows clients and that sort of thing doesn't usually arise across multiple boxes across multiple disparate operating systems.