6,221 reputation
14285
bio website dunxd.com
location London, United Kingdom
age 39
visits member for 4 years, 11 months
seen Dec 10 at 14:23

I work at a large international development charity in London, as International Operations Manager. I manage a team of Regional ICT Service Managers, based in developing world countries, who keep our users happy through fixing problems, setting up great connectivity and generally making sure users can do their day jobs.

I previously worked at the same place as International Network Systems Analyst. I looked after a bunch of ICT systems in offices in the developing world, as well as looking after systems in our HQ. I gained a lot of knowledge in that job, and the techy side competes with the people stuff in the new role, hence I still hang out here a lot.

I'm passionate about the use of ICT in developing countries, both in terms of dealing with the inherent problems for ICT in those places, and using ICT as a tool for development.


Dec
11
awarded  Notable Question
Nov
26
awarded  Benefactor
Nov
26
comment Domain computer cannot resolve internal hostnames, but nslookup can
You get the bounty. It may not have solved the problem (I can't know now as I had to take drastic action), but you did put something down as an answer, and provided links to useful material - I didn't know about node type before and now I do, so thanks.
Nov
24
awarded  Notable Question
Nov
22
comment Domain computer cannot resolve internal hostnames, but nslookup can
In the end time ran out for investigation, and I had to take the drastic action of rebuilding the effected laptops. Bith are now functioning fine getting their settings from DHCP, as they were before, and no change to networking configuration or DNS. Still scratching my head, but in the end I spent more time investigating than it took to re-image both laptops and restore the backed up user data. Sometimes the best way to serve your users is to just get the job done, even if it isn't in an intellectually satisfying way.
Nov
21
awarded  Notable Question
Nov
20
comment Domain computer cannot resolve internal hostnames, but nslookup can
Hosts file is unchanged from default with Windows install. There are two computers on the network I am aware of with this problem. One has been made to workaround the issue by adding common internal hosts to the hostfile, buit clearly that isn't sustainable for any length of time. The network settings for all clients are set to "Register this connection's addresses in DNS" - the same settings are in place for all other clients on the network.
Nov
19
comment Domain computer cannot resolve internal hostnames, but nslookup can
I already tried removing the computer from the domain - but since the computer cannot locate the domain in DNS it is unable to do so.
Nov
19
comment Domain computer cannot resolve internal hostnames, but nslookup can
I also tried setting the network interface to use a different DNS server (in a different subnet) but getting the same results. That really looks like it is something on the client causing the problem.
Nov
19
comment Domain computer cannot resolve internal hostnames, but nslookup can
No - listening on all IP addresses. And it does respond to nslookup from the client (and other computers in the same subnet are working ok). Pretty sure that local Windows is not processing DNS lookups to computers in the domain either using a FQDN or bare hostname.
Nov
19
comment nslookup cannot resolve hostname for machine on external domain from internal domain
Updated the answer as comment above.
Nov
19
revised nslookup cannot resolve hostname for machine on external domain from internal domain
edited body
Nov
19
revised Domain computer cannot resolve internal hostnames, but nslookup can
added 386 characters in body
Nov
19
comment Domain computer cannot resolve internal hostnames, but nslookup can
Packet captures done, and results added to the questions. Why would Windows decide to not do DNS resolution for internal hostnames, whether using FQDN or not.
Nov
19
revised Domain computer cannot resolve internal hostnames, but nslookup can
added 302 characters in body
Nov
19
comment Domain computer cannot resolve internal hostnames, but nslookup can
Yes - returns the DNS suffix set by DHCP. It is correct.
Nov
6
revised Domain computer cannot resolve internal hostnames, but nslookup can
formatting
Nov
6
asked Domain computer cannot resolve internal hostnames, but nslookup can
Nov
5
awarded  Popular Question
Sep
30
awarded  Explainer