Alternate DNS Settings 1

[Fatboy0341]

I have a user who works ostly out of our reglar office. He does however travel once in a while to one of our vendor's offices and needs internet access while he is there. He can plug into their network fine - but he needs to change his DNS settings from "automatically detect" to static server addresses.

Is there a way to have an "alternate" DNS profile, or an icon I can set up for this user that will roll him over to those settings when he needs them - plus a way to roll back?

I know it sounds stupid...but he had it setup something like that on his old laptop - but it was stolen and I have no idea who had what setup on there. He's got a new one now and I'm just going by what he is telling me.

Thanks for any input or advice available...much appreciated.

JB



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[trojanman]

Control Panel > Network connections > Local area connection > Properties > Internet Protocol (TCP/IP) > Alternate Configuration. Or you can click on the Advanced tab and add a list of DNS servers to use.

 

[Fatboy0341]

Thanks trojanman (I never thought I'd hear myself saying that).

Last question - adding DNS servers to that list under "Advanced" - will the system use those DNS servers if it doesn't receive any automatically...almost like having them in reserve?

Thanks for the reply...much appreciated.

JB



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[bcastner]

You really will have little luck using other DNS servers, particularly if they happen to be your clients DC in a Domain!

Use netsh.exe, a native XP command.

To set Static DNS addressing, write a CMD file. Example of away_from_office.cmd :

@echo off
netsh interface ip set dns "Local Area Connection" static 192.168.0.200 <<==== change to the appropriate IP
; not necessary but I add it
ipconfig /reset

--------------------------------------

To revert to DHCP DNS addressing:

@echo off
netsh interface ip set dns "Local Area Connection" dhcp
ipconfig /reset


----------------------------------------

 

[trojanman]

Theoretically, you could use any DNS server available on the internet. When testing remote setups, I use 4.2.2.1 which is located somewhere in Colorado, while I live in Nevada.

If a DHCP assigns you a DNS address automatically, it will not use the ones in the list.

 

[Fatboy0341]

Thanks for the assistance everyone.

My frustration is trying to guess or make assumptions about the vendor's network. Not much I can do there...especially when they don't even have a SysAdmin - they contract everything out.

Thanks again for the advice.

JB \m/



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[bcastner]

Theoretically, you could use any DNS server available on the internet. When testing remote setups, I use 4.2.2.1 which is located somewhere in Colorado, while I live in Nevada.

Practicly, most will deny access if the request comes from outside their managed blocks of IPs.

Always it will be blocked if the DNS server is the DC on a Windows or Linux Domain.

If a DHCP assigns you a DNS address automatically, it will not use the ones in the list.

No.
XP will "fail-over" all listed DNS servers until it finds one that is working.

 

[trojanman]

XP will "fail-over" all listed DNS servers until it finds one that is working.

Thats what I said, just in different words. Obviously the DNS provided by DHCP will work so it wont query the list.

 

[bcastner]

DNS severs can go south and become unavailable.
Consider a Domain setting rather than a referent DNS server from a large ISP.

 

[Fatboy0341]

I think I am just going to contact the vendor and have them make a tech support person available when my user arrives...as opposed to trying to predict the future and talk to someone who doesn't really care in the first place or have the knowledge to tell me what I need to know.

No worries and thanks to everyone who replied.

JB



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."