DNS Changes daily from old to new

[pirchcom]

I have recently got en a serverbeach server. I moved from another dedicated server to this one. I have chaneged nameservers on a number of domains to point to serverbeach nameserver. When I ping the domains some are resolving to the new server ip and some dont and also they change constantly thruout the day. The same domain name can go from the new ip to the old and bach again every 6 or 7 hours. In the morning it will be resolving to the new server and in the evening it will resolve back to the old server ??? I am pinging from the same computer with the same provider.

Any ideas ? and this can also happen from another Provider.


Thanks in advance

Mark

[QT]

There may be multiple nameservers at your provider and one of them may have it cached and the other doesn't. What are the IP addresses of the nameservers you are using, and what domain are you dealing with?

[pirchcom]

the domain I changed aprox 1 week ago is pirch.net

ather domains in question changed within 4 days are

hornbyequipment.com
canadiandateline.com
okanagandateline.com
christinaandfriends.com


the new ip is 69.44.59.145

the old ip is 66.179.60.76


recent domains changed 48 hours ago are

okanaganbands.com
pirch.com
pirchin.com
blueshiftcomputer.com


if I chek at dnsstuff.com they all resolve to the new ip

I phoned my Internet provider and they couldnt figure out why it keeps changing from one to another


Thanks

Mark

[QT]

They are all resolving OK from here too. Check the network configuration on your own machine and see what the IP addresses of your DNS servers are. If you're on Windows the command would be "ipconfig /all"

[pirchcom]

I did the ipconfig /all then pinged the domains and still the old server ip shows up.

I have pinged from diff computers and diff ISP's and the results change but nothing stable as in resolving to the new IP all the time every day.

I phoned my ISP and they dont know whats up. I must have the dns change and the server set correctly or it would fail all the time and not just irratically.

Thanks again

[QT]

I guess I should've made myself more clear, heh. What are the DNS servers listed in ipconfig?

[pirchcom]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : PIRCHMAIN
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Adapter

Physical Address. . . . . . . . . : 00-10-DC-44-87-5C

PPP adapter CNX:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 64.114.48.214
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 216.86.96.2
216.210.96.2
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Owner>

[knightfoo]

There are a couple of weird things going on here. First, it looks like the previous DNS servers had a huge TTL set (400,000+ seconds) for the NS records, so it is taking a long time for them to expire:

;; AUTHORITY SECTION:
pirch.com. 434577 IN NS ns2.valuetech.net.
pirch.com. 434577 IN NS ns1.valuetech.net.
;; AUTHORITY SECTION:
okanaganbands.com. 446194 IN NS ns1.valuetech.net.
okanaganbands.com. 446194 IN NS ns2.valuetech.net.

When the 434,577 and 446,194 counts down to 0, the nameservers will dump their cache and get new information. Both 216.86.96.2 and 216.210.96.2 have the wrong information cached for the above domains.

The rest of your domains that are not resolving properly have the right nameservers, but it looks like you've modified the records in the last 24 hours and they have not propagated yet. You have about 10 hours left before the nameservers your computer is using will drop the old records and get the updated information. A cold restart of DNS services on 216.86.96.2 and 216.210.96.2 will probably fix it too. :D Both of those servers are acting kinda strange.

-knightfoo