DNS Question

[EscortBiz]

anyone know how o flush DNS or something like that

[FrankWhite]

sure if you are using xp

do the following,


Control Panel, Administrative Tools, Services

find "DNS Client"


and stop this service, you can also stop it and start it, but better way is just to stop it and disable it from start on the start up, so this way you always using your isps, fresh entries.

[Brujah]

ipconfig /flushdns
?

[FrankWhite]

Originally posted by Brujah
ipconfig /flushdns
?

yeah you could do it like this as well.

[Cohen]

-press the "start" button in the left buttom corner
-choose "run"
-type CMD and pres enter
-A Dos window show up
-type: ipconfig /flushdns and press enter

[pr0]

Goto DOS & type in

ipconfig partygoat

and enter

it will bring up a list of everything you can do with ipconfig

[pr0]

"ipconfig /displaydns"

bet ya $50 those history washers don't flush your dns

[Cohen]

if its your old problem from earlyer today about acces to only 2 sites try this.

Open a dos-window again and type: ping tucows.com and press enter.
it should look like this
answer from 216.40.32.30: byte=32 time=150ms TTL=240
answer from 216.40.32.30: byte=32 time=143ms TTL=240
answer from 216.40.32.30: byte=32 time=139ms TTL=240
answer from 216.40.32.30: byte=32 time=141ms TTL=240

If it says : "request timeout" try typing this: ping 216.40.32.30

If that works, its your dns, but if there isent any reply, its not your DNS

[doobster]

go to dos and type format c: (someone had to say it)

[EscortBiz]

tried starting and stopping the DNS Client trist the ipconfig /flushdns it said it did it successfully but still having the issue

any other way to flush this

[EscortBiz]

guess im fucked

[strainer]

Originally posted by EscortBiz
guess im fucked

You need to supply more info. DNS has a TTL (time to live in cache) setting. I'm taking a wild guess here you just changed hosts or something? If so, old DNS entries will live in cache in routers and servers all over the world until the TTL expires (typically from 4 hours to 5 days).

Give us a little more info.

[EscortBiz]

Originally posted by strainer


You need to supply more info. DNS has a TTL (time to live in cache) setting. I'm taking a wild guess here you just changed hosts or something? If so, old DNS entries will live in cache in routers and servers all over the world until the TTL expires (typically from 4 hours to 5 days).

Give us a little more info.

Ok here is the info

My host just changed their email IP address, so all the emails I accessed from Eudora somehow are stored in my systems cache and whatever I do it tries to resolve the old IP.

How can I get rid of this old IP in my systems brain, I tried the things above myself but its still trying to resolve the old stuff when I ping.

Try pinging mail.hotlocalescorts.com I get 63.211.38.185 but you will get 66.128.207.58 or somethin

Any help?

[Cohen]

Originally posted by EscortBiz
guess im fucked

if you run winxp or Win2000 ther is a file called HOSTS under
C:\WINDOWS\system32\drivers\etc

edit that one with notepad so it only says :

127.0.0.1 localhost

[EscortBiz]

Originally posted by Cohen


if you run winxp or Win2000 ther is a file called HOSTS under
C:\WINDOWS\system32\drivers\etc

edit that one with notepad so it only says :

127.0.0.1 localhost

Still wont show the correct IP

Im using DSL can it be in the DSL modem

[Cohen]

Originally posted by EscortBiz


Still wont show the correct IP

Im using DSL can it be in the DSL modem

try to turn the dsl-modem of, and let it stay off for 30 seconds, then trun it on again

[EscortBiz]

Originally posted by Cohen


try to turn the dsl-modem of, and let it stay off for 30 seconds, then trun it on again

still same problem, thanks

[strainer]

Originally posted by EscortBiz


Ok here is the info

My host just changed their email IP address, so all the emails I accessed from Eudora somehow are stored in my systems cache and whatever I do it tries to resolve the old IP.

How can I get rid of this old IP in my systems brain, I tried the things above myself but its still trying to resolve the old stuff when I ping.

Try pinging mail.hotlocalescorts.com I get 63.211.38.185 but you will get 66.128.207.58 or somethin

Any help?

Ok here is the deal. From a "dig -t mx hotlocalescorts.com": (Under Unix)

;; ANSWER SECTION:
hotlocalescorts.com. 86400 IN MX 10 mail.hotlocalescorts.com.

;; AUTHORITY SECTION:
hotlocalescorts.com. 86400 IN NS dns2.inyc.com.
hotlocalescorts.com. 86400 IN NS dns1.inyc.com.

;; ADDITIONAL SECTION:
mail.hotlocalescorts.com. 86400 IN A 66.128.207.69

--- So, your mail server has been changed, but it has a TTL of 86,400 seconds. (24 hours).

The reason you get the wrong ping is because your isp's DNS has the old address cached (and will keep it for 24 hours). Turning off your computer or modem won't help, your isp has the number cached.

In the meantime, to check your mail, put in the hardwired address of 66.128.207.69 in Eudora and you can pop in until the 24 hours pass...

[EscortBiz]

Originally posted by strainer


Ok here is the deal. From a "dig -t mx hotlocalescorts.com": (Under Unix)

;; ANSWER SECTION:
hotlocalescorts.com. 86400 IN MX 10 mail.hotlocalescorts.com.

;; AUTHORITY SECTION:
hotlocalescorts.com. 86400 IN NS dns2.inyc.com.
hotlocalescorts.com. 86400 IN NS dns1.inyc.com.

;; ADDITIONAL SECTION:
mail.hotlocalescorts.com. 86400 IN A 66.128.207.69

--- So, your mail server has been changed, but it has a TTL of 86,400 seconds. (24 hours).

The reason you get the wrong ping is because your isp's DNS has the old address cached (and will keep it for 24 hours). Turning off your computer or modem won't help, your isp has the number cached.

In the meantime, to check your mail, put in the hardwired address of 66.128.207.69 in Eudora and you can pop in until the 24 hours pass...

Well so why can everyone else ping it?

[DTK]

Originally posted by EscortBiz


Well so why can everyone else ping it?

We all use Jesus DNS

[heymatty]

Because you are the only person who accessed it, so only your isp has it cached

[strainer]

Originally posted by heymatty
Because you are the only person who accessed it, so only your isp has it cached

Exactly. Since I haven't been to your site in the last 24 hours, my DNS server had to do a fresh query. Then again, I run my own DNS here. If I used my isp's DNS, like most people, there is a fair chance their nameserver might have it cached.