[73450] in North American Network Operators' Group
Recent changes to UltraDNS, problems?
daemon@ATHENA.MIT.EDU (Robert Blayzor)
Mon Aug 23 19:54:03 2004
Date: Mon, 23 Aug 2004 19:53:13 -0400
From: Robert Blayzor <rblayzor@inoc.net>
To: nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu
Has anyone else noticed any strange problems lately when querying
UltraDNS for name server records?
I have a few scripts that seem to have broken in the past week. A
simple PERL script that looks up NS records from the root servers, which
worked fine last week, suddenly starts reporting that the query is
returning an empty answer.
If I change it to any other TLD servers/domains, it works fine. What is
even more strange is that when I use dig, the lookups are just fine.
(most of the time) Can anyone at UltraDNS (or anyone else for that
matter) shed some light on what might have changed/broken?
#!/usr/bin/perl
use strict;
use Net::DNS; #version 0.48
my @tld = ("tld1.ultradns.net", "tld2.ultradns.net");
my $res = Net::DNS::Resolver->new;
$res->nameservers(@tld);
my $query = $res->query("adaconline.org", "NS");
if($query) {
print "It worked!\n";
} else {
print "It failed!\n";
}
exit;
In the above case the query always returns undef and the errorstring
returned is no error. My initial thought was a bug in Net::DNS, but
I've also heard from others they've started noticing strange lookup
problems when asking UltraDNS directly for answers.
--
Robert Blayzor, BOFH
INOC, LLC
rblayzor@inoc.net
PGP: http://www.inoc.net/~dev/
Key fingerprint = 1E02 DABE F989 BC03 3DF5 0E93 8D02 9D0B CB1A A7B0
Profanity is the one language all programmers know best.
