DNS errors/refresh

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm student on a university network, and we have a rogue DHCP server
(probably a router some student hooked up wrong). Every so often the DNS
settings on our computers change to a 192.169.1.1 address. Either runnnig
the Connection repair feature, or unplugging and plugging in the cable again
restores the right settings, but it's annoying. Does anybody know of a way
to get Windows to automatically repair the connection when it changes? If
not, does anybody know how to write a script that will purge the Domain Name
System (DNS) cache, and reregister the DNS? The commands are ipconfig
/flushdns & ipconfig /registerdns I believe. Thanks
 
DANRFXz said:
I'm student on a university network, and we have a rogue DHCP server
(probably a router some student hooked up wrong). Every so often the
DNS
settings on our computers change to a 192.169.1.1 address. Either
runnnig the Connection repair feature, or unplugging and plugging in
the cable again
restores the right settings, but it's annoying. Does anybody know of
a way
to get Windows to automatically repair the connection when it changes?
If not, does anybody know how to write a script that will purge the
Domain Name
System (DNS) cache, and reregister the DNS? The commands are ipconfig
/flushdns & ipconfig /registerdns I believe. Thanks
Click to expand...

I can't help you with writing the script, but why aren't you contacting
your university's IT Dept.? It's their job to make sure the "rogue DHCP
server" is found and removed.

Malke
 
If
not, does anybody know how to write a script that will purge the Domain Name
System (DNS) cache, and reregister the DNS? The commands are ipconfig
/flushdns & ipconfig /registerdns I believe. Thanks
Click to expand...

If those commands will do it for you, just create an empty text file
with them both in it. Save the file, call it resetdns.BAT or something
else you like. Create a shortcut to the desktop and just dbl-click to
run it.
 
We have told the IT department multiple times that there is an issue, but
they have yet to resolve it. The problem began happening in November. They
don't seem to want to take the time to find where in the building the problem
is.
 
Back
Top