You are not logged in.

#1 2009-06-25 20:47:07

psycroptic
Member
Registered: 2008-08-31
Posts: 20

a not-so-serious server log question

Hey whats up. So I've had a very basic network/file server running Arch for around 7-8 months now. It's been my first true foray into working with the Linux OS without using basic GUI tools, and i have to say it's been an interesting experience, though mostly positive. The machine itself has been rock solid - I don't actually think it's been taken down ever save for a few power outages.

I may be kind of going in over my head for such a simple setup, but I've got BIND 9 running as a basic, local network resolution/caching DNS server on my home network, which consists of two desktops, a media center, and a laptop (or 2 or 3 sometimes). I've set the dhcpd server to provide IP updates and to update BIND automatically via a key. I've also got a basic samba user setup with a shared folder and a backup folder, to which both my main desktop and the media center back up to weekly/monthly. All in all, besides the minimal amount of network traffic/HD space that incremental backups consume, it's a rather low-use server - I've considered possibly setting it up to be a gateway router for the network here if I feel curious enough to take the time to do it/learn how.

As far as I can tell, everything seems to be running fine; the bind server caches all of the comps that connect to the network & makes them available for folks, and the samba setup seems to be fine. I have been getting a bunch of these in my logs though:

Jun 25 08:26:01  named[2782]: network unreachable resolving 'ns55.1und1.de/A/IN': 2001:628:453:4905::53#53
Jun 25 08:26:01  named[2782]: network unreachable resolving 'ns3.isc-sns.info/A/IN': 2001:470:1a::1#53
Jun 25 08:26:01  named[2782]: network unreachable resolving 'ns3.isc-sns.info/A/IN': 2001:5a0:10::1#53
Jun 25 08:26:04  named[2782]: network unreachable resolving 'audacious-media-player.org/A/IN': 2001:470:103:4:5::1#53
Jun 25 08:27:51  named[2782]: network unreachable resolving 'ns.msp.se/A/IN': 2001:6b0:e:3::1#53
Jun 25 08:27:51  named[2782]: network unreachable resolving 'ns.msp.se/AAAA/IN': 2001:6b0:e:3::1#53
Jun 25 08:27:51  named[2782]: network unreachable resolving 'ns2.superblock.net/AAAA/IN': 2001:4980:100::2:1#53
Jun 25 08:28:49  named[2782]: network unreachable resolving 'www.scaruffi.com/A/IN': 2001:503:231d::2:30#53
Jun 25 08:30:29  named[2782]: network unreachable resolving 'ns.webage.co.uk/A/IN': 2001:4140:180:f002::1#53
Jun 25 08:43:27  named[2782]: network unreachable resolving 'wapedia.mobi/A/IN': 2001:500:24::1#53
Jun 25 08:43:27  named[2782]: network unreachable resolving 'wapedia.mobi/A/IN': 2001:500:23::1#53
Jun 25 08:59:08  named[2782]: network unreachable resolving 'en-us.fxfeeds.mozilla.com/A/IN': 2001:503:a83e::2:30#53

like i said, everything seems to be working ok; if I run nslookups to the server using any of those addresses I get a good response back. Just wondering if this is something I should look into?

Offline

#2 2009-06-25 21:21:39

cactus
Taco Eater
From: t͈̫̹ͨa͖͕͎̱͈ͨ͆ć̥̖̝o̫̫̼s͈̭̱̞͍̃!̰
Registered: 2004-05-25
Posts: 4,622
Website

Re: a not-so-serious server log question

looks like your machine is trying to hit the ipv6 authoritative nameserver ip for some reason (and failing).
could be a client asking for an ipv6 lookup and it just timing out, then falling back to doing an ipv4 lookup..


"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍

Offline

Board footer

Powered by FluxBB