Date: Tue, 12 Oct 1999 22:37:07 -0500 From: Carol Deihl <carol@tinker.com> To: jahanur <jahanur@jjsoft.com> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: nslookup problem please help Message-ID: <3803FE63.9024EC24@tinker.com> References: <Pine.BSF.3.96.991012202509.1219E-100000@runner.jjsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Jahanur,
Basically, you pay internic to get the root servers to tell *which*
name servers to ask when looking for your domain. Then when someone
does an nslookup, (some details left out here for simplicity) the
root server says look at ns.iguru.net to find out where your domain
is; if ns.iguru.net can't be reached for some reason, look at
ns.iguru.com.
Note that anyone who runs a name server is free to put anything they
want in their own name server - and it is quite common that when a
domain moves to a new hosting facility, no one gets around to removing
the old dns records from the old name servers. But, that is not the
problem here.
The problem here is that only *one* of the *two* new name servers
has the correct information. The ns.iguru.net has *wrong* data in
it, and since it is listed first at the internic, that is the name
server that people are hitting. (ns.iguru.com, the second name
server, has the correct information.)
The solution is to carefully check your zone file *on ns.iguru.net*
to make sure it has the correct data, correct the serial number as
another poster has mentioned (e.g. use 1999101201), and HUP named.
Check your log file to see if it reports any errors in your zone
file.
Note that even after you've done this, you will still have to wait
for things to time out of caches. But, you can check the particular
name server to see what it's reporting with either dig:
$ dig @ns.iguru.net turkishtop500.com any
or with nslookup:
$ nslookup
> server ns.iguru.net
Default Server: ns.iguru.net
Address: 208.206.231.66
> set type=any
> turkishtop500.com
Carol
jahanur wrote:
>
> ---------- Forwarded message ----------
>
> I have nothing to do with ns1.dynamicaweb.net. I dont know who they are.
> They may be the previous host ppl. Thats what I am trying to resolve to
> their site. Unless ns1.dynamicaweb.net still did not take the site down.
> If you do ping you will see that it still showing their address.
>
> Is it true then that it does not matter what the internic reports for the
> dns servers anybody can host it.
> Or then why do you pay internic at all. If it is not telling the nslookup
> for turkishtop500.com in ns.iguru.net or .com
> Somthing must be wrong. By the way here is zone file.
>
> turkishtop500.com. IN SOA astguru2.turkishtop500.com. root.turkishtop500.com (
> 19991012; serial number
> 36000 ; refresh 10 hrs
> 3600 ; retry 1 hours
> 3600000 ; expire 100 hours
> 3600 ; minimum 10 hrs
> )
> ;define nameservers
> ;
> turkishtop500.com. NS astguru2.iguru.com.
> turkishtop500.com. A 208.206.231.67
> ;define localhost
> ;
> localhost IN A 127.0.0.1
> astguru2 IN A 208.206.231.67
> turkishtop500.com IN MX 10 astguru2.iguru.com
> ; IN MX 10 astguru2
> ;setup the hosts
> ;
> ;
> ;* IN MX 10 ns.jjsoft.com.
> www IN CNAME astguru2.turkishtop500.com.
> ns IN CNAME astguru2.turkishtop500.com.
> mail IN CNAME astguru2.turkishtop500.com.
> pop3 IN CNAME astguru2.turkishtop500.com.
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-isp" in the body of the message
--
Carol Deihl - principal, Shrier and Deihl - mailto:carol@tinker.com
Remote Unix Network Admin, Security, Internet Software Development
Tinker Internet Services - Superior FreeBSD-based Web Hosting
http://www.tinker.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3803FE63.9024EC24>