Re: DNS Problem

On 31 Mar 2003 at 11:14, pete peterson wrote:

> >> What do you mean by "the wrong DNS server"?  If you're making a DHCP
> >> connection to your ISP, the resolv.conf should be pointing to the ISP's
> >> DNS servers.
> > On the Win2k machine I specify my DNS servers (primary and secondary) as
> > 192.115.106.10, 192.115.106.11 as per instructions from my ISP.  I edited the
> > resolv.conf file to reflect this as well.  However, when I was connecting on
> > the Linux machine the resolve.conf file was being overwritten with
> > 192.115.106.35, 192.1115.106.10.  When I query the 192.115.106.35 DNS server
> > for www.davidsconsultants.com I get the wrong IP address (66.216.18.92).  When
> > I query the 192.115.106.10 DNS server for www.davidsconsultants.com I get the
> > correct IP address (203.194.198.198).
> 
> Interestingly, I get 66.216.18.92 if I query 192.115.106.11.  Was that
> address associated with your previous service?  Perhaps you're
> getting some old DNS records that haven't expired?  Is your "ISP" the same
> as your "hosting service"?  Is 203.194.198.198 a static IP assigned to
> you?  If so, are you still setting up the port with DHCP or did you 
> configure it as a static address?  
I am being hosted by a company called ICDSoft.  In general I have been very 
happy with their service so far.  They said they fixed the problem you saw with 
the MX record in the DNS.  This is NOT a static IP assigned to my domain but a 
shared IP.
I am using a local ISP for Internet connectivity.  There are three IP addresses 
I have for DNS servers from my ISP 192.115.106.10, .11 and .35.  The only one 
that has the correct value for davidsconsultants.com is .10.

> 
> I assume 192.1115.106.10 was a typo (did you mean 192.115.106.10?).
Yes. Sorry.

> 
> It appears to me that it's not your machine that's messed up, but
> rather something external to you in the DNS records.  Can you elaborate
> on ISP/DNS/(static or dynamic)?
See above.  ISP is local, DNS server is provided by the ISP, DNS entry is 
maintained by the hosting service, IP address for davidsconsultants.com is a 
shared IP rather than a dedicated IP.

> 
> 
> 
> > I tried to take out the part of the script that was overwriting the
> > resolv.conf file.  This helped in the sense that when I tried to ping
> > www.davidsconsultants.com I got back the correct address.  However, when I
> > went to Netscape I was not directed to the correct server (i.e. pages that I
> > had added to the new host did not come up but did when I accessed them via IP
> > address).
> 
> You shouldn't have to do that.  It's a symptom of something else
> broken.  
Unfortunately, my ISP is not very Linux friendly.  I was hoping to figure out a 
work around rather than fighting with their support.  Since everything works 
when the Win2k machine connects directly they are likely to tell me that it is 
a problem in my Linux installation and they don't troubleshoot Linux systems.

If I have DNS servers in my resolv.conf file that contain the correct 
information then why shouldn't that be sufficient to work?

I though of changing the DNS servers listed in my registrar again so that the 
changes get propagated again (i.e. flip primary and secondary).  Maybe then the 
DNS server on my ISP will get the correct updates.

I guess I can always try calling my ISP support again and hope to get a 
sympathetic technician.