We have a /24 from one of our upstream providers that we handoff to a customer. The /24 has been SWIPd to us, and we have nameservers setup with ARIN against that record. Twice now this information has just "disappeared". That is, if do reverse DNS lookups, they returns nothing, whereas they were just working fine earlier. If you do an NS lookup on the block, it returns nothing. The /24 blocks immediately surrounding us continue to work just fine. If we do a lookup directly against our nameserver, it works just fine. It's like the nameserver information against that reverse DNS is just magically gone. The ARIN record looks good, nothing has changed. Last time, our upstream resubmitted the info so it would repopulate, and it started working again soon there after. I admit to not being the smartest one with how these records work: is the problem with the upstream, or ARIN's database, or is there not enough information to tell? Thanks, Caleb
I suggest doing something like: dig +trace -x 204.42.254.5 You can watch the delegation authority for the in-addr at each stage. - Jared On Jan 25, 2011, at 9:30 AM, Caleb Tennis wrote:
We have a /24 from one of our upstream providers that we handoff to a customer. The /24 has been SWIPd to us, and we have nameservers setup with ARIN against that record.
Twice now this information has just "disappeared". That is, if do reverse DNS lookups, they returns nothing, whereas they were just working fine earlier. If you do an NS lookup on the block, it returns nothing. The /24 blocks immediately surrounding us continue to work just fine. If we do a lookup directly against our nameserver, it works just fine.
It's like the nameserver information against that reverse DNS is just magically gone.
The ARIN record looks good, nothing has changed. Last time, our upstream resubmitted the info so it would repopulate, and it started working again soon there after. I admit to not being the smartest one with how these records work: is the problem with the upstream, or ARIN's database, or is there not enough information to tell?
Thanks, Caleb
+1, also a quick check to make sure your name servers are actually set can be done with host.. host -t ns 0.168.192.in-addr.arpa On 25/01/2011 10:34 PM, Jared Mauch wrote:
I suggest doing something like:
dig +trace -x 204.42.254.5
You can watch the delegation authority for the in-addr at each stage.
- Jared
On Jan 25, 2011, at 9:30 AM, Caleb Tennis wrote:
We have a /24 from one of our upstream providers that we handoff to a customer. The /24 has been SWIPd to us, and we have nameservers setup with ARIN against that record.
Twice now this information has just "disappeared". That is, if do reverse DNS lookups, they returns nothing, whereas they were just working fine earlier. If you do an NS lookup on the block, it returns nothing. The /24 blocks immediately surrounding us continue to work just fine. If we do a lookup directly against our nameserver, it works just fine.
It's like the nameserver information against that reverse DNS is just magically gone.
The ARIN record looks good, nothing has changed. Last time, our upstream resubmitted the info so it would repopulate, and it started working again soon there after. I admit to not being the smartest one with how these records work: is the problem with the upstream, or ARIN's database, or is there not enough information to tell?
Thanks, Caleb
I use Squish (www.squish.net/dnscheck) for this purpose. Reasonable web interface and gives lots of info about where things are breaking down... -- Larry Smith lesmith@ecsis.net On Tue January 25 2011 08:38, p8x wrote:
+1, also a quick check to make sure your name servers are actually set can be done with host.. host -t ns 0.168.192.in-addr.arpa
On 25/01/2011 10:34 PM, Jared Mauch wrote:
I suggest doing something like:
dig +trace -x 204.42.254.5
You can watch the delegation authority for the in-addr at each stage.
- Jared
On Jan 25, 2011, at 9:30 AM, Caleb Tennis wrote:
We have a /24 from one of our upstream providers that we handoff to a customer. The /24 has been SWIPd to us, and we have nameservers setup with ARIN against that record.
Twice now this information has just "disappeared". That is, if do reverse DNS lookups, they returns nothing, whereas they were just working fine earlier. If you do an NS lookup on the block, it returns nothing. The /24 blocks immediately surrounding us continue to work just fine. If we do a lookup directly against our nameserver, it works just fine.
It's like the nameserver information against that reverse DNS is just magically gone.
The ARIN record looks good, nothing has changed. Last time, our upstream resubmitted the info so it would repopulate, and it started working again soon there after. I admit to not being the smartest one with how these records work: is the problem with the upstream, or ARIN's database, or is there not enough information to tell?
Thanks, Caleb
On Tue, 25 Jan 2011, Larry Smith wrote:
I use Squish (www.squish.net/dnscheck) for this purpose. Reasonable web interface and gives lots of info about where things are breaking down...
-- Larry Smith
squish.net/dnscheck is great, except when I've had problems with it, or wanted a second opinion. Does anyone know another site that offers much the same functionality? Jethro. . . . . . . . . . . . . . . . . . . . . . . . . . Jethro R Binks, Network Manager, Information Services Directorate, University Of Strathclyde, Glasgow, UK The University of Strathclyde is a charitable body, registered in Scotland, number SC015263.
On 2011-01-25 17:21, Jethro R Binks wrote:
On Tue, 25 Jan 2011, Larry Smith wrote:
I use Squish (www.squish.net/dnscheck) for this purpose. Reasonable web interface and gives lots of info about where things are breaking down...
-- Larry Smith
squish.net/dnscheck is great, except when I've had problems with it, or wanted a second opinion. Does anyone know another site that offers much the same functionality?
google(dns doctor) google(zonecheck) (various places host that tool and you can install it locally too) Oh and this tool called 'dig' which is really amazing. Greets, Jeroen
On 2011-01-25 17:21, Jethro R Binks wrote:
On Tue, 25 Jan 2011, Larry Smith wrote:
I use Squish (www.squish.net/dnscheck) for this purpose. Reasonable web interface and gives lots of info about where things are breaking down...
-- Larry Smith
squish.net/dnscheck is great, except when I've had problems with it, or wanted a second opinion. Does anyone know another site that offers much the same functionality?
If you like a nice graphic schematic try: http://www.zonecut.net/dns/index.cgi -Hank
At 08:47 25/01/2011 -0600, Larry Smith wrote:
I use Squish (www.squish.net/dnscheck) for this purpose. Reasonable web interface and gives lots of info about where things are breaking down...
Seems to be having issues: Finding servers for . from A.ROOT-SERVERS.NET (198.41.0.4) Error: Resolve for NSs of . to A.ROOT-SERVERS.NET (198.41.0.4) failed: query timed out -Hank
-- Larry Smith lesmith@ecsis.net
On Tue January 25 2011 08:38, p8x wrote:
+1, also a quick check to make sure your name servers are actually set can be done with host.. host -t ns 0.168.192.in-addr.arpa
On 25/01/2011 10:34 PM, Jared Mauch wrote:
I suggest doing something like:
dig +trace -x 204.42.254.5
You can watch the delegation authority for the in-addr at each stage.
- Jared
On Jan 25, 2011, at 9:30 AM, Caleb Tennis wrote:
We have a /24 from one of our upstream providers that we handoff to a customer. The /24 has been SWIPd to us, and we have nameservers setup with ARIN against that record.
Twice now this information has just "disappeared". That is, if do reverse DNS lookups, they returns nothing, whereas they were just working fine earlier. If you do an NS lookup on the block, it returns nothing. The /24 blocks immediately surrounding us continue to work just fine. If we do a lookup directly against our nameserver, it works just fine.
It's like the nameserver information against that reverse DNS is just magically gone.
The ARIN record looks good, nothing has changed. Last time, our upstream resubmitted the info so it would repopulate, and it started working again soon there after. I admit to not being the smartest one with how these records work: is the problem with the upstream, or ARIN's database, or is there not enough information to tell?
Thanks, Caleb
Excellent, the +trace option is most helpful, thank you. On Jan 25, 2011, at 9:34 AM, Jared Mauch wrote:
I suggest doing something like:
dig +trace -x 204.42.254.5
You can watch the delegation authority for the in-addr at each stage.
- Jared
On Jan 25, 2011, at 9:30 AM, Caleb Tennis wrote:
We have a /24 from one of our upstream providers that we handoff to a customer. The /24 has been SWIPd to us, and we have nameservers setup with ARIN against that record.
Twice now this information has just "disappeared". That is, if do reverse DNS lookups, they returns nothing, whereas they were just working fine earlier. If you do an NS lookup on the block, it returns nothing. The /24 blocks immediately surrounding us continue to work just fine. If we do a lookup directly against our nameserver, it works just fine.
It's like the nameserver information against that reverse DNS is just magically gone.
The ARIN record looks good, nothing has changed. Last time, our upstream resubmitted the info so it would repopulate, and it started working again soon there after. I admit to not being the smartest one with how these records work: is the problem with the upstream, or ARIN's database, or is there not enough information to tell?
Thanks, Caleb
participants (7)
-
Caleb Tennis -
Hank Nussbacher -
Jared Mauch -
Jeroen Massar -
Jethro R Binks -
Larry Smith -
p8x