Date: Tue, 12 Oct 1999 19:27:56 -0500 From: Carol Deihl <carol@tinker.com> To: freebsd-isp@FreeBSD.ORG Subject: Re: nslookup problem please help. Message-ID: <3803D20C.B5D27C47@tinker.com>
next in thread | raw e-mail | index | archive | help
Hello Jahanur,
Registration at the Internic doesn't tell *where* your *servers* are,
but *which name servers* to ask to find out where your servers are.
The Internic is reporting that the name servers for your domain are:
turkishtop500.com. 172800 NS NS.IGURU.NET.
turkishtop500.com. 172800 NS NS.IGURU.COM.
At ns.iguru.net, a "dig" reports this information:
$ dig @ns.iguru.net turkishtop500.com any
; <<>> DiG 2.2 <<>> @ns.iguru.net turkishtop500.com any
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd ra; Ques: 1, Ans: 4, Auth: 2, Addit: 2
;; QUESTIONS:
;; turkishtop500.com, type = ANY, class = IN
;; ANSWERS:
turkishtop500.com. 60356 NS NS1.DYNAMICWEB.NET.
turkishtop500.com. 60356 NS NS2.DYNAMICWEB.NET.
turkishtop500.com. 24276 SOA NS1.DYNAMICWEB.NET.
staff.DYNAMICWEB.NET. (
1999080205 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
604800 ; expire (7 days)
86400 ) ; minimum (1 day)
turkishtop500.com. 67250 A 205.178.149.87
;; AUTHORITY RECORDS:
turkishtop500.com. 60356 NS NS1.DYNAMICWEB.NET.
turkishtop500.com. 60356 NS NS2.DYNAMICWEB.NET.
;; ADDITIONAL RECORDS:
NS1.DYNAMICWEB.NET. 151540 A 205.178.159.134
NS2.DYNAMICWEB.NET. 151540 A 205.178.138.137
Note this information says that servers at dynamicweb.net are
your name servers, which I presume is the *old* information. So, the
named configuration at ns.iguru.net is *not* correct. It needs to
be fixed.
The information at your secondary (ns.iguru.com) is different:
$ dig @ns.iguru.com turkishtop500.com any
; <<>> DiG 2.2 <<>> @ns.iguru.com turkishtop500.com any
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr aa rd ra; Ques: 1, Ans: 3, Auth: 1, Addit: 1
;; QUESTIONS:
;; turkishtop500.com, type = ANY, class = IN
;; ANSWERS:
turkishtop500.com. 3600 NS astguru2.iguru.com.
turkishtop500.com. 3600 A 208.206.231.67
turkishtop500.com. 3600 SOA astguru2.turkishtop500.com.
root.turkishtop500.com.turkishtop500.com. (
19991012 ; serial
36000 ; refresh (10 hours)
3600 ; retry (1 hour)
3600000 ; expire (41 days 16 hours)
3600 ) ; minimum (1 hour)
;; AUTHORITY RECORDS:
turkishtop500.com. 3600 NS astguru2.iguru.com.
;; ADDITIONAL RECORDS:
astguru2.iguru.com. 3600 A 208.206.231.67
So if 208.206.231.67 is the correct (new) address, ns.iguru.com has the
correct information. If not, it will need to be updated too.
Note that when you update the named config, remember to update the
serial number in the SOA record, or named won't notice that you've
updated the information. Also, remember to HUP named afterwards, too!
Hope this helps,
Carol
jahanur wrote:
>
> Hi,
>
> I am having problem with one my customers domain name.
> I am setting it up as a virtual name.
> We have a lot of virtuals they are all working fine.Even I added different
> domain name after this particular one and they are all working fine.
> Domain name is turkishtop500.com.
> If I do whois turkishtop500.com. it shows our dns entries successfully.
> And named was setup correctly also.
> but if I do nslookup on turkishtop500.com it resolves to old server.
> I dont have any clue to what is going on.
> I thought if I change it with the Internic it should automaticaly look for
> our servers.
> Please help.
>
> Thanks
> Jahanur@jjsoft.com
--
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?3803D20C.B5D27C47>