[00:24] <artillerytx> anyone have experience with setting up name servers?
[00:25] <pmatulis> !search sensors
[00:52] <artillerytx> ... so if im setting up a server and dns ... how exactly does the domain mydomain.com know that the name servers are hosted as ns1.mydomain.com
[00:52] <artillerytx> because i don't think it will take ns1.mydomain.com as a dns server
[00:53] <jmarsden> It works fine.  As an example do    dig computeroptions.net ns    and notice that both nameservers are with the domain concerned.
[00:54] <artillerytx> i followed this - http://beer.org.uk/bsacdns/
[00:54] <artillerytx> and when i try to change the name servers on my domain it says that the one i created is invalid
[00:54] <artillerytx> or am trying to use
[00:55] <jmarsden> You need to tell your domain registrar what machines are nameservers for your domain.  if it says they are invalid, then most likely your newly created nameserver is not working right, and when the registrar check it they discover that and so won't let you set your DNS servers to a non-working server.
[00:55] <artillerytx> oh okay...
[00:56] <artillerytx> i did everything in that tutorial except to see if its working which i don't know how he did that
[00:56] <jmarsden> Do you need to troubleshoot your new server and make sure it works and believes itself to be authoritative for the domain concerned.
[00:56] <jmarsden> Ever heard of the dig command? :)
[00:56] <artillerytx> never
[00:56] <jmarsden> man dig
[00:57] <artillerytx> um
[00:58] <artillerytx> well maybe you can tell me if what im doing is completely wrong or not... I want to host a couple domains off my ubuntu server
[00:58] <artillerytx> so im creating a dns server
[00:59] <jmarsden> Sounds fine as long as you know enough to run a DNS server :)
[00:59] <artillerytx> I want to learn but it seems like i can't grasp exactly how it works
[01:00] <jmarsden> DNS is just a global tree of databases so you can look up names and get numbers (IP addresses) back, and look up Ip addresses and get names back.
[01:01] <artillerytx> right... So if i have a domain lets say apples.com and i want that one to be the one that has the name servers associated with it like ns1.apples.com ... i added a master zone and then the name servers
[01:01] <artillerytx> and than what do i do domain side
[01:01] <pmatulis> artillerytx: who will be using this dns server to look up your domains?
[01:01] <artillerytx> pmatulis: what registrar ?
[01:02] <artillerytx> i just thought anytime you want to host a domain on a certain server you have to enter in the name servers and tell the hosting service this domain should look in this virtual folder
[01:02] <jmarsden> artillerytx: Does that newly created nameserver *work* ?  Can you query it (with dig) and get the answers you expect?
[01:03] <jmarsden> Until it works, telling your registrar to use it as a master DNS server is not a good idea...
[01:03] <artillerytx> jmarsden: when i do digg @apples.com it says no server could be reached
[01:04] <jmarsden> artillerytx: Use the Ip address sicne it is not yet registered :)  dig @12.34.56.78 apples.com
[01:04] <artillerytx> k
[01:05] <artillerytx> im behind a router i should probly open the ports
[01:05] <giovani> artillerytx: apples.com is the domain, not the address of the server, I imagine
[01:05] <giovani> there's no need to forward ports if you're testing internally
[01:05] <artillerytx> okay
[01:06] <jmarsden> What does    dig @12.34.56.78  apples.com   do when 12.34.56.78 is the local IP on your LAN of the DNS server machine?
[01:06] <artillerytx> i tried dig @xx.xx.xx.78 longhornpcrepair.com and it says connection timed out
[01:07] <artillerytx> oh lol
[01:07] <jmarsden> Where xx.xx.xx.78 is a local IP address?
[01:07] <artillerytx> okay i'm seeing the name servers
[01:07] <jmarsden> You are testing internally...
[01:07] <giovani> artillerytx: then either your DNS daemon isn't running, or there's a firewall in the way
[01:08] <jmarsden> So, now use dig to check all the info you expect (MX records, A records, etc).  When you know they are all there, you'll need to straighten out your router/firewall so the rest of the world can see this DNs server.
[01:08] <artillerytx> alright im seeing the name servers i created earlier
[01:08] <giovani> where are you seeing them?
[01:08] <artillerytx> on the local ip
[01:08] <giovani> you said dig failed and said connection timed out
[01:08] <artillerytx> i was using the public ip
[01:09] <artillerytx> its been a long day
[01:09] <artillerytx> now i can open the ports
[01:09] <giovani> ok, well if you have an A record for that domain ... then the answer should've been printed
[01:10] <artillerytx> oh where is says SERVER:192.168.1.2#82(192.168.1.2)
[01:10] <artillerytx> woops
[01:11] <artillerytx> the #number is the port i open
[01:11] <giovani> no
[01:12] <giovani> DNS is run over port 53
[01:12] <artillerytx> forgive me if i sound super idiotic this is just very new and strange
[01:13] <artillerytx> Okay so what do i need to do so that my registrar will let me use ns1.apples.com
[01:13] <giovani> well you're in the middle of a topic you haven't really learned yet, so it's normal for it to be new and strange
[01:13] <jmarsden> artillerytx: Straighten out your firewall so the world can see your DNS server on TCP and UDP port 53.
[01:13] <giovani> artillerytx: you need to register your nameservers with your registrar, each registrar has different ways of doing this
[01:13] <jmarsden> Then ask your registrar to use your server as the master DNS server for your domain.
[01:14] <jmarsden> Until your newly created DNS server exists (and works) on the Internet, your registrar is unlikely to let you use it, because for everyone except you, it does not yet really exist :)
[01:15] <giovani> I don't know of registrars that prevent you from using inactive DNS servers
[01:15] <giovani> but he'll need to register his nameservers first if he wants them to be referenced as nsX.apples.com
[01:16] <artillerytx> okay well i opened the port 53
[01:17] <jmarsden> artillerytx: Do you have a way to test frm the outside?  ssh to a remote machine and dig from there to @yy.yy.yy.yy apples.com where that is your public Internet Ip of the DNS server?
[01:17] <artillerytx> how do i check and see if the world can see it
[01:17] <artillerytx> jmarsden: no i don't
[01:18] <jmarsden> Or tell me what the IP and apples.com are and I can test it from here... :)
[01:18] <artillerytx> can i PM you ?
[01:18] <jmarsden> Sure.
[01:18] <giovani> artillerytx: this isn't a secret, you've already pasted your domain name into the channel
[01:18] <giovani> and your nameserver's IP can't be private
[01:18] <artillerytx> thats true
[01:19] <artillerytx> well my domain isn't apples.com
[01:19] <giovani> I'm aware
[01:19] <giovani> you pasted it earlier
[01:19] <artillerytx> Oh okay
[01:19] <artillerytx> haha sorry i trust you guys
[01:19] <giovani> well trust us or not, the channel is logged on the internet
[01:20] <artillerytx> k
[01:20] <artillerytx> so it would be @75.43.20.78  dns1.longhornpcrepair.com
[01:20] <artillerytx> i guess
[01:20] <giovani> no ...
[01:21] <giovani> we're not looking for an A record for dns1.
[01:21] <giovani> but yes, your DNS server is reachable from the internet
[01:22] <giovani> so you can continue setting things up
[01:22] <artillerytx> hooray
[01:22] <artillerytx> argg still not taking it
[01:23] <artillerytx> is there something special i need to do to get them to take it
[02:32] <giovani> artillerytx: I told you that you need to *register* your name servers first
[02:32] <artillerytx> how do you do that
[04:55] <ball> kirkland: ping
[05:02] <ball> Goodnight everyone
[07:36] <uvirtbot`> New bug: #404768 in bacula (universe) "package bacula-director-mysql 2.4.4-1ubuntu5 failed to install/upgrade: subprocess post-installation script returned error exit status 1" [Undecided,New] https://launchpad.net/bugs/404768
[09:11] <Skaag> how do I get pure-ftpd to recognize a symlink?
[13:11] <nai1sirk> Has anyone enabled SELinux on a ubuntu server?
[13:19] <andy1234124> hi
[13:20] <andy1234124> I can't setup apache2 mod_rewrite properly under ubuntu(it works well under windows, but not ubuntu).
[13:21] <andy1234124> anyone there?
[13:32] <RoyK> andy1234124: works for me (tm)
[13:32] <RoyK> have you enabled it?
[13:38] <andy1234124> yes.
[13:38] <andy1234124> Royk: yes
[13:39] <andy1234124> it works for some pattern
[13:39] <RoyK> erm
[13:39] <RoyK> ok?
[13:40] <RoyK> it's still only apache - the code is the same
[13:40] <andy1234124> under windows, all the patterns are ok. but under ubuntu, some are ok, some don't work.
[13:40] <RoyK> what versions of apache?
[13:41] <andy1234124> apache2.2
[13:42] <andy1234124> there are apache2.conf, http.conf, sites-enabled/000-default, i am not sure which file should I add the rules?
[14:06] <giovani> andy1234124: this is probably much more relevant for #apache (they probably know more definitively)
[14:07] <andy1234124> giovani: thanks
[14:08] <andy1234124> RoyK: thanks
[14:09] <giovani> my initial guess is either your rules are for a different version syntax, or they weren't written to spec initially, and now they're broken in the newer version, or there are some minor differences between the *nix/windows versions
[14:12] <andy1234124> ah, interesting. I moved the rules into that specific directory, then it works
[14:12] <giovani> you said some were working, some weren't
[14:12] <giovani> that doesn't really make sense if they were in the wrong directory
[14:13] <andy1234124> no. i put those things globally inside apache2.conf
[14:14] <andy1234124> sorry for the confusion. now i moved them to sites-enabled/000-default, then everything is ok
[14:17] <andy1234124> but still don't understand why can't put things at the end of apache2.conf.
[14:17] <giovani> nobody said you can't -- it's just messy, and definitely not scalable
[14:20] <giovani> you'll appreciate one-config-per-site when you have a few hundred/thousand of them, trust me :)
[14:21] <andy1234124> :) thanks a lot. i don't know much about apache, i'll definitely read the apache manual ag.
[16:46] <uvirtbot`> New bug: #404905 in mysql-dfsg-5.0 (main) "package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 [modified: /var/lib/dpkg/info/mysql-server-5.0.list] failed to install/upgrade: subproces pre-installation script gaf een foutwaarde 1 terug" [Undecided,New] https://launchpad.net/bugs/404905
[19:09] <artillerytx> is there no apache module for ebox
[19:49] <fightskillz> hi, is there a log that shows ssh user actions?
[20:11] <giovani|notwork> fightskillz: you mean shell commands?  That's up to the shell to record
[20:13] <fightskillz> my server got hacked this morning, I wanted to see what they did after they ssh-ed in.. assuming they didn't delete their tracks
[20:14] <giovani|notwork> fightskillz: do you know which user they logged in as?
[20:17] <fightskillz> not yet, i'm gonna boot up and grab the logs and then decide what to do.. just want to make sure i get them all
[20:17] <giovani|notwork> well there's no need to "get" them all -- whatever's there is there
[20:18] <giovani|notwork> presuming the users use the bash shell, they'll have a file in their home directory named .bash_history
[20:18] <artillerytx> woo i registered my name servers
[20:18] <artillerytx> how do i remove ebox ?
[20:18] <giovani|notwork> artillerytx: sudo apt-get remove ebox
[20:19] <artillerytx> i didn't know ebox wasn't really for web servers
[20:19] <fightskillz> i'm concerned that they'll ssh in again and delete the log files. but thanks i'll download the home directories too
[20:20] <giovani|notwork> fightskillz: if the system has been compromised, you shouldn't be placing it back on the network at all, so that shouldn't be a concern
[20:22] <fightskillz> catch 22?
[20:22] <giovani|notwork> that's not a catch-22
[20:23] <giovani|notwork> that's incident response 101
[20:23] <giovani|notwork> unless you're *trying* to get the attacker to log back in
[20:23] <fightskillz> ya but how do i look at the log files without putting it on the network
[20:24] <giovani|notwork> you connect via keyboard, serial console, IPMI, KVMoIP, whatever
[20:24] <chrislabeard> is there an alternative to webmin thats not ebox
[20:25] <giovani|notwork> chrislabeard: there are others ... none are supported here
[20:25] <chrislabeard> giovani|notwork: the only one that is supported is ebox ?
[20:25] <fightskillz>  ipmi
[20:26] <giovani|notwork> chrislabeard: yes
[20:26] <fightskillz> sorry, ignore that
[20:26] <chrislabeard> giovani|notwork: why ebox sucks
[20:26] <chrislabeard> giovani|notwork: wait it doesn't suck just takes more time to set up
[20:26] <giovani|notwork> chrislabeard: because ebox is the only one that works with debian/ubuntu properly
[20:26] <chrislabeard> excuse me
[20:26] <giovani|notwork> if it were up to me, none of them (including ebox) would be supported
[20:26] <giovani|notwork> but clearly there's too much demand to say no
[20:27] <chrislabeard> yeah
[20:27] <chrislabeard> cause people like me will just use the web panel instead of actually know whats going on
[20:27] <giovani|notwork> which leads to many problems down the road
[20:28] <chrislabeard> yeah
[20:28] <giovani|notwork> yeah, so I advise against using any kind of "web panel"
[20:28] <giovani|notwork> for sever administration
[20:28] <chrislabeard> alright what about like phpmyadmin ?
[20:29] <chrislabeard> that shouldn't be that bad
[20:29] <chrislabeard> just mysql
[20:29] <giovani|notwork> it's bloat, it opens up a host of security risks, and it keeps you from learning how to actually use mysql
[20:30] <giovani|notwork> but you're clearly free to use it
[20:42] <chrislabeard> man i'm getting a syntax error when i try to start apache
[20:44] <giovani> chrislabeard: presumably you mean a syntax error in your config files -- you should check them with "apachectl configtest"
[20:45] <chrislabeard> mmk
[20:45] <giovani> (this is in the apache manual, and all over google)
[21:06] <fightskillz> lol, so instead of taking your advice, I booted my server and downloaded the log files before shutting it down again..  within 10 seconds iftop was showing a bunch of ssh connections from other ips. i'm still looking through the logs but looks like they never actually got in. one set of hackers were brute forcing usernames and the other brute forcing passwords, what's funny is it's been going on for days and i only noticed it or t
[21:06] <fightskillz> hought to look after seeing suspicious apache log. i've gotta get on top of this
[21:07] <giovani> yeah ...
[21:08] <giovani> this is why IDSes are useful
[21:08] <giovani> you would've seen it instantly
[21:10] <fightskillz> agreed i've been a fool. a FOOL!
[21:17] <giovani> or even just log monitoring
[21:22] <chrislabeard> you guys know of any way to be able to see my webserver inside my network .. it works fine outside my network but i can't go to the live url and see it
[21:22] <giovani> chrislabeard: you can use its internal ip
[21:23] <chrislabeard> giovani: true
[21:23] <giovani> or have your internal dns resolve the external domain to your internal ip
[21:43] <chrislabeard> is this working http://75.43.20.78:80/ for you guys
[21:44] <fightskillz> It works!
[21:44] <chrislabeard> hooray
[21:44] <chrislabeard> what about http://longhornpcrepair.com
[21:44] <giovani> chrislabeard: yep, it works
[21:44] <chrislabeard> great
[21:45] <fightskillz> ditto
[21:45] <chrislabeard> no i need to figure out how exactly virtual hosts work
[21:45] <giovani> apache has great docs on the subject
[21:45] <chrislabeard> yeah im reading it right now
[21:46] <chrislabeard> so whenever i want to host another domain i create another virtual server add a new record to my dns server and that should be good
[21:46] <chrislabeard> im still reading thats just what im assuming right now
[21:49] <chrislabeard> so each domain has its own virtual server
[21:50] <fightskillz> dns will direct requests to your ip address, vhosts will direct those incoming requests based on port and requested domain/subdomain to a folder
[21:52] <giovani> chrislabeard: no, there's no "virtual server"
[21:52] <giovani> just a virtual name host
[21:52] <chrislabeard> giovani: yeah sorry
[21:53] <giovani> presuming you want all of your sites to be on the same IP
[21:53] <giovani> if not, then you use ip-based virtual hosts
[21:54] <chrislabeard> alright.. so i have a new domain i assign my dns servers to it... they will look on my server to see if i have created a host for this domain
[21:58] <giovani> ok
[22:00] <chrislabeard> alright i think i understand how it works now
[22:09] <Acs> hello
[22:10] <Acs> I have this entry in my crontab
[22:10] <Acs> 30 * * * * /home/acs/update.php
[22:10] <Acs> shouldn't this run every 30minutes?
[22:10] <Acs> every time the script is ran it writes to a log file and I have log dates an hour apart instead of 30m
[22:11] <Acs> anyone?
[22:13] <Acs> is there something wrong with how I set up the time??
[22:14] <giovani> Acs: no, that's incorrect
[22:14] <giovani> the first field should be "*/30" to get the job to run every 30 minutes
[22:16] <giovani> putting 30 in there means that it will run every hour at the 30 minute mark
[22:16] <Acs> oooohh of course
[22:16] <Acs> giovani thanks
[22:17] <giovani> if you know specific minute-marks you want it to run at, you can specify them
[22:17] <Acs> giovani I really just want this to run every 30 m
[22:17] <giovani> ok
[22:17] <giovani> then */30 will be what you want
[22:17] <Acs> so it will be like
[22:17] <Acs> */30 * * * * /home/acs/update.php
[22:17] <Acs> thanks giovani
[22:18] <giovani> Acs: yep
[22:37] <chrislabeard> anyone ever setup proftpd?