In your jenkins build, can you try just running a command "nslookup" (or ping would probably work too) on your agent machine to see what response you get from actually within the build session? That might indicate whether you're even getting a valid lookup back from DNS from within your job environment.
Might need to set up a new temp job which doesn't do any Git calls, etc. to actually get to your build steps. Scott On Fri, Dec 14, 2012 at 7:09 AM, mwpowellhtx <mwpowell...@gmail.com> wrote: > The mystery still has me puzzled: Git Bash worked cloning, fetching, > pulling. Yet Jenkins persistently failed even after repeated attempts > restarting Jenkins Windows Service. It sounds plausible that Windows DNS > Cache Service needed restarting, but then why did Git Bash work and Jenkins > service did not? Are there any other services upon which Jenkins depends > that might cause something like this? For now I've got an entry in my hosts > file, but I still don't think I should have to do this, provided of course > DNS is working right. > >
