slight dns confusion again

slight dns confusion again

[Gregory Nowak]

Hi all,

I decided to find out what my secondary dns knows about my domain after getting my primary DNS configured a few days ago.


DiG 9.1.2 <<>> @ns2.granitecanyon.com romualt.dhs.org -t SOA
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44790
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;romualt.dhs.org.               IN      SOA

;; AUTHORITY SECTION:
dhs.org.                6608    IN      NS      ns1.dhs.org.
dhs.org.                6608    IN      NS      ns2.dhs.org.

;; ADDITIONAL SECTION:
ns1.dhs.org.            156589  IN      A       63.175.98.30
ns2.dhs.org.            156589  IN      A       202.77.181.57

;; Query time: 93 msec
;; SERVER: 65.102.83.43#53(ns2.granitecanyon.com)
;; WHEN: Fri May 10 13:57:21 2002
;; MSG SIZE  rcvd: 101



Upon seeing this, I became conserned that I didn't get what I was expecting (which was the SOA record for my domain). 

Since it was late at night, and there was no trafic to my box for a while according to my logs, I decided to shut down my primary dns and do some experimenting.

After shutting down my bind, the first thing I did was:

dig romualt.dhs.org -t SOA

and got a time out error from dig.

Then, I tried accessing my new site.

lynx http://www.romualt.dhs.org

and was informed by lynx that the site could not be found, even though apache was still running.

Next, I got into my remote unix account, and tried to access linserver.romualt.dhs.org by telnetting to it on a certain port. This worked fine. Then, I reactivated my primary dns, and things were fine.

Does this mean that zone transfers are not taking place between my primary and secondary DNS servers? I was under the impression that my allow transfer directives in /etc/named.conf were fine, since I wrote them according to the docs, and since named didn't complain. Maybe it would be best if someone experienced was willing to have a look at my named.conf and zone files to let me know what I screwed up. If anyone is willing to do that, please e-mail me privately. 

Also, if anyone would like to let me know what you think about
http://www.romualt.dhs.org
, please do so. I'd be interested in getting some comments.
Thanks.
Greg

Re: slight dns confusion again

[Cecil H. Whitley]

Hi,
One suggestion first.  I think you missed a trailing period.  It should be
dig romualt.dhs.org. -t SOA
If I remember correctly.  Give that a try with your resolv.conf set to your
secondary dns.  If that fails, I will be glad to look over your files.
Regards,
Cecil

Re: slight dns confusion again

[William F. Acker WB2FLW +1-303-777-8123]

Hi Gregg,

     It sounds like you were using the name-server that you just shut down
as your default.  If that's right, you shouldn't have been able to resolve
anything from your box.  The problem with doing it from a system that you
frequent such as the Unix box you mentioned is that it was likely to have
your info cached somewhere along the way.  It might have been a good idea
to log in to speakup.octothorp.org, a place where you're not likely to be
querying your stuff from very often, to see if it could go out to
granatecanyon to get the info.  Or, even easier, try appending 63.224.68.1
to the end of your dig request.  I'm pretty sure that that should work.





          HTH.
          Bill

Re: slight dns confusion again

[Raul A. Gallegos]

Hi.  Speaking of all this dns weirdness and bill's latest message it
prompted me to wonder why my domain is not updated on all changes.  I'll
explain.  I have asmodean.net and set up 4 authoritive dns servers
ns1.mi.sprintbbd.net, ns2.mi.sprintbbd.net, ns1.az and ns2.az.  Now the
host saidin.asmodean.net used to have IP 216.254.102.192 but when I
moved and got a new IP address I changed it to 216.254.114.61 which is
the current one.  Since I currently only have one machine I figured I
would just have cname records to www.asmodean.net, ftp.asmodean.net and
mg.asmodean.net all cname to saidin.asmodean.net.  OK, now to the
problem.  When I moved and changed it to 216.254.114.61 everything
seemed to be working yet if you query dns servers at random some still
say that saidin resolves to the 102.192 address instead of the 114.61
address.  And so of course because the www. host was cnamed to saidin it
too was not resolving.    I checked and rechecked my zone file and it
looks correct.  I can ask ns1.mi, ns2.mi, ns1.az and ns2.az for the
information with dig or host and they give the correct 114.61 IP
address.   If you ask for example ns1.earthlink.net and ns1.kc.rr.com
they do not have the correct address.  Furhter more what I di was change
the cname records to a records and just have the individual hosts www,
ftp, and mg resolve to the IP 114.61 directly instead of the cname
saidin.  NOw those ns servers which still say that saidin is on 102.192
report the correct ip address 114.61 for www and mg yet they still say
that saidin is 102.192.

