DNS Lookup problem

[debbie]

I'm trying to explain a flaky website which can be viewed fine on some
pcs but not on others (various networks, isps etc.)

I can't view the website at all from my pc, yet a friends pc could
view it first time without messing with his hosts file etc.

I couldn't ping the nameserver address, e.g. ns1.hostname.co.uk
but could ping its ip address.

Once I'd mapped the hostname in my hosts file, I could then ping the
name, but still couldn't view the web for the domain I wanted.

There is another site hosted on that nameserver which I'm aware of
thatI can view ok It looks like it's configured differently though as
if I do a whois lookup on that site it lists the nameservers as

name ipaddress

whereas the faulty site just has

name
(without the ipaddress mapping)

Any ideas, explanations, or pointers to places I could investigate
further would be welcomed.

(btw, apologies to those who have already read this on another, less
suitable, newsgoup.)

Debbie

 

[Guest]

I'm trying to explain a flaky website which can be viewed fine on some
pcs but not on others (various networks, isps etc.)

I can't view the website at all from my pc, yet a friends pc could
view it first time without messing with his hosts file etc.

I couldn't ping the nameserver address, e.g. ns1.hostname.co.uk
but could ping its ip address.

Once I'd mapped the hostname in my hosts file, I could then ping the
name, but still couldn't view the web for the domain I wanted.

There is another site hosted on that nameserver which I'm aware of
thatI can view ok It looks like it's configured differently though as
if I do a whois lookup on that site it lists the nameservers as

name ipaddress

whereas the faulty site just has

name
(without the ipaddress mapping)

Any ideas, explanations, or pointers to places I could investigate
further would be welcomed.

(btw, apologies to those who have already read this on another, less
suitable, newsgoup.)

Debbie

Your DNS server is the problem, try to see or correct the settings for the
DNS.
Try this:
= Click Start >> Control panel >> Network and Internet Connections >> Double
click Network connections, then right your LAN Icon and select Properties.
On the LAN properties under General make sure the Internet Protocol TCP/IP
is selected and click Properties.
There make sure the Machine Get assigned Automatically IP address and DNS
Auto.

= Click start >> Control Panel >> Double Click Network and Internet
Connections >> Double click Internet Options, on the IE Properties window
you will see these Options:
General | Security | Privacy | Content | Connections | Programs
| Advanced.
Clear your cookies and Caches while on the IE properties.
Click on Connections tab and make sure the Connection is listed there then
click on LAN settings button and uncheck Automatically detect settings.
Click [OK] and close Hit F5 and open a run command and type in:
ipconfig /flushdns click [OK]
ipconfig /renew click [OK]
netsh winsock reset click [OK]

Download the winsock fix from here:
http://www.nasstec.co.uk/tools.html
Reboot your machine.

If the above didn't help, then write back with more info (technical Info)
about the Connection nature, is it a router/modem, workgroup, are you able to
access other websites or this particular site is the problematic one?,
firewall installed/Anti-virus, Anti-malware...etc...

 

[debbie]

Download the winsock fix from here:http://www.nasstec.co.uk/tools.html
Reboot your machine.

If the above didn't help, then write back with more info (technical Info)
about the Connection nature, is it a router/modem, workgroup, are you able to
access other websites or this particular site is the problematic one?,
firewall installed/Anti-virus, Anti-malware...etc...- Hide quoted text -

That didn't help. The web site in question is flaky on more than one
computer, not just mine. Some can see it and others can't.
I can access all other websites ok. Well, I could: I seem to have a
problem since I did the winsock fix. I'm trying to sort this out on my
other pc.

 

[Guest]

You don't say how you are connecting to the site, so I assume broadband via a
router.

I find that a lot of broadband/cable routers have flaky internal DNS servers
(or DNS forwarding.) Often you're better using the DNS servers provided by
your ISP, directly.

If you've changed to automatic IP asignment then chances are you're now
using the router as the DNS server, which explains why your PC has acquired
the problem.

In some cases a firmware update for the router will improve matters, but the
best resolution is to assign the ISP's (or your domain-controller's if it's a
corporate LAN) DNS server addresses directly in Windows TCP settings.