Hi all,

I used to host my DNS server and other servers at a different ISP than
I do now. Back then, I had the hostname ns.sourcehosting.net set up
with an IP address of 65.160.204.234 and I used GraniteCanyon for my
authoritative DNS servers. I changed colo providers and started using
Zoneedit.com for authoritative DNS server hosting. The address of
ns.sourcehosting.net also changed to 12.160.213.43. This switch took
place almost a year ago, I think.

Since then, there are some DNS servers out there (most of them, from
what I can tell) that still think ns.sourcehosting.net has the old
address. My current authoritative name servers for sourcehosting.net
are:

NS12.ZONEEDIT.COM
NS14.ZONEEDIT.COM
NS1.DYNI.NET
NS.SOURCEHOSTING.NET

Using dig, I can see that the zoneedit.com and dyni.net DNS servers
have the correct IP address for ns.sourcehosting.net. If I use dig on
the ns.sourcehosting.net machine, it thinks that the IP address is
correct. ns.sourcehosting.net is set up as the master, and the other
3 servers are slaves to it.

However, any other DNS server that I check on the Internet seems to
have the old address for ns.sourcehosting.net:

$ dig @ns1.ezoshosting.net ns.sourcehosting.net A | grep
^ns.sourcehosting.net
ns.sourcehosting.net. 172792 IN A 65.160.204.234

$ dig @ns.austin.ibm.com ns.sourcehosting.net A | grep
^ns.sourcehosting.net
ns.sourcehosting.net. 66383 IN A 65.160.204.234

$ dig @ns1.jlc.net ns.sourcehosting.net A | grep ^ns.sourcehosting.net
ns.sourcehosting.net. 172793 IN A 65.160.204.234

$ dig @ns1.granitecanyon.com ns.sourcehosting.net A | grep
^ns.sourcehosting.net
ns.sourcehosting.net. 43200 IN A 65.160.204.234


So GraniteCanyon still has the old address, but it shouldn't matter
since I don't list it as an auth name server, I don't think. I tried
to delete the zone from there, but it hasn't been successful yet.

My question is - where are all of the rest of the name servers that
I've queried getting the old address from? Do I have to delete
NS.SOURCEHOSTING.NET from the WHOIS record for a while to get things
to settle down, then re-add it or something like that?

If anyone has any ideas, I would appreciate it a lot!

Thank you,
Greg Larkin
----
SourceHosting.Net, LLC
The new baseline for configuration management
[url]http://www.sourcehosting.net/[/url]

> My question is - where are all of the rest of the name servers that
> I've queried getting the old address from? Do I have to delete
> NS.SOURCEHOSTING.NET from the WHOIS record for a while to get things
> to settle down, then re-add it or something like that?

When you registered the name, you entered your NS.SOURCEHOSTING.NET
and its IP address as a nameserver. That address is in the .net
zone as a glue record. If you run 'dig @a.gtld-servers.net
ns.sourcehosting.net' you'll see the old address.

You need to visit your registrar (for sourcehosting.net) and change
the IP address of the nameserver. For GoDaddy, see the FAQ entry
titled "How do I register my own name servers with GoDaddy.com?"

Duane W.

Hmm....I have a follow on question about this.

We have thousands of websites that need to have the DNS moved just like
this.....with hundreds of registrars. Do we have to visit the registrar for
every website? This is bizarre to me.

Why is the IP address glued for the name server. It too occassionally has
to change....


----- Original Message -----
From: "Duane Wessels" <c2de@packet-pushers.com>
To: "Greg Larkin" <glarkin@sourcehosting.net>
Cc: <comp-protocols-dns-bind@isc.org>
Sent: Thursday, April 15, 2004 2:34 PM
Subject: Re: Incorrect nameserver address - where is it coming from?


> > My question is - where are all of the rest of the name servers that
> > I've queried getting the old address from? Do I have to delete
> > NS.SOURCEHOSTING.NET from the WHOIS record for a while to get things
> > to settle down, then re-add it or something like that?
>
> When you registered the name, you entered your NS.SOURCEHOSTING.NET
> and its IP address as a nameserver. That address is in the .net
> zone as a glue record. If you run 'dig @a.gtld-servers.net
> ns.sourcehosting.net' you'll see the old address.
>
> You need to visit your registrar (for sourcehosting.net) and change
> the IP address of the nameserver. For GoDaddy, see the FAQ entry
> titled "How do I register my own name servers with GoDaddy.com?"
>
> Duane W.
>

On Thu, 15 Apr 2004, Michael Barber wrote:

> We have thousands of websites that need to have the DNS moved just like
> this.....with hundreds of registrars. Do we have to visit the registrar for
> every website? This is bizarre to me.

It depends on how your domains are set up. Hopefully you don't
have thousands of different nameserver names. If you're lucky you
have one or a few nameservers for all your domains.

> Why is the IP address glued for the name server. It too occassionally has
> to change....

Glue records solve a chicken-and-egg problem when your nameserver
name (say ns.example.com) lives under its own domain (example.com).

See the DNS and BIND book for a better explanation. (BTW, there
is a 4th edition out now).

Duane W.

Thanks...I see that this is one other problem I have inherited....that I
thought might apply to us (and it does) when that message got posted.

BTW, I will be picking up the DNS and Bind book from Barnes and Noble on the
way home.

And, my mistake, I have experience on Bind 4.95 (I believe)...not just 2
(I'm not that old for goodness sakes ;)

----- Original Message -----
From: "Duane Wessels" <c2de@packet-pushers.com>
To: "Michael Barber" <mikeb@comcity.com>
Cc: <comp-protocols-dns-bind@isc.org>
Sent: Thursday, April 15, 2004 4:37 PM
Subject: Re: Incorrect nameserver address - where is it coming from?


>
>
> On Thu, 15 Apr 2004, Michael Barber wrote:
>
> > We have thousands of websites that need to have the DNS moved just like
> > this.....with hundreds of registrars. Do we have to visit the registrar
for
> > every website? This is bizarre to me.
>
> It depends on how your domains are set up. Hopefully you don't
> have thousands of different nameserver names. If you're lucky you
> have one or a few nameservers for all your domains.
>
> > Why is the IP address glued for the name server. It too occassionally
has
> > to change....
>
> Glue records solve a chicken-and-egg problem when your nameserver
> name (say ns.example.com) lives under its own domain (example.com).
>
> See the DNS and BIND book for a better explanation. (BTW, there
> is a 4th edition out now).
>
> Duane W.