Can anyone explain why this would be so?  The change from the old ip to
the new one happened in March.  That is definitely past the one week ttl
time set on most default name servers.

-- 
If you perceive that there are four possible ways in which a procedure can
go wrong, and circumvent these, then a fifth way will promptly develop.
Raul A. Gallegos - http://www.asmodean.net

Re: slight dns confusion again

[Cecil H. Whitley]

Hi,
Did you remember to change the serial numbers when you made the change?
Also, did your upstream dns change their a records for the nameserver(s)?
Regards,
Cecil

Re: slight dns confusion again

[Raul A. Gallegos]

I did change the serial numbers.  As to your other question I'm not 
sure what you are trying to ask.    the sprintbbd.net are the only
authoritive name servers for my domain.   What upstream servers are 
you referring to?

Cecil H. Whitley said the following on Fri, May 10,
2002 at 10:53:03PM -0400:
> Hi,
> Did you remember to change the serial numbers when you made the change?
> Also, did your upstream dns change their a records for the nameserver(s)?
> Regards,
> Cecil
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
If you perceive that there are four possible ways in which a procedure can
go wrong, and circumvent these, then a fifth way will promptly develop.
Raul A. Gallegos - http://www.asmodean.net

Re: slight dns confusion again

[Darrell Shandrow]

[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]

Hi Raul,

DNS delegates authority for domains.  Hypothetically, this delegation could 
be many levels deep...

If you serve your own domains, then your "upstream" DNS would simply be the 
root name servers.

Regards.

At 01:20 AM 5/11/2002 -0500, you wrote:

>I did change the serial numbers.  As to your other question I'm not
>sure what you are trying to ask.    the sprintbbd.net are the only
>authoritive name servers for my domain.   What upstream servers are
>you referring to?
>
>Cecil H. Whitley said the following on Fri, May 10,
>2002 at 10:53:03PM -0400:
> > Hi,
> > Did you remember to change the serial numbers when you made the change?
> > Also, did your upstream dns change their a records for the nameserver(s)?
> > Regards,
> > Cecil
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>--
>If you perceive that there are four possible ways in which a procedure can
>go wrong, and circumvent these, then a fifth way will promptly develop.
>Raul A. Gallegos - http://www.asmodean.net
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.361 / Virus Database: 199 - Release Date: 5/7/2002

Best regards,
Darrell Shandrow
Access technology consulting / network and UNIX         systems administration.

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.361 / Virus Database: 199 - Release Date: 5/7/2002

Re: slight dns confusion again

[Gregory Nowak]

Hmmm, very interesting. The thing with my situation is that I have never before owned a domain. Besides, I've sent off my configuration and zone files to Cecil, so we'll see what the vertict is in my case in terms of how well I've applied what I've read in the docs and howtos.
Greg


On Fri, May 10, 2002 at 09:45:02PM -0500, Raul A. Gallegos wrote:
> Hi.  Speaking of all this dns weirdness and bill's latest message it
> prompted me to wonder why my domain is not updated on all changes.  I'll
> explain.  I have asmodean.net and set up 4 authoritive dns servers
> ns1.mi.sprintbbd.net, ns2.mi.sprintbbd.net, ns1.az and ns2.az.  Now the
> host saidin.asmodean.net used to have IP 216.254.102.192 but when I
> moved and got a new IP address I changed it to 216.254.114.61 which is
> the current one.  Since I currently only have one machine I figured I
> would just have cname records to www.asmodean.net, ftp.asmodean.net and
> mg.asmodean.net all cname to saidin.asmodean.net.  OK, now to the
> problem.  When I moved and changed it to 216.254.114.61 everything
> seemed to be working yet if you query dns servers at random some still
> say that saidin resolves to the 102.192 address instead of the 114.61
> address.  And so of course because the www. host was cnamed to saidin it
> too was not resolving.    I checked and rechecked my zone file and it
> looks correct.  I can ask ns1.mi, ns2.mi, ns1.az and ns2.az for the
> information with dig or host and they give the correct 114.61 IP
> address.   If you ask for example ns1.earthlink.net and ns1.kc.rr.com
> they do not have the correct address.  Furhter more what I di was change
> the cname records to a records and just have the individual hosts www,
> ftp, and mg resolve to the IP 114.61 directly instead of the cname
> saidin.  NOw those ns servers which still say that saidin is on 102.192
> report the correct ip address 114.61 for www and mg yet they still say
> that saidin is 102.192.
> 
> Can anyone explain why this would be so?  The change from the old ip to
> the new one happened in March.  That is definitely past the one week ttl
> time set on most default name servers.
> 
> -- 
> If you perceive that there are four possible ways in which a procedure can
> go wrong, and circumvent these, then a fifth way will promptly develop.
> Raul A. Gallegos - http://www.asmodean.net
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: slight dns confusion again

