Related to NS record IP change

[KSP]

Swapana,

Short Answer:

The hostnames dn1.nkginfo.com and dn2.nkginfo.com were, at some point,
registered as nameservers with Go Daddy Software.  Contact Go Daddy, and
have them remove these nameserver entries.

Long Answer:

---snip---
[me at dahost] whois -h whois.internic.net "nameserver dn1.nkginfo.com"

Whois Server Version 1.3

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

   Server Name: DN1.NKGINFO.COM
   IP Address: 216.240.145.47
   Registrar: GO DADDY SOFTWARE, INC.
   Whois Server: whois.godaddy.com
   Referral URL: http://registrar.godaddy.com

[me at dahost] whois -h whois.internic.net "nameserver dn2.nkginfo.com"

Whois Server Version 1.3

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

   Server Name: DN2.NKGINFO.COM
   IP Address: 216.105.38.65
   Registrar: GO DADDY SOFTWARE, INC.
   Whois Server: whois.godaddy.com
   Referral URL: http://registrar.godaddy.com
---snip---

Notice how, if you query a.gtld-servers.net for the A record of
"dn2.nkginfo.com", that you get an answer back:

("+no" options for brevity)
---snip---
[pickardk at staff] dig @a.gtld-servers.net dn2.nkginfo.com +noaddit +noauth a

; <<>> DiG 9.2.1 <<>> @a.gtld-servers.net dn2.nkginfo.com +noaddit +noauth a
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1722
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;dn2.nkginfo.com.               IN      A

;; ANSWER SECTION:
dn2.nkginfo.com.        172800  IN      A       216.105.38.65

;; Query time: 69 msec
;; SERVER: 192.5.6.30#53(a.gtld-servers.net)
;; WHEN: Mon Jul 19 15:05:26 2004
;; MSG SIZE  rcvd: 127
---snip---

Whereas, if you were to query the same server for the A record of
"dn3.nkginfo.com", a hostname which has never been registered as a
nameserver with any registrar, you get back no answer at all:

---snip---
[pickardk at staff] dig @a.gtld-servers.net dn3.nkginfo.com +noaddit +noauth a

; <<>> DiG 9.2.1 <<>> @a.gtld-servers.net dn3.nkginfo.com +noaddit +noauth a
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62470
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;dn3.nkginfo.com.               IN      A

;; Query time: 67 msec
;; SERVER: 192.5.6.30#53(a.gtld-servers.net)
;; WHEN: Mon Jul 19 15:07:53 2004
;; MSG SIZE  rcvd: 111
---snip---

In the same fashion that you have no direct control over what
dns1.ghen.net and dns2.ghen.net resolve to, (the "root" servers are doing
this for you, in essence, before your servers ever get the chance), you
likewise have no control over the A record associations for these
hostnames either.  Not for the time being, anyway.

If neither you or your customer plan to use these servers for hosting
authoritative DNS records, request that Go Daddy have these records
removed from the "root" servers.

Best Regards,

ksp

Kevin S. Pickard
ksp at att.com

On Mon, 19 Jul 2004, Swapana Ghosh wrote:

> Hi
>
>       One of our client *nkginfo.com* is keeping their domain in our
> nameserver.
>
> Our name servers are as follows:
>
> dns1.ghen.net
> dns2.ghen.net
>
> Recently the client has changed the IP of that domain to 66.98.146.88.
>
> They are using two more domains as follow...
>
> dn1.nkginfo.com
> dn2.nkginfo.com
>
> as *name servers* . These should be also  changed to 66.98.146.88.
>
> dn1/dn2.nkginfo.com  are mentioned in our nameserver as *A* records.
>
> I  have changed the IP too... But almost 2 days are over, still  it is
> holding the old ip. The trace is showing the old ip of these records.
>
> The old ip of dn1.nkginfo.com was  216.240.145.47  and
> dns2.nkginfo.com was  216.105.38.65
>
> Where i am missing? Should i need to mention anything more to
> indicate it as *name servers*?
>
> Thanks in advance
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Vote for the stars of Yahoo!'s next ad campaign!
> http://advision.webevents.yahoo.com/yahoo/votelifeengine/
>
>
>