Delinquent DNS (6)

Topic

New Reply

I’m not sure that this is totally the correct forum for this question, but I’m sure all you good folks’ll point me in the righht direction if not.

I’ve just taken over looking after the web site for my church. The site has been around for years.

It is set up on some free web space with a redirection on its “real” domain name.

Now, here’s the crux; the name servers automatically supplied by my ISP do not know the address of the actual host. I’ve never come across this before.

What can one do in this situation? Is there a way to nudge the name servers into action?

The site address is stjamesmilton.port5.com (note no www) and the hosting company is http://www.portland.co.uk
The delinquent nameservers are 194.72.9.34 and 194.74.65.68
and neither the port5 nor the portland.co.uk addresses are recognised by it.

Any ideas?

Reply | Quote

Replies

Have you checked to see if you have any entries in your hosts file that may be causing the problem? Have you contacted the ISP?

Joe

--Joe

Reply | Quote

Contacting the ISP is not possible.

Thanks for your reply. I guess I ought to expand a bit on what PD I
have already done.

First let me explain how I found the problem in the first place:

I work from home, connected to work via a VPN.

My work machine (ThinkPad) and another PC (Netvista) are both connected to
an ADSL Router Modem.

I was getting to these sites with no problem at all from my ThinkPad.
However, when I went to the Netvista, Internet Explorer said that it
couldn’t find the site.

So thought I, what is the difference between these 2 machines. The
difference that I came up with was that the ThinkPad had a virtual network
adapter (the VPN) with work’s DNSs, whilst the Netvista was relying on only the
DNS known by the router modem. (By the way, I’d love to know how windows
decides whether to send stuff down the real network adapter or the virtual
one).

Hence I tried the NSLOOKUP approach. NSLOOKUP with no server parameter heads
straight off down the real network adapter and could not resolve the
address. However, NSLOOKUP when supplied with the work DNS (that is
registered with the virtual adapter) resolved the address perfectly.

So I asked my wife (who is connected at her office on an ADSL connection
with a different ISP) what name servers she was using. Once again NSLOOKUP
when supplied with one of these DNS resolves the address.

Reply | Quote

Have you tried manually configuring the Netvista with one of the working DNS addresses? HTH

Reply | Quote

Paul,
When I went to the address you mentioned, I got this screen:
IS this what you receive or something different? ( it does say they are working on SOME accounts involved )

Reply | Quote