[William F. Acker WB2FLW +1-303-777-8123]

Hi Raul,

     The problem is that the internic thinks that saidin is a name-server.  
You should be able to fix it at godady.  If you want it to be a 
name-server, even for playing, or to host other peoples domains, change the 
IP address.  If you don't intend for it to be a name-server, you could 
just delete the record.




          HTH.
          Bill


On Fri, 10 May 
2002, Raul A. Gallegos wrote:

> Hi.  Speaking of all this dns weirdness and bill's latest message it
> prompted me to wonder why my domain is not updated on all changes.  I'll
> explain.  I have asmodean.net and set up 4 authoritive dns servers
> ns1.mi.sprintbbd.net, ns2.mi.sprintbbd.net, ns1.az and ns2.az.  Now the
> host saidin.asmodean.net used to have IP 216.254.102.192 but when I
> moved and got a new IP address I changed it to 216.254.114.61 which is
> the current one.  Since I currently only have one machine I figured I
> would just have cname records to www.asmodean.net, ftp.asmodean.net and
> mg.asmodean.net all cname to saidin.asmodean.net.  OK, now to the
> problem.  When I moved and changed it to 216.254.114.61 everything
> seemed to be working yet if you query dns servers at random some still
> say that saidin resolves to the 102.192 address instead of the 114.61
> address.  And so of course because the www. host was cnamed to saidin it
> too was not resolving.    I checked and rechecked my zone file and it
> looks correct.  I can ask ns1.mi, ns2.mi, ns1.az and ns2.az for the
> information with dig or host and they give the correct 114.61 IP
> address.   If you ask for example ns1.earthlink.net and ns1.kc.rr.com
> they do not have the correct address.  Furhter more what I di was change
> the cname records to a records and just have the individual hosts www,
> ftp, and mg resolve to the IP 114.61 directly instead of the cname
> saidin.  NOw those ns servers which still say that saidin is on 102.192
> report the correct ip address 114.61 for www and mg yet they still say
> that saidin is 102.192.
> 
> Can anyone explain why this would be so?  The change from the old ip to
> the new one happened in March.  That is definitely past the one week ttl
> time set on most default name servers.
> 
> 

Re: slight dns confusion again

[Raul A. Gallegos]

lol, lol and once more lol.  This is tottaly the thing I forgot to do. I
remember now when I was moving I had to first change the name server
information for my domain from saidin.asmodean.net to the ones on
sprintbbd.net and then had to change or unregister the name server.  Well, I
changed asmodean.net to sprintbbd.net but totally forgot to change the
actual name server.  Talk about major oops and since I didn't even think I
forgot that I was under the assumption it had been done and so didn't even
check to see about it.


----- Original Message -----
From: "William F. Acker WB2FLW +1-303-777-8123" <wacker@octothorp.org>
To: <speakup@braille.uwo.ca>
Sent: Saturday, May 11, 2002 2:56 AM
Subject: Re: slight dns confusion again


>
>
> Hi Raul,
>
>      The problem is that the internic thinks that saidin is a name-server.
> You should be able to fix it at godady.  If you want it to be a
> name-server, even for playing, or to host other peoples domains, change
the
> IP address.  If you don't intend for it to be a name-server, you could
> just delete the record.
>
>
>

Re: slight dns confusion again

[Raul A. Gallegos]

Well this sucks.  I looked up saidin.asmodean.net on the name server whois
and sure enough it comes up with the old IP. godaddy does not say that I
have any registered name servers.  So since they say I don't ahve any I
can't modify it. So I'm going to add a new name server with the saidin host
and new ip and see if that will overwrite the old ip.

This is not good if godaddy has no record of me making that name server
which I clearly used to have.  Hpefully they will just let me update the new
IP on it.

----- Original Message -----
From: "Raul A. Gallegos" <raul@asmodean.net>
To: <speakup@braille.uwo.ca>
Sent: Saturday, May 11, 2002 3:13 PM
Subject: Re: slight dns confusion again


> lol, lol and once more lol.  This is tottaly the thing I forgot to do. I
> remember now when I was moving I had to first change the name server
> information for my domain from saidin.asmodean.net to the ones on
> sprintbbd.net and then had to change or unregister the name server.  Well,
I
> changed asmodean.net to sprintbbd.net but totally forgot to change the
> actual name server.  Talk about major oops and since I didn't even think I
> forgot that I was under the assumption it had been done and so didn't even
> check to see about it.

