The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
I think I have DNS issues on my network
JamesKeenan
Registered User regular
Registered User regular
Regularly on all workstations for any website, the initial attempt to connect to a website the fails citing a DNS error, but 1 or rarely 2 refreshes and it connects just fine, and quickly.
I feel this also affects the fact that the ttfb for the webserver running on a virtual machine is something like 7 seconds.
I have no idea where to start debugging this issue. And I'm the IT guy, embarrassingly enough.
I feel this also affects the fact that the ttfb for the webserver running on a virtual machine is something like 7 seconds.
I have no idea where to start debugging this issue. And I'm the IT guy, embarrassingly enough.
0
Posts
If you see those then you can start trying to figure out where the failure is. Do you have any ethernet cable testers?
Thank you for the reply, really. I know it's probably something simple that's just unknown to me.
I ran
ping -t 192.168.etc.etc for the network DNS server. mostly 1-2ms pings, occasionally 80ms. But no timeouts.
I have a cable tester, I'll try that. It's just that the workstations reaching outside is intermittent and not constant, but the website never loads fast. I don't know the impact of having a webserver as a VM though.
If you bypass the router and go directly into your modem with a pc, do you get the errors?
Most DNS errors I see are from either having it defined incorrectly in network settings, or from a router not using dns servers properly.
The webserver is dhcp, the DNS server and the router are both using 8.8.4.4 and 8.8.8.8.
I appreciate the help. I'm definitely going to figure this out eventually.
Generally they'll give you a pair, and at my place we general set the third DNS to 8.8.8.8 or 8.8.4.4 in case our internal DNS fails.
If your router is giving out DHCP, it might have a separate DNS setting for lease range.
Edit: I don't know anything about networking btw.
Please describe this network a little bit.
Is there an Active Directory server on your network?
When you said
Is "192.168.etc.etc." the local IP address for your Active Directory server?
If not, then what sort of device is serving up DNS?
Also, perform an nslookup. Open up a command prompt and type 'nslookup'.
You should receive a response similar to this:
Type the address of any major public website, for instance
You should immediately receive a response similar to:
Default Server: servername.networkname.domain Address: 192.168.x.x Non-authoritative answer: Name: www.google.com Addresses: 2607:f8b0:400e:c02::63 173.194.79.104 173.194.79.106 173.194.79.147 173.194.79.105 173.194.79.103 173.194.79.99If you receive anything else, or if this result does not appear immediately, let us know what you get.
the "no true scotch man" fallacy.