Barry Margolin wrote:
In article <mailman.702.1255556893.14796.bind-us...@lists.isc.org>,
Robert Moskowitz <r...@htt-consult.com> wrote:
SOLVED!!!
Problem was with the DNS server for home.htt. The zone files there are
built from scripts from a database, and there are problems with the SOA,
NS, and MX records. I will have to submit a bug.
I don't get it. I thought things worked correctly when you queried the
DNS server for home.htt, and the problem was only when you queried the
htt server.
Truly weird. I sent in a bug report to the amahi developers, and then I
had to actually make the fixes to the script. Turned out not to be too
hard. At least for this problem. There are others that are not as
broken, but still problems...
When I queried from home.htt (really hda.home.htt), it appears that it
does not matter that the SOA and NS are wrong and do not point to an IP
address. It is authoratative for the zone and just reports from its
cache. Likewise a client that uses it directly as its nameserver, would
never be the wiser of the problem. Only when another nameserver did the
lookup. If you look at that TCPDUMP use see the first lookup of say,
wiki.home.htt which returns the A record. Then a lookup of home.htt
which fails. From this point on, ANY lookup of any host in home.htt
fails completely. The cache is 'ruined?' with that failed lookup of the
NS from hda.home.htt.
Wierd, but then who puts an SOA and NS entry that does not have an A
record? That is the case here...
It could also been fixed simply with an A record for home.htt which many
sites do so that http://home.htt would work.
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
