Liam Posted June 3, 2015 Posted June 3, 2015 Hi All, Not sure if this is the right forum. I am having issues with google chrome when accessing our internal vle server This problem only started when we re-addressed our network and made changes to dns etc. The strange thing is is that it only affects chrome, all over browsers resolve perfectly fine. I have done some light bedtime reading as we do, and found that if i reset google chrome dns cache and flush sockets via chrome://net-internals that it should resolve this but it didn't resolve it. Any ideas? Im really at a loss
pete Posted June 3, 2015 Posted June 3, 2015 How are DNS entries set for the VLE server? Is it: vle.schoolname.whatever both internally and externally? or... vle.internal.schoolname.whatever internally and vle.schoolname.whatever externally? Does nslookup/dig show anything odd? Is Chrome getting the appropriate IP?
Liam Posted June 3, 2015 Author Posted June 3, 2015 I'm using split dns for an external name. For certificate reasons. The computer resolves it. Google doesn't.
computer_expert Posted June 5, 2015 Posted June 5, 2015 Have you tried disabling the inbuilt chrome DNS client? It's under Admin Templates > Google > Google Chrome and the setting is called 'Use built-in DNS client' (assuming you have the Chrome ADMX templates installed)
Liam Posted June 5, 2015 Author Posted June 5, 2015 Yes I have tried that too. I'll give it another go though. Thanks.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now