IP Problems

[pmidwest]

I'm not sure if this is the right place for this question... but...

we are running terminal servers and we were using MSDE for the database in the server farm. we have added a new server with SQL to take over the roles of the MSDE server.

Now I'm not sure how the routing works because I'm the new guy here... but... apparently our ISP routes the website for the TS to an internal IP here. so I shut down the MSDE server and gave the SQL server the IP address from the MSDE server...

Everything works like a charm. Until...

This morning I turned on the MSDE server to work on it (it has a new IP address now) and the TS website started acting funny. so I shut down the server and then I got a "page can not be displayed" error.

after looking into it, the page is trying to load on the new MSDE IP address... so I changed the IP on the SQL server and everything started working again.

I hope this makes since to someone and they can tell me what's going on here... sorry if I've confused everyone

 

[pmidwest]

some more info that might help.

Keep in mind one of these servers is offline at the moment

Server 1: Offline
Server 2: Online

when I do a nslookup on Server 1 it shows that its connected and gives the IP of Server 2.

I get the same thing when I do an nslookup on Server 2

 

[pmidwest]

NSLOOKUP

> Server 1
Server: PDC.mydomain.com
Address: 10.0.0.5

Name: Server 1.mydomain.com
Address: 10.0.0.247

> Server 2
Server: PDC.mydomain.com
Address: 10.0.0.5

Name: Server 2.mydomain.com
Address: 10.0.0.247

 

[treyhunsucker]

I would say that the MSDE server is running a dynamic dns update program.

Basically what happens is when the server gets a new IP address, it sends a message so the DNS server to update the A record with the new ip.

you might try starting the server and looking for this type of application. I've heard of people using

http://www.no-ip.com

for this type of setup.

 

[pmidwest]

The problem was that in our DNS instead of pointing the website to an IP address it was pointing at the server name. so when the server came back online with a new IP the DNS resolved to the new IP. if that makes any since