Sites stopped working

This morning all my test sites have stopped working. They have been working well since Monday.

The dns records seem to have resolved ok with wooodsidekennels.com using my ns1.badbison.co.uk

my own dns records haven't changed and point to 93.97.188.1.

If I type the ip address directly into a browser it displays the default apache page.

The only change I've noticed this morning is the mail server has now resolved and delivering all mail. Also there was a warning message on ispconfig advising of an update required. To deal with this from the command line I typed:
apt-get update
apt-get upgrade
and it performed the commands.
I then rebooted the server from command line.

The warning message is now gone from ispconfig but it's stil not serving the sites up.

Can anyone suggest what might have happened? Do I need to restart any services or something?

Thanks for the help. I took a different approach Friday - started again on debian lenny, transferred a domain to schlundtech to use as a glue record and no2 ns server left it over the weekend to propogate and this morning it's all started working fine!

All test websites can be accessed from different Internet areas. Hooray.

I've not tried it yet but i'm confident the mail services work too. What I would like to do is set up pop or imap mail services so any poiinters there would be good. I'm guessing it'll be just a case of setting up dns records?

I'll put this all into a beginners tutorial for others so you don't keep getting the same questions rephrased by people.

There were no errors in the mail error log but there were warnings in that log that I'll paste at the end.

There is something I haven't managed to get my head around regarding secondary name servers. I appreciate that I've told the schundtech registry to use my ip glued to a domain as the primary server. And it also knows the ns10.schlundtech.de is the secondary. And I understand that in my dns records I've added the ip of ns10 to allow export of the records.

Does this mean that my ns will contact the schlundtech one and give it the details, or does ns10 somehow know to contact my ns to get the records?

I'm nearly done With beginners questions (i think)

