Re: DNS Problem

> From: [email protected]
> To: [email protected]
> Subject: 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 don't understand "shared IP".  Do you mean dynamic?  That is, can you
get a different IP each time you connect?  If so, the DNS has has to
specify a short TTL -- otherwise various DNS servers will have cached
the old values.  Did you configure the port to be DHCP?  If so, the
DHCP server at the ISP should send you the proper nameservers and
resolv.conf should be updated OK.  If you didn't set it up as DHCP,
it shouldn't have tweaked resolv.conf, but you would then not get the
right IP set up either.



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


Well, that IP was listed as one of the ones you got from your ISP.
The 106.35 one isn't accessible from here and the .11 one (another
of the ones you said your ISP recommended gave the wrong answer.
--------------------------------------------------
[root@ns1 mqueue]# host davidsconsultants.com 192.115.106.10
Using domain server:
Name: 192.115.106.10
Address: 192.115.106.10#53
Aliases: 

davidsconsultants.com has address 203.194.198.198

[root@ns1 mqueue]# host davidsconsultants.com 192.115.106.11
Using domain server:
Name: 192.115.106.11
Address: 192.115.106.11#53
Aliases: 

davidsconsultants.com has address 66.216.18.92

[root@ns1 mqueue]# host davidsconsultants.com 192.115.106.35
Using domain server:
Name: 192.115.106.35
Address: 192.115.106.35#53
Aliases: 

Host davidsconsultants.com not found: 5(REFUSED)
--------------------------------------------------



> > 
> > 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?

The problem is that the DNS servers that your ISP recommended have
inconsistent values.  This has absolutely nothing to do with your
machine.  I'm doing DNS queries from here and getting two different 
answers from 192.115.106.10 and 192.115.106.11.
 
> 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.

The name servers in your NS records give the proper IP ---
--------------------------------------------------

[root@ns1 mqueue]# host -t ns davidsconsultants.com 
davidsconsultants.com name server ns1.station192.com.
davidsconsultants.com name server ns2.station192.com.
[root@ns1 mqueue]# host davidsconsultants.com. ns1.station192.com.
Using domain server:
Name: ns1.station192.com.
Address: 203.194.198.198#53
Aliases: 

davidsconsultants.com has address 203.194.198.198
[root@ns1 mqueue]# 
[root@ns1 mqueue]# host davidsconsultants.com. ns2.station192.com.
Using domain server:
Name: ns2.station192.com.
Address: 203.194.198.199#53
Aliases: 

davidsconsultants.com has address 203.194.198.198
--------------------------------------------------

Is "station192.com" part of your ISP?  It seems like there's some kind
of disconnect between the name servers specified you your ISP and the
ones in the DNS specified for your domain.


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