cachepilot/DNS entry on w2k3 server

[SimpleSi]

Got a problem with a teachers machine that was set in IE to use cachepilot as proxy.

 

Wasn't working.

 

Couldn't access the cachepilot content either using http://cachepilot...

 

Set proxy to lancsngfl.ac.uk (main RBC one) and changed espresso shortcut to http://10.86.8.8/... and all works (but bit of a bodge )

 

If I pinged cachepilot I'm getting a response from some microsoft site

65.74.135.110

 

Gone to another machine - its fine -IE fine - cachepilot fine - ping cachepilot gives 10.86.8.250 (correct address)

 

Now, what I'd like to know is WTFH is going on !

I can see that maybe I should have previously manually entered the cachepilot in my DNS server - but maybe not???

 

How come it's worked fine for now (server been in for months)

 

How come this machine I'm typing on isn't affected!!

 

Or have I just been lucky up til now??

 

regards

Simon

[ricki]

Hi Simon

 

I have an a record for the cachepilot in dns.

 

Are you running just dns or wins as well?

 

Have you tried flushing the dns on the server and the client and then try pinging again.

 

If you are using wins you might have a strange record in there as well.

 

Lastly compare the settings in network setting / ip / advanced.

 

Lastly does this teacher use this machine somewhere else. I have had in the past where a teacher has fixed the ip and got a setting wrong like the dns server.

 

Also if you enter the ip address of the cachepilot rather than the name it speeds up response.

 

Just an idea

 

Richard

[Newton]

I had a similar problem a while ago, turned out that the setting for primary and secondary DNS servers was wrong on the PC

[SimpleSi]

Thanks for all the pointers. I'll check them all out next time on that site.

 

The bit that gets me is that I can easily see how using the name cachepilot wouldn't work if I didn't have a manual entry in the DNS (which I don't).

 

What I can't understand is how its worked ever since I put the server in (anout 2-3 months) and how it works in all my other schools (where I haven't done it either)

 

Any why it just changed on this one computer (so far anyway!)

 

Its a fixed machine BTW

 

It'll be a nice learning exercise anyway - I love DNS (as ChrisH, Stewart etc know )

 

regards

 

Simon

[SimpleSi]

HOT NEWS- FAULT SPREADING TO OTHER SCHOOLS

 

Just has same issue at this school - can't access espresso - it trys to contact "65.74.125.110"

 

I think I'm in trouble

 

regards

 

Simon

[SimpleSi]

@richard (or anyone who knows

What FQDN name do I use when I create a record in the DNS.?

 

is is cachepilot.mysitenameetc

or

cachepilot.somethingelse

 

 

regards

 

Simon

[SimpleSi]

OK i've slowed down a bit.

At one school I did this.

 

added cachepilot as an A record.

 

Duff machines still not resolving cachepilot to local ip address.

 

Used repair net connection on client - no diff.

 

Pressed all sorts of update options in DNS !

 

On client - disabled net connect - re-enabled - now working fine.

 

ping cachepilot resolves to local 10.86.8.250 ip.

 

in IE "http://cachepilot/..." gives my local espresso page.

 

At this point in time, I don't know if it was the DNS change or the dis/re-enable network connection or both that "cured" it.

 

I'll see what happens at other school tmrrw

regards

Simon

[SimpleSi]

Bit more info (are their any DNS experts here )

 

back at Broadoak at 7am! (2nd school to have problem) and doing a few tests before I start.

 

On a client thats fine if I ping cachepilot, i get response from 10.81.62.250 - fine.

 

Ping cachepilot.mshome.net and it resolves to 65.74.125.110 (but no reply)

 

Now on a problematic client pinging cachepilot resolves to 65.74.125.110.

 

repair net connection - no diff

switch computer on and off - no diff

Disable net connection - re-enable - now fine! - ping cachepilot resolves to 10.81.62.250.

 

This is before trying to enter the cachepilot into my DNS server settings.

 

And I think I need to do more that just create an A record in the DNS but I really really coulld do with some help please.

 

regards

 

Simon

PS Not running WINS and the machines are not AD - just use the w2k3 servesr as DNS/DHCP/File/Printer server.

[Geoff]

Is there anything set in the hosts file for the cachepilot on the affected machine? Are the dns server IPs the same on both machines?

[SimpleSi]

The cavalry arrives

I've moved on to another school -Kingsfold (don't know if they've got same problem yet - I'm trying machines out)

 

 

However - I did check out hosts file on an affected machine at Euxton CE (1st school) and their was no entry apart from 127.0.0.1 localhost.

 

ipconfig /all gives shows DHCP and DNS pointing to server.

 

as a matter of interest what do you get if you ping cachepilot.mshome.net?

 

I think somethings changed either on CLEO network or outside of it and because I've have't properly entered the cachepilot into my DNS (or something else that I haven't done on my W2k3 sites ) - I'm being bitten in the backside now

 

Should the cachepilot just have a simple manual entry A record entry in the DNS xxx.local forward lookup zone or is something more complicated needed?

 

(BTW on 1st 2 schools, I didn't create any rev zones as I didn't think they are actually needed for normal operations - could that affect this issue?)

 

And how do I get the settings to roll out to all clients without having to go around and disable/re-enable all machines?

regards

Simon (feeling extremely simple today )

 

PS [edit]I't seems I'd already entered cachepilot in DNS at this school - Kingsfold, so it'll be interesting to see if I can find any affected machines -I'm not as useless as I'd thought [/edit]