Dec 20 14:29:46 badbuntu postfix/smtpd[26623]: warning: 189.34.170.147: hostname bd22aa93.virtua.com.br verification failed: Name or service not known
Dec 20 17:10:41 badbuntu postfix/smtpd[28966]: warning: 187.11.152.222: hostname 187-11-152-222.dsl.telesp.net.br verification failed: Name or service not known
Dec 21 01:31:26 badbuntu postfix/smtpd[21179]: warning: 200.59.62.225: hostname adsl225.infracom.com.ar verification failed: Name or service not known
Dec 21 09:50:02 badbuntu postfix/smtpd[9630]: warning: 89.120.127.209: hostname adsl89-120-127-209.romtelecom.net verification failed: Name or service not known
Dec 21 15:39:00 badbuntu postfix/smtpd[14690]: warning: 95.231.50.201: hostname host201-50-static.231-95-b.business.telecomitalia.it verification failed: Name or service not known
Dec 21 18:27:19 badbuntu postfix/smtpd[17287]: warning: 110.136.246.75: hostname 75.subnet110-136-246.speedy.telkom.net.id verification failed: Name or service not known
Dec 21 19:26:57 badbuntu postfix/smtpd[18144]: warning: 201.240.183.68: hostname client-201.240.183.68.speedy.net.pe verification failed: Name or service not known
Dec 22 04:47:02 badbuntu postfix/smtpd[11222]: warning: 222.78.76.254: hostname 254.76.78.222.board.ly.fj.dynamic.163data.com.cn verification failed: Name or service not known
Dec 22 06:18:35 badbuntu postfix/smtpd[12584]: warning: 113.161.0.10: address not listed for hostname localhost
Dec 22 07:57:47 badbuntu postfix/smtpd[27649]: warning: 123.19.237.142: address not listed for hostname localhost
Dec 22 08:22:20 badbuntu postfix/smtpd[28021]: warning: 190.192.128.186: hostname 186-128-192-190.cab.prima.net.ar verification failed: Name or service not known
Dec 22 09:49:25 badbuntu postfix/smtpd[29260]: warning: 118.68.184.204: hostname adsl-dynamic-pool-xxx.hcm.fpt.vn verification failed: Name or service not known
Dec 22 13:09:32 badbuntu postfix/smtpd[32154]: warning: 122.160.96.227: hostname ABTS-North-Static-227.96.160.122.airtelbroadband.in verification failed: Name or service not known
Dec 22 16:37:02 badbuntu postfix/smtpd[2766]: warning: 95.19.18.207: hostname 207.18.19.95.dynamic.jazztel.es verification failed: Name or service not known
Dec 22 16:37:04 badbuntu postfix/smtpd[2768]: warning: 95.19.18.207: hostname 207.18.19.95.dynamic.jazztel.es verification failed: Name or service not known
Dec 22 18:08:08 badbuntu postfix/smtpd[4218]: warning: 190.48.250.16: hostname 190-48-250-16.speedy.com.ar verification failed: Name or service not known
Dec 22 18:25:15 badbuntu postfix/smtpd[4483]: warning: 212.118.142.76: hostname 212-118-142-76.saudi.net.sa verification failed: Name or service not known
Dec 22 20:08:40 badbuntu postfix/smtpd[3683]: warning: 190.247.219.54: hostname 54-219-247-190.fibertel.com.ar verification failed: Name or service not known
Dec 22 21:59:23 badbuntu postfix/smtpd[5276]: warning: 187.41.67.211: hostname 18741067211.user.veloxzone.com.br verification failed: Name or service not known
Dec 22 23:06:46 badbuntu postfix/smtpd[23644]: warning: 190.186.48.204: hostname dynamic-ip-adsl-190.186.48.204.cotas.com.bo verification failed: Name or service not known
Dec 22 23:42:00 badbuntu postfix/smtpd[24153]: warning: 189.83.193.111: hostname 18983193111.user.veloxzone.com.br verification failed: Name or service not known
Dec 23 00:18:55 badbuntu postfix/smtpd[24684]: warning: 189.121.119.236: hostname bd7977ec.virtua.com.br verification failed: Name or service not known
Dec 23 01:32:07 badbuntu postfix/smtpd[25847]: warning: 201.245.247.233: hostname adsl201-245247233.dyn.etb.net.co verification failed: Name or service not known
Dec 23 02:26:57 badbuntu postfix/smtpd[26650]: warning: 122.164.162.100: hostname ABTS-TN-dynamic-100.162.164.122.airtelbroadband.in verification failed: Name or service not known
Dec 23 08:27:47 badbuntu postfix/smtpd[13178]: warning: 125.164.199.47: hostname 47.subnet125-164-199.speedy.telkom.net.id verification failed: Name or service not known
Dec 23 09:15:13 badbuntu postfix/smtpd[13878]: warning: 89.122.156.84: hostname adsl89-122-156-84.romtelecom.net verification failed: Name or service not known
Dec 23 11:36:35 badbuntu postfix/smtpd[15916]: warning: 123.16.127.246: address not listed for hostname localhost
Dec 23 12:26:24 badbuntu postfix/smtpd[16656]: warning: 92.241.94.50: hostname host-92-241-94-50-customer.wanex.net verification failed: Name or service not known
Dec 23 12:31:10 badbuntu postfix/smtpd[16731]: warning: 95.87.198.86: hostname mladost-95-87-198-86.net1.bg verification failed: Name or service not known
Dec 23 13:07:26 badbuntu postfix/smtpd[17266]: warning: 85.100.126.247: hostname dsl.static85100126247.ttnet.net.tr verification failed: Name or service not known
Dec 23 14:01:15 badbuntu postfix/smtpd[18032]: warning: 212.125.23.99: hostname 99.23.125.212.dsl.static.turk.net verification failed: Name or service not known
Dec 23 14:05:35 badbuntu postfix/smtpd[18113]: warning: 77.78.67.74: hostname assigned-77-78-67-074.casablanca.cz verification failed: Name or service not known
Dec 23 14:31:44 badbuntu postfix/smtpd[18504]: warning: 115.48.149.17: hostname hn.kd.ny.adsl verification failed: Name or service not known
Dec 23 15:32:59 badbuntu postfix/smtpd[19389]: warning: 187.14.147.13: hostname 18714147013.user.veloxzone.com.br verification failed: Name or service not known

