Single name server not propagating

Kevin Schaeper kevins at ecx.com
Wed Nov 7 21:13:32 UTC 2001



Thanks...
I began to think that was the problem ( one of them)
I had set 53 open and may have closed it, I believe I set the box in a DMZ
to test it all.
perhaps that config didn't work or I screwed up.

at any rate I will start there. Thanks.

I am somewhat new and starting from scratch...

Thanks.

-----Original Message-----
From: Michael Kjorling [mailto:michael at kjorling.com]
Sent: Wednesday, November 07, 2001 12:57 PM
To: BIND-Users
Subject: RE: Single name server not propagating



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, as Barry pointed out, there isn't a lot we can do to help people
who hide their real domains and IPs behind "doctored" information. Not
to mention logs and configuration files... snipping is OK most of the
times but downright editing them can be disasterous. It's amazing how
many problems are solved by this doctoring.

When I ask the A gTLD root server, splashdomain.com. is delegated to
the single name server NS1.splashdomain.com., which has a glue A RR
pointing to 4.43.252.248. When I do a SOA query on this server for
splashdomain.com. using dig, it times out. Traceroute gives me an OK
result but a long roundtrip time - over 1200 ms. This may cause some
resolvers to time out while resolving your domain (though dig spent a
good time on this, far more than a few seconds). (Comparisation: the
last router before 4.43.252.248, 4.24.148.178, has a roundtrip of
roughly 220 ms with one packet out of three timing out or getting
dropped for some reason.)

It seems to me right now at least that you have a firewall issue. Make
sure traffic to port 53 over TCP _and_ UDP is allowed in your
firewall. Also, get a slave server somewhere. Secondary.com provides
that service for free for up to five domains or 100 RRs (whichever
limit you hit first), and so far seems to be working perfectly for me.


Michael Kjörling


On Nov 7 2001 12:05 -0800, Kevin Schaeper wrote:

> the domain name is splashdomain.com
> and i had it set to ns1.splashdomain.com
>
> currently I was just trying mydomain.com as an ip pointer, cuz I can't
seem
> to get anything to work..

- -- 
Michael Kjörling  --  Programmer/Network administrator  ^..^
PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e   \/
Internet: michael at kjorling.com -- FidoNet: 2:204/254.4

"There is something to be said about not trying to be glamorous
and popular and cool. Just be real -- and life will be real."
(Joyce Sequichie Hifler, September 13 2001, www.hifler.com)


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Public key is at http://michael.kjorling.com/contact/pgp.html

iD8DBQE76aAQKqN7/Ypw4z4RAvL9AJ4kSFTQyURVTUtuwEoI0aqrqzLhUwCghb3M
RXKU+IXdYU9mceQWMRq5JBU=
=K29s
-----END PGP SIGNATURE-----




More information about the bind-users mailing list