by rhyde » Fri, 16 Jun 2000 04:00:00
How do I resolve this error when my ISP does not have the PTR records for
the DNS servers? - I'd rather not run in.named on this particular box.
Thanks
Rhyder Storm
by Rich Tee » Fri, 16 Jun 2000 04:00:00
--
Rich Teer
NT tries to do almost everything UNIX does, but fails - miserably.
The use of Windoze cripples the mind; its use should, therefore, be
regarded as a criminal offence. (With apologies to Edsger W. Dijkstra)
If it ain't analogue, it ain't music.
Voice: +1 (250) 763-6205
WWW: www.rite-group.com
1. RH50 nslookup IP doesn't match ISP nslookup ip??!?
Hi,
I'm running RH50, 2.0.32. I've noticed recently that for some reason,
the IP resolved for a specific domain does not match that reported by
my ISP. In other words, I've got a domain name from dyn.ml.org. Once
updated after modem connection, the rest of the world can see my box
just fine. But, for some reason, the IP reported by nslookup on my
RH50 box for my domain name doesn't match that provided by my ISP
nslookup. Also, this isn't consistent. If I mess around with it enough
(not really fixing anything, just running lots of tests) it will then
be fine for several hours. Then, it will be wrong again.
So, on Friday, everything was fine. Saturday, the IP being returned by
my ISP nslookup was the correct one, and since ALWAYS has been. But,
the nslookup returned by my RH50 box both Saturday and today, Sunday,
keeps reverting to the IP I was assigned Friday by my ISP.
My ISP has 2 DNS servers, and this happens on both. Anyway, the fact
that my ISP nslookup is always correct really doesn't lead me to
believe that either my ISP or the people at dyn.ml.org have problems.
It seems to be my RH50 box.
So, what's the problem, since the rest of the world can see my box
anyway? Well, I have a script that runs every half hour to make sure
that the IP hasn't changed (like if the modem accidently gets
disconnected). Anyway, since the script uses nslookup on the RH50 box,
it keeps reporting that the IP for my domain name has changed for some
reason. Does nslookup have some config file I missed? I thought it
just used /etc/resolv.conf. BTW, I'm running IP masq on this machine,
and AFAIK, have had no other DNS lookup problems...
What could be causing this? I've had this box up about a month, and
haven't made almost any major changes to it for weeks. This is the
first this has happened.
Thanks,
Jon
3. nslookup fails on DNS server
5. DNS Problem: NSLOOKUP gives default server of all 0.0.0.0's
6. verifying/testing apache's rewrite
7. nslookup tries to reverse lookup DNS IP?
8. How do I search for a file - YET ANOTHER TYPICAL mjt NON-REPONSE!
9. Q: DNS, nslookup, /etc/hosts, nsswitch and name resolution.
10. Qs: Can't get connected to ISP
11. I can't resolve domain names using my ISP DNS Server!!!!
13. PLEASE HELP: PING, DNS AND NSLOOKUP - NSLOOKUP GOOD PING BAD