There is something I haven't managed to get my head around regarding secondary name servers. I appreciate that I've told the schundtech registry to use my ip glued to a domain as the primary server. And it also knows the ns10.schlundtech.de is the secondary. And I understand that in my dns records I've added the ip of ns10 to allow export of the records.

Does this mean that my ns will contact the schlundtech one and give it the details, or does ns10 somehow know to contact my ns to get the records?

Click to expand...

The secondary DNS will contact the primary one and get the records.

It seems as if there's something wrong with your name resolution. What's in /etc/resolv.conf? Are these valid nameservers?

I thought the name servers are valid. My dns shows a record for ns1.badbison.co.uk pointing to my public ip address which the router points all ports to the same ports on the lan ip of the server.

As the second name server I've used ns10.schlundtech.de as that is used in the howto. To get the ip address of this server I used the dig command which returned in the answer section 62.116.163.100. I have put this address in the ip address to export zone records section of my dns records.

That sort of refers back to my earlier question of how does ns10.schlundtech.de know it has to act as my secondary name server and go get the records.

I can't display the contents of resolv.conf as I'm on a mobile device right now and the result get lost out of the screen, although you're welcome to ssh it yourself, though I appreciate you can't help that personally to everyone.

The fault does seem intermittent. On my local network I can view web pages held fine. It also works from my phone fine using the telephone connection. It worked fine from work yesterday, but today it does not. The template sites I've put up are badbison.com and prizepalace.co.uk if you'd like to view.

There is something playing on my mind though, I have a faint memory of Reading somewhere not to use the same domain name as your LAN is. My router does have the same LAN domain as my name servers domain - badbison.co.uk. Have I imagined this or should I change the routers domain setting?

I'm not sure where it's got those names servers from though, the router is the 0.1 and I have a feeling the .154 and .155 are the names servers that the router dishes out when leasing dhcp. However, the server that this is running on is on a static IP if 0.100 as per the lenny perfect tutorial.

it's odd, when I send an email from another address i get a rejection reply straight away, although often the email does come through but not for about an hour later. A sample mail box is my name@badbison.com my name is David!

Should I delete those other name servers from resolv.conf. ? Also my file doesn't end with the question mark like the one you mentioned. I presume this doesn't matter?

Leave even the one that relates to the router ip? I'll trust you on that.

What does the resolv.conf file actually do?
Ref the ? , a question mark was included a couple of times at the end of resolv.conf. Just wanted to make sure I was editting the right file.

Still not having much luck with those emails. If I send on from an mailbox on the same server it gets through fine, if it comes from other servers outside the domain then we run into problems. Please see the return message below. I'd love to get this working properly.

I tried from a different computer on a different network today to access my two test sites. One, prizepalace.co.uk came up first time. The other, badbison.com failed the first two times quoting dns error, unable to find host.. clicked retry a third time and it came up no problems and has done ever since.

Email is still behaving very odd.. someone sent me an email from a yahoo email account last night. It never arrived and returned the following message to the sender:

Sorry, we were unable to deliver your message to the following address.

However, this morning someone sent me an email from a yahoo account and it came through fine with no reported errors.

I get the feeling one of the name servers are not working properly and it's purely chance which name server is used for the look up. Is there anyway to tell which is working properly? According to ISP config3 I have MX and A records setup for the account.

I wasn't sure if my previous slave name server was doing it's job so I've used one supplied by zoneedit which does seem to be picking up the records from the primary. The serials are currently out of sync but I think that'll cure in time.

Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Same Glue Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows:
For ns2.zoneedit.com the parent reported: ['69.72.158.226'] and your nameservers reported: ['69.72.158.226']

INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are:
93.97.188.1
69.72.158.226
You can fix this for example by adding A records to your nameservers for the zones listed above.

FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!*
ns2.zoneedit.com.badbison.co.uk

Click to expand...

web pages are still appearing intermittently and emails take six hours to get through from some domains.
I'd really appreciate some guidance as what to do next please.