Re: slight dns confusion again

[Igor Gueths]

Hi Raul. Good luck with overwriting the old ip. If it doesn't work, what
will end up happening most likely is a collision between one domain and
two ips. If more than one nameserver responds with the same ip, then
things are probably ok. However, if two nameservers respond with two
different ips for the same domain, then you have a problem.

Gates go to hell, your OS is waiting for you there!

On Sat, 11 May 2002, Raul A. Gallegos wrote:

> Well this sucks.  I looked up saidin.asmodean.net on the name server whois
> and sure enough it comes up with the old IP. godaddy does not say that I
> have any registered name servers.  So since they say I don't ahve any I
> can't modify it. So I'm going to add a new name server with the saidin host
> and new ip and see if that will overwrite the old ip.
>
> This is not good if godaddy has no record of me making that name server
> which I clearly used to have.  Hpefully they will just let me update the new
> IP on it.
>
> ----- Original Message -----
> From: "Raul A. Gallegos" <raul@asmodean.net>
> To: <speakup@braille.uwo.ca>
> Sent: Saturday, May 11, 2002 3:13 PM
> Subject: Re: slight dns confusion again
>
>
> > lol, lol and once more lol.  This is tottaly the thing I forgot to do. I
> > remember now when I was moving I had to first change the name server
> > information for my domain from saidin.asmodean.net to the ones on
> > sprintbbd.net and then had to change or unregister the name server.  Well,
> I
> > changed asmodean.net to sprintbbd.net but totally forgot to change the
> > actual name server.  Talk about major oops and since I didn't even think I
> > forgot that I was under the assumption it had been done and so didn't even
> > check to see about it.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: slight dns confusion again

[Igor Gueths]

Hi Raul. Did you check whois on your domain to see when the record was
last updated? This could be part of the problem, assuming that rr.com and
earthlink.net get their dns updates from whois.

Gates go to hell, your OS is waiting for you there!

On Fri, 10 May 2002, Raul A. Gallegos wrote:

> Hi.  Speaking of all this dns weirdness and bill's latest message it
> prompted me to wonder why my domain is not updated on all changes.  I'll
> explain.  I have asmodean.net and set up 4 authoritive dns servers
> ns1.mi.sprintbbd.net, ns2.mi.sprintbbd.net, ns1.az and ns2.az.  Now the
> host saidin.asmodean.net used to have IP 216.254.102.192 but when I
> moved and got a new IP address I changed it to 216.254.114.61 which is
> the current one.  Since I currently only have one machine I figured I
> would just have cname records to www.asmodean.net, ftp.asmodean.net and
> mg.asmodean.net all cname to saidin.asmodean.net.  OK, now to the
> problem.  When I moved and changed it to 216.254.114.61 everything
> seemed to be working yet if you query dns servers at random some still
> say that saidin resolves to the 102.192 address instead of the 114.61
> address.  And so of course because the www. host was cnamed to saidin it
> too was not resolving.    I checked and rechecked my zone file and it
> looks correct.  I can ask ns1.mi, ns2.mi, ns1.az and ns2.az for the
> information with dig or host and they give the correct 114.61 IP
> address.   If you ask for example ns1.earthlink.net and ns1.kc.rr.com
> they do not have the correct address.  Furhter more what I di was change
> the cname records to a records and just have the individual hosts www,
> ftp, and mg resolve to the IP 114.61 directly instead of the cname
> saidin.  NOw those ns servers which still say that saidin is on 102.192
> report the correct ip address 114.61 for www and mg yet they still say
> that saidin is 102.192.
>
> Can anyone explain why this would be so?  The change from the old ip to
> the new one happened in March.  That is definitely past the one week ttl
> time set on most default name servers.
>
> --
> If you perceive that there are four possible ways in which a procedure can
> go wrong, and circumvent these, then a fifth way will promptly develop.
> Raul A. Gallegos - http://www.asmodean.net
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: slight dns confusion again

[Gregory Nowak]

Hi Bill and all,

I just briefly shut down my primary DNS again, and tried bill's suggestion:

"dig @63.224.68.1 romualt.dhs.org. -t SOA", and got exactly what I expected. I varified that my primary named was actually down by looking at my logs right after shutting it down, and by telneting to 127.0.0.1 53, and getting conection refused. So, I guess it sounds like my zone transfers are fine after all. Is this asumption correct?
Greg